Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1rjwx2-009Az8-IO for pgsql-general@arkaria.postgresql.org; Tue, 12 Mar 2024 07:53:33 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1rjwwz-007t5X-SM for pgsql-general@arkaria.postgresql.org; Tue, 12 Mar 2024 07:53:30 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1rjwwz-007t0e-Gn for pgsql-general@lists.postgresql.org; Tue, 12 Mar 2024 07:53:30 +0000 Received: from mx1.purehosting.services ([2a03:4000:56:f7c:99::f30]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1rjwwv-0045K3-Fq for pgsql-general@lists.postgresql.org; Tue, 12 Mar 2024 07:53:28 +0000 Message-ID: Date: Tue, 12 Mar 2024 08:53:22 +0100 MIME-Version: 1.0 Subject: Re: pgBadger: Cannot find any log entries from systemd-journald Content-Language: en-GB To: pgsql-general@lists.postgresql.org References: <84c14e3e-f4d7-436f-939f-f88d026743f5@frank.uvena.de> From: Frank Lanitz In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk 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 > 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