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

From: Frank Lanitz <frank(at)frank(dot)uvena(dot)de>
To: pgsql-general(at)lists(dot)postgresql(dot)org
Subject: Re: pgBadger: Cannot find any log entries from systemd-journald
Date: 2024-03-12 07:53:22
Message-ID: cf43d6e1-71e9-441f-be3b-e1e789ec98df@frank.uvena.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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(at)frank(dot)uvena(dot)de <mailto:frank(at)frank(dot)uvena(dot)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't want 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

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Nick Renders 2024-03-12 09:57:19 Re: could not open file "global/pg_filenode.map": Operation not permitted
Previous Message Avi Weinberg 2024-03-12 07:21:10 RE: [External] Re: walsender RAM increases by 500 MB while data is 80 MB