| From: | Don Seiler <don(at)seiler(dot)us> |
|---|---|
| To: | Rajesh Kumar <rajeshkumar(dot)dba09(at)gmail(dot)com> |
| Cc: | Pgsql-admin <pgsql-admin(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Full backup failed |
| Date: | 2024-02-19 05:05:31 |
| Message-ID: | CAHJZqBCRp+FU8BCkRSnY8Khg2ftGau0t90H2DCvG7xPW0hScOA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
On Sun, Feb 18, 2024 at 10:05 PM Rajesh Kumar <rajeshkumar(dot)dba09(at)gmail(dot)com>
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]"
>
> 7time="2024-02-18T18:26:59Z" level=fatal msg="command terminated with exit
> code 82"
>
What is your database instance's archive_command set to? Is that normally
succeeding?
--
Don Seiler
www.seiler.us
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Laurenz Albe | 2024-02-19 07:23:39 | Re: Full backup failed |
| Previous Message | Rajesh Kumar | 2024-02-19 04:05:03 | Full backup failed |