pg.ddx.io  pgsql-general@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Frank Lanitz <frank@frank.uvena.de>
To: pgsql-general@lists.postgresql.org
Subject: Re: pgBadger: Cannot find any log entries from systemd-journald
Date: Tue, 12 Mar 2024 08:53:22 +0100
Message-ID: <cf43d6e1-71e9-441f-be3b-e1e789ec98df@frank.uvena.de> (raw)
In-Reply-To: <CAKAnmm+6AfNMXXzC6Oc-i3kpKbNESjZ8muLX_a20V+w14+xmrQ@mail.gmail.com>
References: <84c14e3e-f4d7-436f-939f-f88d026743f5@frank.uvena.de>
	<CAKAnmm+6AfNMXXzC6Oc-i3kpKbNESjZ8muLX_a20V+w14+xmrQ@mail.gmail.com>

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'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





view thread (5+ messages)

Message-ID: <cf43d6e1-71e9-441f-be3b-e1e789ec98df@frank.uvena.de>
Permalink:  ../cf43d6e1-71e9-441f-be3b-e1e789ec98df@frank.uvena.de/
Also on:    postgresql.org/message-id/cf43d6e1-71e9-441f-be3b-e1e789ec98df@frank.uvena.de

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-general@postgresql.org
  Cc: frank@frank.uvena.de
  Subject: Re: pgBadger: Cannot find any log entries from systemd-journald
  In-Reply-To: <cf43d6e1-71e9-441f-be3b-e1e789ec98df@frank.uvena.de>
  References: <84c14e3e-f4d7-436f-939f-f88d026743f5@frank.uvena.de> <CAKAnmm+6AfNMXXzC6Oc-i3kpKbNESjZ8muLX_a20V+w14+xmrQ@mail.gmail.com> <cf43d6e1-71e9-441f-be3b-e1e789ec98df@frank.uvena.de>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox