Re: Full backup failed

From: Amitpal Singh <palshekhawat(at)gmail(dot)com>
To: Rajesh Kumar <rajeshkumar(dot)dba09(at)gmail(dot)com>
Cc: Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>, Pgsql-admin <pgsql-admin(at)lists(dot)postgresql(dot)org>
Subject: Re: Full backup failed
Date: 2024-02-19 14:27:26
Message-ID: CAJV0TBDv_DOSVJg6mm4y_-UpN58Vh6=wQW6y=xdNsThk70PtuQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

You can do one thing delete the stanza and re create it , it will work .

On Mon, Feb 19, 2024, 1:14 PM Rajesh Kumar <rajeshkumar(dot)dba09(at)gmail(dot)com>
wrote:

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

In response to

Browse pgsql-admin by date

  From Date Subject
Next Message Rajesh Kumar 2024-02-20 04:32:02 Wraparound
Previous Message Michael Banck 2024-02-19 07:50:57 Re: Full backup failed