Re: pgBadger: Cannot find any log entries from systemd-journald

Поиск
Список
Период
Сортировка
От Frank Lanitz
Тема Re: pgBadger: Cannot find any log entries from systemd-journald
Дата
Msg-id cf43d6e1-71e9-441f-be3b-e1e789ec98df@frank.uvena.de
обсуждение исходный текст
Ответ на pgBadger: Cannot find any log entries from systemd-journald  (Frank Lanitz <frank@frank.uvena.de>)
Список pgsql-general
Hello,

Sorry for the late response.

Am 06.03.24 um 16:40 schrieb Greg Sabino Mullane:
> On Tue, Mar 5, 2024 at 3:14 AM Frank Lanitz <frank@frank.uvena.de <mailto:frank@frank.uvena.de>> wrote:
> 
>     $ pgbadger --journalctl "journalctl -u postgresql.service"
> 
> 
> You could try adding --verbose to see if it gives more clues.

No, unfortunately not. Though, it adds some more nice information in general, but none that actually helped me.

>     Having a look into the journal there is a lot of
> 
> 
> None of the snippets from journald you showed were actually things pgbadger cares about, FWIW. 

It was just an random pick to show there is a bunch of logging -- I also can see checkpoints and vacuum etc. I just
didn'twant to paste 1GB of log ;)
 

You can get an idea of what is actually parsed by running "journalctl -u postgresql --output=short-iso"

Looks good to me.

>     log_error_verbosity = 'verbose'
> 
> 
> This is probably not needed, and there is a finite chance that the extra context is confusing pgbadger.

I tried to change it, but in my case no difference.

Cheers,
Frank



В списке pgsql-general по дате отправления:

Предыдущее
От: Avi Weinberg
Дата:
Сообщение: RE: [External] Re: walsender RAM increases by 500 MB while data is 80 MB
Следующее
От: Nick Renders
Дата:
Сообщение: Re: could not open file "global/pg_filenode.map": Operation not permitted