Re: Full backup failed - Mailing list pgsql-admin

From Rajesh Kumar
Subject Re: Full backup failed
Date
Msg-id CAJk5AtYvQf42EdHT30sFJtLoTkOiHJj8kWsaworLafyM1Wquvw@mail.gmail.com
Whole thread Raw
In response to Re: Full backup failed  (Laurenz Albe <laurenz.albe@cybertec.at>)
Responses Re: Full backup failed
Re: Full backup failed
List pgsql-admin
Archive command is set to pgbackrest --stanza=db archive-push "%p"

There were no such issue since last year.

In postgres logs, don't see anything related to archive. But I see, WARNING,0100, aborting backup due to backend exiting before pg_backup_stop was called....pgbackrest[backup] client backend, 58568621736954596

On Mon, 19 Feb 2024, 12:53 Laurenz Albe, <laurenz.albe@cybertec.at> wrote:
On Mon, 2024-02-19 at 09:35 +0530, Rajesh Kumar wrote:
> 6time="2024-02-18T18:26:59Z" level=info msg="stderr=[ERROR: [082]: WAL segment 0000003F0000050A0000000C was not archived before the 60000ms timeout\n HINT: check the archive_command to ensure that all options are correct (especially --stanza).\n HINT: check the PostgreSQL server log for errors.\n HINT: run the 'start' command if the stanza was previously stopped.\n]"

Look into the PostgreSQL log for messages from the "archive_comand".

Yours,
Laurenz Albe

pgsql-admin by date:

Previous
From: Laurenz Albe
Date:
Subject: Re: Full backup failed
Next
From: Michael Banck
Date:
Subject: Re: Full backup failed