Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1um5xk-009rkR-Gp for pgsql-general@arkaria.postgresql.org; Wed, 13 Aug 2025 07:31:56 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1um5xi-00D2xe-Ak for pgsql-general@arkaria.postgresql.org; Wed, 13 Aug 2025 07:31:54 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1um5xh-00D2xN-UO for pgsql-general@lists.postgresql.org; Wed, 13 Aug 2025 07:31:54 +0000 Received: from mail-yb1-xb2d.google.com ([2607:f8b0:4864:20::b2d]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1um5xf-000Uf0-2t for pgsql-general@lists.postgresql.org; Wed, 13 Aug 2025 07:31:53 +0000 Received: by mail-yb1-xb2d.google.com with SMTP id 3f1490d57ef6-e8da9b7386dso756187276.1 for ; Wed, 13 Aug 2025 00:31:51 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1755070310; x=1755675110; darn=lists.postgresql.org; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=nnjwW5rXVXDZ4EFVJG0lTNFQXDI9Z39C4Q7XkjQge6g=; b=Lp5vXCcLUvabCjWfMeQT8vn6QCF4YA7+NklFl+eJjFbtUaCse93kwDvAMkNR7ju4T5 5IQPgK74ccaW8jORG3Al8nZtAK01a7k106BvaTBQZRUzCARkpJ6JwuKaly3nB4Jwm4n0 cOrvKHlj5FoEq6Hy2u58V2d/6Fm69FkL5tinBG+/w9y8DojQn/nv2bil9Gmtcj/DY+fZ niKjnfqSYVUbv/SuLJe0EISpqdSl9RtPxWizpHMCQIck/j51vljj5C2k5/vwS6RGrZbC MAdRBh+lN8LRR2qW1zkvoQamFDMCwzUipwurM/hUvjLFP070IX1UkZ6FHHnBumxOI0wb vd5A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1755070310; x=1755675110; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=nnjwW5rXVXDZ4EFVJG0lTNFQXDI9Z39C4Q7XkjQge6g=; b=eg7fHF7kGJcO8sPQtERn9NmEgSlL/PFWivY5JGmeVu+tW21Gwvozu6E1P5NyLo57l9 gR35mLvu2RYIw5X6tqzkUdcgOqfZSWwvup1eUED4yTJ43k306fbZxwZPClAkj2Jv9gqj 9FMKxLxFSLxyWqXczOyo9xCv6LjXDJ0qXW4HwhODKa+avhxQs7wMfLrCvuaMg0KJ/rFy 6RHeDscjIGUfakKGqLkYFMFk7l9j722LNw5G4WdPDEO7D10RuRp6M8EQTtm5zI25/zX3 IOSxzg8MicgNESuaFG3ieKVXpN6QXZxPboNN6HpSRX19eYbg8Ic7iNKGM3R8nX8px2Kw pj6w== X-Gm-Message-State: AOJu0YxjsVb+o1EaLX0HaCRSHR3rQrihMAH7yUcuaKnokDwrG4ein76d HXQ2FF+m+JvXxUQO02AD2tA7n9H7+wa7ZfJRKDySzuqBFd4a6Xtxcgizoo7HwId8mzFPc9vU4bl HSys+etq6YloUEXmNNjfbBCRPNjqMCVOSiRUt X-Gm-Gg: ASbGncs9K4XKydiP1RmWHNo/b04I+ssHUU5UBcMBvCK+mD19aKtdvOMaDQ8O2Y6yFvL niBHMaEZY3E6ALdpdrpywZTgMJ9BUX3uJvbf+AF+eDV0GFBD58OjJgJZCUg7kYCZfdqViXgzGpd OAL/xxZwjj+mdB6v0wUjNuCW1hHR1hDEiVzDrbr/f2QfOmKpzeeevsDuoshsbdEcnbZKUnqoWkJ Ly6RlAa X-Google-Smtp-Source: AGHT+IGpYtvh/lC9SKMsHbUwbO54DkSXW9ZuW+NB8Dt8Hy4MdWnv4InawFXQIh3Bfi7DDjP5cJw5st4fy76Q61RcVpQ= X-Received: by 2002:a05:690c:680b:b0:71b:f2dd:6dc4 with SMTP id 00721157ae682-71d50a8f93emr16463537b3.18.1755070309595; Wed, 13 Aug 2025 00:31:49 -0700 (PDT) MIME-Version: 1.0 From: KK CHN Date: Wed, 13 Aug 2025 13:05:41 +0530 X-Gm-Features: Ac12FXwwYRjerS0HXoe2itx4w1FxWTdVEZqWSByEtE9B4tmIWKP4dpFVoXuUN7I Message-ID: Subject: pgbackrest check info fails without success To: pgsql-general@lists.postgresql.org Content-Type: multipart/alternative; boundary="0000000000005c0134063c3a2621" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --0000000000005c0134063c3a2621 Content-Type: text/plain; charset="UTF-8" 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 --0000000000005c0134063c3a2621 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi all,

I have configured=C2=A0 pgbackr= est=C2=A0 on ( RHEL 9.3=C2=A0 , pgbackrest 2.52.1=C2=A0 database version 16= ) for a remote repo machine (RHEL 9.3, pgbackrest 2.52.1 )=C2=A0

I have created the stanza=C2=A0 =C2=A0K_repo

=
archive_command =3D 'pgbackrest --stanza=3DK_Repo archive-pu= sh %p'=C2=A0 =C2=A0 in postgresql.conf


Created stanza=C2=A0 successfully :=C2=A0 =C2=A0 on my Repo server<= /div>
[root@db01 ~]# sudo -u pgbackrest pgbackrest --stanza=3DK_Repo --= log-level-console=3Dinfo stanza-create
successful

<= /div>
But=C2=A0 info check fails multiple times no even success for one= time
[root@db01 ~]# sudo -u pgbackrest pgbackrest --stanza=3DKer= ala_Repo --log-level-console=3Dinfo check
fails always with error=

INFO: check repo1 configuration (primary)
INFO= : check repo1 archive for WAL (primary)
ERROR: [082]: WAL segment 000000= 010000001D0000001E was not archived before the 60000ms timeout
=C2=A0 = =C2=A0 =C2=A0 =C2=A0HINT: check the archive_command to ensure that all opti= ons are correct (especially --stanza).
=C2=A0 =C2=A0 =C2=A0 =C2=A0HINT: = check the PostgreSQL server log for errors.
=C2=A0 =C2=A0 =C2=A0 =C2=A0H= INT: run the 'start' command if the stanza was previously stopped.<= br>INFO: check command end: aborted with exception [082]

I have done start, stop, start the stanza from Repo host and re-exec= uted the=C2=A0 info check but failed.=C2=A0

What m= ay be the issue, what will be the fix ?=C2=A0 any hints most welcome..



Thank you
Kris= hane


here the db server log.=
025-08-13 12:20:29.488 P00 =C2=A0 INFO: archive-push command beg= in 2.52.1: [pg_wal/000000010000001700000021] --archive-async --exec-id=3D37= 75881-26b1d28c --log-level-console=3Dinfo --log-level-file=3Ddebug --pg1-pa= th=3D/data/edb/as16/data --pg-version-force=3D16 --process-max=3D6 --repo1-= host=3D10.50.2.202 --repo1-host-user=3Dpgbackrest --spool-path=3D/var/spool= /pgbackrest --stanza=3DK_Repo
2025-08-13 12:20:42 IST LOG: =C2=A0checkpo= int starting: time
2025-08-13 12:20:43.691 P00 =C2=A0 INFO: pushed WAL f= ile '000000010000001700000021' to the archive asynchronously
202= 5-08-13 12:20:43.691 P00 =C2=A0 INFO: archive-push command end: completed s= uccessfully (14205ms)
2025-08-13 12:20:43.698 P00 =C2=A0 INFO: archive-p= ush command begin 2.52.1: [pg_wal/000000010000001700000022] --archive-async= --exec-id=3D3775955-a5353845 --log-level-console=3Dinfo --log-level-file= =3Ddebug --pg1-path=3D/data/edb/as16/data --pg-version-force=3D16 --process= -max=3D6 --repo1-host=3D10.50.2.202 --repo1-host-user=3Dpgbackrest --spool-= path=3D/var/spool/pgbackrest --stanza=3DK_Repo
2025-08-13 12:20:57.901 P= 00 =C2=A0 INFO: pushed WAL file '000000010000001700000022' to the a= rchive asynchronously
2025-08-13 12:20:57.901 P00 =C2=A0 INFO: archive-p= ush command end: completed successfully (14205ms)
2025-08-13 12:20:57.90= 8 P00 =C2=A0 INFO: archive-push command begin 2.52.1: [pg_wal/0000000100000= 01700000023] --archive-async --exec-id=3D3776006-fc68ed25 --log-level-conso= le=3Dinfo --log-level-file=3Ddebug --pg1-path=3D/data/edb/as16/data --pg-ve= rsion-force=3D16 --process-max=3D6 --repo1-host=3D10.50.2.202 --repo1-host-= user=3Dpgbackrest --spool-path=3D/var/spool/pgbackrest --stanza=3DK_Repo2025-08-13 12:21:01.110 P00 =C2=A0 INFO: pushed WAL file '000000010000= 001700000023' to the archive asynchronously
2025-08-13 12:21:01.110 = P00 =C2=A0 INFO: archive-push command end: completed successfully (3203ms)<= br>2025-08-13 12:21:01.118 P00 =C2=A0 INFO: archive-push command begin 2.52= .1: [pg_wal/000000010000001700000024] --archive-async --exec-id=3D3776015-5= 508d157 --log-level-console=3Dinfo --log-level-file=3Ddebug --pg1-path=3D/d= ata/edb/as16/data --pg-version-force=3D16 --process-max=3D6 --repo1-host=3D= 10.50.2.202 --repo1-host-user=3Dpgbackrest --spool-path=3D/var/spool/pgback= rest --stanza=3DK_Repo
2025-08-13 12:21:15.321 P00 =C2=A0 INFO: pushed W= AL file '000000010000001700000024' to the archive asynchronously2025-08-13 12:21:15.321 P00 =C2=A0 INFO: archive-push command end: complet= ed successfully (14204ms)
2025-08-13 12:21:15.328 P00 =C2=A0 INFO: archi= ve-push command begin 2.52.1: [pg_wal/000000010000001700000025] --archive-a= sync --exec-id=3D3776065-a6d63fe2 --log-level-console=3Dinfo --log-level-fi= le=3Ddebug --pg1-path=3D/data/edb/as16/data --pg-version-force=3D16 --proce= ss-max=3D6 --repo1-host=3D10.50.2.202 --repo1-host-user=3Dpgbackrest --spoo= l-path=3D/var/spool/pgbackrest --stanza=3DK_Repo

<= br>




<= br>

--0000000000005c0134063c3a2621--