From: Domen Šetar <domen.setar@izum.si>
To: Dischner, Anton <Anton.Dischner@med.uni-muenchen.de>
Cc: pgsql-admin@lists.postgresql.org <pgsql-admin@lists.postgresql.org>
Subject: RE: wal seams to be corrupted
Date: Fri, 19 Jul 2024 07:18:17 +0000
Message-ID: <a1b0d802971c4f82b451a26baf46d26c@izum.si> (raw)
In-Reply-To: <d700a9b981f84f8fb2b598fe8780a4e6@med.uni-muenchen.de>
References: <a3391a6f61cc492c98078c65c88c66fc@izum.si>
<d700a9b981f84f8fb2b598fe8780a4e6@med.uni-muenchen.de>
Yes. Sometimes we don't see obvious.
I noticed now that I don't have disk checks fort his host on Icinga and I'm adding some now. 😉
Best regards!
[izum]
Domen Šetar
Computer Systems Support
IZUM – Institute of Information Science | Prešernova ulica 17 | 2000 Maribor | Slovenia
T: +386 2 25 20 339 | M: +386 41 676 342 | www.izum.si<http://www.izum.si/; | domen.setar@izum.si<mailto:domen.setar@izum.si>
From: Dischner, Anton <Anton.Dischner@med.uni-muenchen.de>
Sent: Friday, July 19, 2024 9:16 AM
To: Domen Šetar <domen.setar@izum.si>
Cc: pgsql-admin@lists.postgresql.org
Subject: AW: wal seams to be corrupted
Hi,
glad you found the problem. Had it in mind but didn’t dare to say it 😉
Maybe you want to install a monitor software like check_mk or Icinga. We use both and uptime_kuma to get noticed if services trend to fail or have failed.
BTW: check_mk and the PostgreSQL is also a very nice tool.
Best regards,
Anton
Von: Domen Šetar <domen.setar@izum.si<mailto:domen.setar@izum.si>>
Gesendet: Freitag, 19. Juli 2024 09:08
An: pgsql-admin@lists.postgresql.org<mailto:pgsql-admin@lists.postgresql.org>
Betreff: RE: wal seams to be corrupted
Thank you admins for helping me.
The problem was stupid and I'm a little bit ashamed.
Archive disk was full and I didn't notice it.
I made some space on it and everything is ok know.
Best regards!
[izum]
Domen Šetar
Computer Systems Support
IZUM – Institute of Information Science | Prešernova ulica 17 | 2000 Maribor | Slovenia
T: +386 2 25 20 339 | M: +386 41 676 342 | www.izum.si<http://www.izum.si/; | domen.setar@izum.si<mailto:domen.setar@izum.si>
From: Domen Šetar
Sent: Friday, July 19, 2024 7:58 AM
To: pgsql-admin@lists.postgresql.org<mailto:pgsql-admin@lists.postgresql.org>
Subject: wal seams to be corrupted
Hi admins,
The number of wal files on my postgresql server is rising, because it seams that one wal is corrupted. Postgrsql is running normaly. I see this in postgresql log file:
2024-07-19 07:44:12 CEST [2205]: [32288-1] user=,db=,app=,client= DETAIL: The failed archive command was: test ! -f /var/lib/pgsql/ArchiveDir/000000010000044E0000009D && cp pg_wal/000000010000044E0000009D /var/lib/pgsql/ArchiveDir/000000010000044E0000009D
Usualy helped if I deleted wal in ArchiveDir directory. But not this time. Wal is copied again from pg_wal to ArchiveDir directory and error message continues.
What can I do to solve this problem? Is pg_resetwal solution fort his problem? If it is, how to use it?
Best regards!
[izum]
Domen Šetar
Computer Systems Support
IZUM – Institute of Information Science | Prešernova ulica 17 | 2000 Maribor | Slovenia
T: +386 2 25 20 339 | M: +386 41 676 342 | www.izum.si<http://www.izum.si/; | domen.setar@izum.si<mailto:domen.setar@izum.si>
Attachments:
[image/jpeg] image002.jpg (1.3K, ../a1b0d802971c4f82b451a26baf46d26c@izum.si/3-image002.jpg)
download | view image
[image/jpeg] image003.jpg (1.3K, ../a1b0d802971c4f82b451a26baf46d26c@izum.si/4-image003.jpg)
download | view image
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 using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: domen.setar@izum.si, Anton.Dischner@med.uni-muenchen.de, pgsql-admin@lists.postgresql.org
Subject: RE: wal seams to be corrupted
In-Reply-To: <a1b0d802971c4f82b451a26baf46d26c@izum.si>
* 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