Re: Unable to archive logs in standby server

From: Christophe Pettus <xof(at)thebuild(dot)com>
To: Meera Nair <mnair(at)commvault(dot)com>
Cc: "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org>, Punit Pranesh Koujalgi <pkoujalgi(at)commvault(dot)com>
Subject: Re: Unable to archive logs in standby server
Date: 2022-09-02 14:12:35
Message-ID: 28429F2F-A1BA-42D8-9DC7-FCA27390AD0C@thebuild.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

> On Sep 1, 2022, at 21:41, Meera Nair <mnair(at)commvault(dot)com> wrote:
> Archival hangs. Is this expected?
> postgres=# select pg_start_backup('test', true, false);
> pg_start_backup
> -----------------
> 1/F9000060
> (1 row)
>
> postgres=# select pg_stop_backup('f');
> NOTICE: base backup done, waiting for required WAL segments to be archived
> WARNING: still waiting for all required WAL segments to be archived (60 seconds elapsed)
> HINT: Check that your archive_command is executing properly. You can safely cancel this backup, but the database backup will not be usable without all the WAL segments.
> WARNING: still waiting for all required WAL segments to be archived (120 seconds elapsed)
> HINT: Check that your archive_command is executing properly. You can safely cancel this backup, but the database backup will not be usable without all the WAL segments.

This generally means the command being run by archive_command is failing. Check the PostgreSQL logs (if you are using CSV logs, check the *.log file rather than the *.csv file).

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Jeffrey Walton 2022-09-02 14:55:12 Re: How to make PostreSQL utilities honor home directories?
Previous Message Peter J. Holzer 2022-09-02 11:34:38 Re: How to make PostreSQL utilities honor home directories?