pgbackrest check info fails without success

Hi all,

I have configured pgbackrest on ( RHEL 9.3 , pgbackrest 2.52.1
database version 16 ) for a remote repo machine (RHEL 9.3, pgbackrest
2.52.1 )

I have created the stanza K_repo

archive_command = 'pgbackrest --stanza=K_Repo archive-push %p' in
postgresql.conf

Created stanza successfully : on my Repo server
[root@db01 ~]# sudo -u pgbackrest pgbackrest --stanza=K_Repo
--log-level-console=info stanza-create
successful

But info check fails multiple times no even success for one time
[root@db01 ~]# sudo -u pgbackrest pgbackrest --stanza=Kerala_Repo
--log-level-console=info check
fails always with error

INFO: check repo1 configuration (primary)
INFO: check repo1 archive for WAL (primary)
ERROR: [082]: WAL segment 000000010000001D0000001E was not archived before
the 60000ms timeout
HINT: check the archive_command to ensure that all options are
correct (especially --stanza).
HINT: check the PostgreSQL server log for errors.
HINT: run the 'start' command if the stanza was previously stopped.
INFO: check command end: aborted with exception [082]

I have done start, stop, start the stanza from Repo host and re-executed
the info check but failed.

What may be the issue, what will be the fix ? any hints most welcome..

Thank you
Krishane

*here the db server log.*
025-08-13 12:20:29.488 P00 INFO: archive-push command begin 2.52.1:
[pg_wal/000000010000001700000021] --archive-async
--exec-id=3775881-26b1d28c --log-level-console=info --log-level-file=debug
--pg1-path=/data/edb/as16/data --pg-version-force=16 --process-max=6
--repo1-host=10.50.2.202 --repo1-host-user=pgbackrest
--spool-path=/var/spool/pgbackrest --stanza=K_Repo
2025-08-13 12:20:42 IST LOG: checkpoint starting: time
2025-08-13 12:20:43.691 P00 INFO: pushed WAL file
'000000010000001700000021' to the archive asynchronously
2025-08-13 12:20:43.691 P00 INFO: archive-push command end: completed
successfully (14205ms)
2025-08-13 12:20:43.698 P00 INFO: archive-push command begin 2.52.1:
[pg_wal/000000010000001700000022] --archive-async
--exec-id=3775955-a5353845 --log-level-console=info --log-level-file=debug
--pg1-path=/data/edb/as16/data --pg-version-force=16 --process-max=6
--repo1-host=10.50.2.202 --repo1-host-user=pgbackrest
--spool-path=/var/spool/pgbackrest --stanza=K_Repo
2025-08-13 12:20:57.901 P00 INFO: pushed WAL file
'000000010000001700000022' to the archive asynchronously
2025-08-13 12:20:57.901 P00 INFO: archive-push command end: completed
successfully (14205ms)
2025-08-13 12:20:57.908 P00 INFO: archive-push command begin 2.52.1:
[pg_wal/000000010000001700000023] --archive-async
--exec-id=3776006-fc68ed25 --log-level-console=info --log-level-file=debug
--pg1-path=/data/edb/as16/data --pg-version-force=16 --process-max=6
--repo1-host=10.50.2.202 --repo1-host-user=pgbackrest
--spool-path=/var/spool/pgbackrest --stanza=K_Repo
2025-08-13 12:21:01.110 P00 INFO: pushed WAL file
'000000010000001700000023' to the archive asynchronously
2025-08-13 12:21:01.110 P00 INFO: archive-push command end: completed
successfully (3203ms)
2025-08-13 12:21:01.118 P00 INFO: archive-push command begin 2.52.1:
[pg_wal/000000010000001700000024] --archive-async
--exec-id=3776015-5508d157 --log-level-console=info --log-level-file=debug
--pg1-path=/data/edb/as16/data --pg-version-force=16 --process-max=6
--repo1-host=10.50.2.202 --repo1-host-user=pgbackrest
--spool-path=/var/spool/pgbackrest --stanza=K_Repo
2025-08-13 12:21:15.321 P00 INFO: pushed WAL file
'000000010000001700000024' to the archive asynchronously
2025-08-13 12:21:15.321 P00 INFO: archive-push command end: completed
successfully (14204ms)
2025-08-13 12:21:15.328 P00 INFO: archive-push command begin 2.52.1:
[pg_wal/000000010000001700000025] --archive-async
--exec-id=3776065-a6d63fe2 --log-level-console=info --log-level-file=debug
--pg1-path=/data/edb/as16/data --pg-version-force=16 --process-max=6
--repo1-host=10.50.2.202 --repo1-host-user=pgbackrest
--spool-path=/var/spool/pgbackrest --stanza=K_Repo

On Wed, Aug 13, 2025 at 8:32 AM KK CHN <kkchn.in@gmail.com> wrote:

Hi all,

I have configured pgbackrest on ( RHEL 9.3 , pgbackrest 2.52.1
database version 16 ) for a remote repo machine (RHEL 9.3, pgbackrest
2.52.1 )

I have created the stanza K_repo

archive_command = 'pgbackrest --stanza=K_Repo archive-push %p' in
postgresql.conf

Created stanza successfully : on my Repo server
[root@db01 ~]# sudo -u pgbackrest pgbackrest --stanza=K_Repo
--log-level-console=info stanza-create
successful

But info check fails multiple times no even success for one time
[root@db01 ~]# sudo -u pgbackrest pgbackrest --stanza=Kerala_Repo
--log-level-console=info check
fails always with error

INFO: check repo1 configuration (primary)
INFO: check repo1 archive for WAL (primary)
ERROR: [082]: WAL segment 000000010000001D0000001E was not archived
before the 60000ms timeout
HINT: check the archive_command to ensure that all options are
correct (especially --stanza).
HINT: check the PostgreSQL server log for errors.
HINT: run the 'start' command if the stanza was previously stopped.
INFO: check command end: aborted with exception [082]

I have done start, stop, start the stanza from Repo host and re-executed
the info check but failed.

What may be the issue, what will be the fix ? any hints most welcome..

Thank you
Krishane

*here the db server log.*
025-08-13 12:20:29.488 P00 INFO: archive-push command begin 2.52.1:
[pg_wal/000000010000001700000021] --archive-async
--exec-id=3775881-26b1d28c --log-level-console=info --log-level-file=debug
--pg1-path=/data/edb/as16/data --pg-version-force=16 --process-max=6
--repo1-host=10.50.2.202 --repo1-host-user=pgbackrest
--spool-path=/var/spool/pgbackrest --stanza=K_Repo
2025-08-13 12:20:42 IST LOG: checkpoint starting: time
2025-08-13 12:20:43.691 P00 INFO: pushed WAL file
'000000010000001700000021' to the archive asynchronously
2025-08-13 12:20:43.691 P00 INFO: archive-push command end: completed
successfully (14205ms)
2025-08-13 12:20:43.698 P00 INFO: archive-push command begin 2.52.1:
[pg_wal/000000010000001700000022] --archive-async
--exec-id=3775955-a5353845 --log-level-console=info --log-level-file=debug
--pg1-path=/data/edb/as16/data --pg-version-force=16 --process-max=6
--repo1-host=10.50.2.202 --repo1-host-user=pgbackrest
--spool-path=/var/spool/pgbackrest --stanza=K_Repo
2025-08-13 12:20:57.901 P00 INFO: pushed WAL file
'000000010000001700000022' to the archive asynchronously
2025-08-13 12:20:57.901 P00 INFO: archive-push command end: completed
successfully (14205ms)
2025-08-13 12:20:57.908 P00 INFO: archive-push command begin 2.52.1:
[pg_wal/000000010000001700000023] --archive-async
--exec-id=3776006-fc68ed25 --log-level-console=info --log-level-file=debug
--pg1-path=/data/edb/as16/data --pg-version-force=16 --process-max=6
--repo1-host=10.50.2.202 --repo1-host-user=pgbackrest
--spool-path=/var/spool/pgbackrest --stanza=K_Repo
2025-08-13 12:21:01.110 P00 INFO: pushed WAL file
'000000010000001700000023' to the archive asynchronously
2025-08-13 12:21:01.110 P00 INFO: archive-push command end: completed
successfully (3203ms)
2025-08-13 12:21:01.118 P00 INFO: archive-push command begin 2.52.1:
[pg_wal/000000010000001700000024] --archive-async
--exec-id=3776015-5508d157 --log-level-console=info --log-level-file=debug
--pg1-path=/data/edb/as16/data --pg-version-force=16 --process-max=6
--repo1-host=10.50.2.202 --repo1-host-user=pgbackrest
--spool-path=/var/spool/pgbackrest --stanza=K_Repo
2025-08-13 12:21:15.321 P00 INFO: pushed WAL file
'000000010000001700000024' to the archive asynchronously
2025-08-13 12:21:15.321 P00 INFO: archive-push command end: completed
successfully (14204ms)
2025-08-13 12:21:15.328 P00 INFO: archive-push command begin 2.52.1:
[pg_wal/000000010000001700000025] --archive-async
--exec-id=3776065-a6d63fe2 --log-level-console=info --log-level-file=debug
--pg1-path=/data/edb/as16/data --pg-version-force=16 --process-max=6
--repo1-host=10.50.2.202 --repo1-host-user=pgbackrest
--spool-path=/var/spool/pgbackrest --stanza=K_Repo

