From: | Rajesh Kumar <rajeshkumar(dot)dba09(at)gmail(dot)com> |
---|---|
To: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
Cc: | Pgsql-admin <pgsql-admin(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Full backup failed |
Date: | 2024-02-19 07:43:36 |
Message-ID: | CAJk5AtYvQf42EdHT30sFJtLoTkOiHJj8kWsaworLafyM1Wquvw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | 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(dot)albe(at)cybertec(dot)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
>
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Banck | 2024-02-19 07:50:57 | Re: Full backup failed |
Previous Message | Laurenz Albe | 2024-02-19 07:23:39 | Re: Full backup failed |