On Wed, Aug 13, 2025 at 1:24 PM Ruben Morais <ruben.gmorais@gmail.com>
wrote:

Hi,

All seems ok, but in your check command you use a different stanza name
from the configuration and from what you have in postgres.log file.

Created stanza successfully : on my Repo server
[root@db01 ~]# sudo -u pgbackrest pgbackrest --stanza=K_Repo
--log-level-console=info stanza-create
successful

But info check fails multiple times no even success for one time
[root@db01 ~]# sudo -u pgbackrest pgbackrest --stanza=Kerala_Repo
--log-level-console=info check <<< change Kerala_Repo to K_Repo
fails always with error

*Rúben Morais*

I think I messed up with Stanza names ...

I want to delete the wrong stanza and recreate a new stanza. Please
correct me if I'm wrong, for recreating the stanza with the
following steps ?

1. Stop the DB cluster on the DB server machine(This is a production
server, so down time constraints ) is this step mandatory if I wish to
recreate the stanza ?
( Or can I do without stopping the DB cluster on the DB Server machine and
follow the below steps )
2. sudo -u pgbackrest pgbackers --stanza=K_Repo stop ( On Repo server
) and
3. sudo -u enterprisedb pgbackrest --stanza=K_Repo stop ( On the DB Server
M/C also ?)

4. sudo -u pgbackrest pgbackrest --stanza=K_Repo stanza-delete ( On Repo
server ) do I need to repeat this on DB Server also as ( sudo -u
enterprisedb pgbackrest --stanza=K_Repo stanza-delete ?)

Then
5. Execute fresh stanza-create step with correct stanza name .

If the above 5 sequence are correct let me know, or if any thing
repetition or not required in the steps 1 to 4 let me know.

Krishane

On Wed, Aug 13, 2025 at 8:32 AM KK CHN <kkchn.in@gmail.com> wrote:

Hi all,

I have configured pgbackrest on ( RHEL 9.3 , pgbackrest 2.52.1
database version 16 ) for a remote repo machine (RHEL 9.3, pgbackrest
2.52.1 )

I have created the stanza K_repo

archive_command = 'pgbackrest --stanza=K_Repo archive-push %p' in
postgresql.conf

Created stanza successfully : on my Repo server
[root@db01 ~]# sudo -u pgbackrest pgbackrest --stanza=K_Repo
--log-level-console=info stanza-create
successful

But info check fails multiple times no even success for one time
[root@db01 ~]# sudo -u pgbackrest pgbackrest --stanza=Kerala_Repo
--log-level-console=info check
fails always with error

INFO: check repo1 configuration (primary)
INFO: check repo1 archive for WAL (primary)
ERROR: [082]: WAL segment 000000010000001D0000001E was not archived
before the 60000ms timeout
HINT: check the archive_command to ensure that all options are
correct (especially --stanza).
HINT: check the PostgreSQL server log for errors.
HINT: run the 'start' command if the stanza was previously
stopped.
INFO: check command end: aborted with exception [082]

I have done start, stop, start the stanza from Repo host and re-executed
the info check but failed.

What may be the issue, what will be the fix ? any hints most welcome..

Thank you
Krishane

*here the db server log.*
025-08-13 12:20:29.488 P00 INFO: archive-push command begin 2.52.1:
[pg_wal/000000010000001700000021] --archive-async
--exec-id=3775881-26b1d28c --log-level-console=info --log-level-file=debug
--pg1-path=/data/edb/as16/data --pg-version-force=16 --process-max=6
--repo1-host=10.50.2.202 --repo1-host-user=pgbackrest
--spool-path=/var/spool/pgbackrest --stanza=K_Repo
2025-08-13 12:20:42 IST LOG: checkpoint starting: time
2025-08-13 12:20:43.691 P00 INFO: pushed WAL file
'000000010000001700000021' to the archive asynchronously
2025-08-13 12:20:43.691 P00 INFO: archive-push command end: completed
successfully (14205ms)
2025-08-13 12:20:43.698 P00 INFO: archive-push command begin 2.52.1:
[pg_wal/000000010000001700000022] --archive-async
--exec-id=3775955-a5353845 --log-level-console=info --log-level-file=debug
--pg1-path=/data/edb/as16/data --pg-version-force=16 --process-max=6
--repo1-host=10.50.2.202 --repo1-host-user=pgbackrest
--spool-path=/var/spool/pgbackrest --stanza=K_Repo
2025-08-13 12:20:57.901 P00 INFO: pushed WAL file
'000000010000001700000022' to the archive asynchronously
2025-08-13 12:20:57.901 P00 INFO: archive-push command end: completed
successfully (14205ms)
2025-08-13 12:20:57.908 P00 INFO: archive-push command begin 2.52.1:
[pg_wal/000000010000001700000023] --archive-async
--exec-id=3776006-fc68ed25 --log-level-console=info --log-level-file=debug
--pg1-path=/data/edb/as16/data --pg-version-force=16 --process-max=6
--repo1-host=10.50.2.202 --repo1-host-user=pgbackrest
--spool-path=/var/spool/pgbackrest --stanza=K_Repo
2025-08-13 12:21:01.110 P00 INFO: pushed WAL file
'000000010000001700000023' to the archive asynchronously
2025-08-13 12:21:01.110 P00 INFO: archive-push command end: completed
successfully (3203ms)
2025-08-13 12:21:01.118 P00 INFO: archive-push command begin 2.52.1:
[pg_wal/000000010000001700000024] --archive-async
--exec-id=3776015-5508d157 --log-level-console=info --log-level-file=debug
--pg1-path=/data/edb/as16/data --pg-version-force=16 --process-max=6
--repo1-host=10.50.2.202 --repo1-host-user=pgbackrest
--spool-path=/var/spool/pgbackrest --stanza=K_Repo
2025-08-13 12:21:15.321 P00 INFO: pushed WAL file
'000000010000001700000024' to the archive asynchronously
2025-08-13 12:21:15.321 P00 INFO: archive-push command end: completed
successfully (14204ms)
2025-08-13 12:21:15.328 P00 INFO: archive-push command begin 2.52.1:
[pg_wal/000000010000001700000025] --archive-async
--exec-id=3776065-a6d63fe2 --log-level-console=info --log-level-file=debug
--pg1-path=/data/edb/as16/data --pg-version-force=16 --process-max=6
--repo1-host=10.50.2.202 --repo1-host-user=pgbackrest
--spool-path=/var/spool/pgbackrest --stanza=K_Repo

On Wed, Aug 13, 2025 at 9:48 AM KK CHN <kkchn.in@gmail.com> wrote:

On Wed, Aug 13, 2025 at 1:24 PM Ruben Morais <ruben.gmorais@gmail.com>
wrote:

Hi,

All seems ok, but in your check command you use a different stanza name
from the configuration and from what you have in postgres.log file.

Created stanza successfully : on my Repo server
[root@db01 ~]# sudo -u pgbackrest pgbackrest --stanza=K_Repo
--log-level-console=info stanza-create
successful

But info check fails multiple times no even success for one time
[root@db01 ~]# sudo -u pgbackrest pgbackrest --stanza=Kerala_Repo
--log-level-console=info check <<< change Kerala_Repo to K_Repo
fails always with error

*Rúben Morais*

I think I messed up with Stanza names ...

I want to delete the wrong stanza and recreate a new stanza. Please
correct me if I'm wrong, for recreating the stanza with the
following steps ?

1. Stop the DB cluster on the DB server machine(This is a production
server, so down time constraints ) is this step mandatory if I wish to
recreate the stanza ?
( Or can I do without stopping the DB cluster on the DB Server machine
and follow the below steps )
2. sudo -u pgbackrest pgbackers --stanza=K_Repo stop ( On Repo server
) and
3. sudo -u enterprisedb pgbackrest --stanza=K_Repo stop ( On the DB
Server M/C also ?)

4. sudo -u pgbackrest pgbackrest --stanza=K_Repo stanza-delete ( On
Repo server ) do I need to repeat this on DB Server also as ( sudo -u
enterprisedb pgbackrest --stanza=K_Repo stanza-delete ?)

Then
5. Execute fresh stanza-create step with correct stanza name .

If the above 5 sequence are correct let me know, or if any thing
repetition or not required in the steps 1 to 4 let me know.

Krishane

On Wed, Aug 13, 2025 at 8:32 AM KK CHN <kkchn.in@gmail.com> wrote:

Hi all,

I have configured pgbackrest on ( RHEL 9.3 , pgbackrest 2.52.1
database version 16 ) for a remote repo machine (RHEL 9.3, pgbackrest
2.52.1 )

I have created the stanza K_repo

archive_command = 'pgbackrest --stanza=K_Repo archive-push %p' in
postgresql.conf

Created stanza successfully : on my Repo server
[root@db01 ~]# sudo -u pgbackrest pgbackrest --stanza=K_Repo
--log-level-console=info stanza-create
successful

But info check fails multiple times no even success for one time
[root@db01 ~]# sudo -u pgbackrest pgbackrest --stanza=Kerala_Repo
--log-level-console=info check
fails always with error

INFO: check repo1 configuration (primary)
INFO: check repo1 archive for WAL (primary)
ERROR: [082]: WAL segment 000000010000001D0000001E was not archived
before the 60000ms timeout
HINT: check the archive_command to ensure that all options are
correct (especially --stanza).
HINT: check the PostgreSQL server log for errors.
HINT: run the 'start' command if the stanza was previously
stopped.
INFO: check command end: aborted with exception [082]

I have done start, stop, start the stanza from Repo host and
re-executed the info check but failed.

What may be the issue, what will be the fix ? any hints most welcome..

Thank you
Krishane

*here the db server log.*
025-08-13 12:20:29.488 P00 INFO: archive-push command begin 2.52.1:
[pg_wal/000000010000001700000021] --archive-async
--exec-id=3775881-26b1d28c --log-level-console=info --log-level-file=debug
--pg1-path=/data/edb/as16/data --pg-version-force=16 --process-max=6
--repo1-host=10.50.2.202 --repo1-host-user=pgbackrest
--spool-path=/var/spool/pgbackrest --stanza=K_Repo
2025-08-13 12:20:42 IST LOG: checkpoint starting: time
2025-08-13 12:20:43.691 P00 INFO: pushed WAL file
'000000010000001700000021' to the archive asynchronously
2025-08-13 12:20:43.691 P00 INFO: archive-push command end: completed
successfully (14205ms)
2025-08-13 12:20:43.698 P00 INFO: archive-push command begin 2.52.1:
[pg_wal/000000010000001700000022] --archive-async
--exec-id=3775955-a5353845 --log-level-console=info --log-level-file=debug
--pg1-path=/data/edb/as16/data --pg-version-force=16 --process-max=6
--repo1-host=10.50.2.202 --repo1-host-user=pgbackrest
--spool-path=/var/spool/pgbackrest --stanza=K_Repo
2025-08-13 12:20:57.901 P00 INFO: pushed WAL file
'000000010000001700000022' to the archive asynchronously
2025-08-13 12:20:57.901 P00 INFO: archive-push command end: completed
successfully (14205ms)
2025-08-13 12:20:57.908 P00 INFO: archive-push command begin 2.52.1:
[pg_wal/000000010000001700000023] --archive-async
--exec-id=3776006-fc68ed25 --log-level-console=info --log-level-file=debug
--pg1-path=/data/edb/as16/data --pg-version-force=16 --process-max=6
--repo1-host=10.50.2.202 --repo1-host-user=pgbackrest
--spool-path=/var/spool/pgbackrest --stanza=K_Repo
2025-08-13 12:21:01.110 P00 INFO: pushed WAL file
'000000010000001700000023' to the archive asynchronously
2025-08-13 12:21:01.110 P00 INFO: archive-push command end: completed
successfully (3203ms)
2025-08-13 12:21:01.118 P00 INFO: archive-push command begin 2.52.1:
[pg_wal/000000010000001700000024] --archive-async
--exec-id=3776015-5508d157 --log-level-console=info --log-level-file=debug
--pg1-path=/data/edb/as16/data --pg-version-force=16 --process-max=6
--repo1-host=10.50.2.202 --repo1-host-user=pgbackrest
--spool-path=/var/spool/pgbackrest --stanza=K_Repo
2025-08-13 12:21:15.321 P00 INFO: pushed WAL file
'000000010000001700000024' to the archive asynchronously
2025-08-13 12:21:15.321 P00 INFO: archive-push command end: completed
successfully (14204ms)
2025-08-13 12:21:15.328 P00 INFO: archive-push command begin 2.52.1:
[pg_wal/000000010000001700000025] --archive-async
--exec-id=3776065-a6d63fe2 --log-level-console=info --log-level-file=debug
--pg1-path=/data/edb/as16/data --pg-version-force=16 --process-max=6
--repo1-host=10.50.2.202 --repo1-host-user=pgbackrest
--spool-path=/var/spool/pgbackrest --stanza=K_Repo