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 1um7db-00AFoH-6o for pgsql-general@arkaria.postgresql.org; Wed, 13 Aug 2025 09:19:15 +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 1um7dZ-00DspZ-Jx for pgsql-general@arkaria.postgresql.org; Wed, 13 Aug 2025 09:19:13 +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 1um7dZ-00DspR-4v for pgsql-general@lists.postgresql.org; Wed, 13 Aug 2025 09:19:13 +0000 Received: from mail-pg1-x532.google.com ([2607:f8b0:4864:20::532]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1um7dX-000VcT-0Q for pgsql-general@lists.postgresql.org; Wed, 13 Aug 2025 09:19:13 +0000 Received: by mail-pg1-x532.google.com with SMTP id 41be03b00d2f7-b271f3ae786so5224160a12.3 for ; Wed, 13 Aug 2025 02:19:11 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1755076749; x=1755681549; darn=lists.postgresql.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=g80ozFuHXZ5i2JFwTdHoybRNhXkxp5nun9b9puf0Ch8=; b=jJi/+Qx/7evhHFW6RheY7EfTEOn6E4vdp+iPdUzdBvRyE9pcAObR00bx+RAO84Fjjf 9dQ14ewnUL0vaLh5Wq6zIckoNHIeUqdt66VJe/1Togpoopfu6D/xSKa9y1SLYdFv3GLT rTsMBpEEijcumg36qaLaX0xLpbC8rbq/PvJpqZoB68IyKdysJCepSQTJpMjOo1mCgR6Z TTyX+obBL2lgxEyPdfHXI5YGjhlmQ1T/Hpq9Fov4/cNwHQLWwcNW1+BeCxlNeBBw2uFH EmPjrKuPL+93O4tKOzHGslB7JnGFadGoLvBYQQB4R59CkubOK0EPLSI0I2vqBeoKxObV wfRw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1755076749; x=1755681549; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=g80ozFuHXZ5i2JFwTdHoybRNhXkxp5nun9b9puf0Ch8=; b=PkYHsK4EhPRaQp8pvlDqtNdnQehi9HE/bK0pdECeJtY0fmu6yTvvzwMcG7JoGj1VUh VYlk9odpLD3YFJsXwNgeStUrlxvbUywDQULFB+Xc8AK2ndBoHwoXSFegAZwDuekSH/DY J9RBcXtOTtOdk1gGYUsVLRei3bgjPkYQpeH2H6orUAGF6z+SL+gifP8fVJoEJvBo6qam M5zvpevAtpjFov9p2Ed9UUmwIzk9le3nMrqVbPJb/DNfOzuFv3N0qDKBa8B9k+6DefDp on7llMJX26A92yEFgxErbuXYm0B0UO4m4wVMiXxgVKs8UHFvdibSa/hNVjcn2IGMc/1Q chQQ== X-Gm-Message-State: AOJu0Yzh4oaBXbNsuOUOZxS7cOt1ACD/aw4tkbIl3l/uccZHN2Evq177 X6zHJDiy4CYneMUFK/mNuME/S+sPHrZBJgmxoWD1C87OoWkDvIo7AoMCnuePJkGkQpAGjSLUSjS iuOVrIsSiRbeyoNXh1btmWGGdaCGJT1g= X-Gm-Gg: ASbGncuSGq73S1v54N4F+ca0PsXJGAcEecKyfioXXN+Ti07nU6Kt8TTKNO5n+Gu9fTg KGvshwkERdWRCJgt5UULxLTUwUM+v4alIE36ZklhfNAYmXIF/8WUBrPIlYfGmDIIUrVUlNn12n9 3pLan1+Jv4zOLjYJW6xIG4iydU7SML/zw8mMdV9BOR8m2mQadGBGz0YEVNn5iOc2E0pE8AGKXaz paw+ffZByyuKeTk X-Google-Smtp-Source: AGHT+IGa5cwi0AnwbMmKOSusVpbSvT8ABnnyoIpetv+YaaLsnm71gsVOQx+a1Uzt6iqZdKhWkQ0BxnviU2X68/uBMRc= X-Received: by 2002:a17:902:ef03:b0:240:a54e:21a0 with SMTP id d9443c01a7336-2430d100a5cmr33302415ad.19.1755076749143; Wed, 13 Aug 2025 02:19:09 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Ruben Morais Date: Wed, 13 Aug 2025 10:18:57 +0100 X-Gm-Features: Ac12FXw_xvQhTz0I4oXCR59ZR1Tsb58-fIQ1FcyBFMrYsPDKGIt4GSSaCTFbaDQ Message-ID: Subject: Re: pgbackrest check info fails without success To: KK CHN Cc: pgsql-general@lists.postgresql.org Content-Type: multipart/alternative; boundary="0000000000002fb049063c3ba63d" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --0000000000002fb049063c3ba63d Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi, Simply update the postgres.conf with the desired stanza, and add the new one in the pgbackrest.conf file. After that, run stanza-create with the new name. Once everything is OK, go to the repository directory and remove all files related to that stanza. With this approach, there=E2=80=99s no downtime in production (just make su= re beforehand that, in a production environment, if you don't need the backups already done with old stanza name). BR *R=C3=BAben Morais* On Wed, Aug 13, 2025 at 9:48=E2=80=AFAM KK CHN wrote: > > > > > > On Wed, Aug 13, 2025 at 1:24=E2=80=AFPM Ruben Morais > 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=3DK_Repo >> --log-level-console=3Dinfo stanza-create >> successful >> >> But info check fails multiple times no even success for one time >> [root@db01 ~]# sudo -u pgbackrest pgbackrest --stanza=3DKerala_Repo >> --log-level-console=3Dinfo check <<< change Kerala_Repo to K_Repo >> fails always with error >> >> *R=C3=BAben 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 an= d > follow the below steps ) > 2. sudo -u pgbackrest pgbackers --stanza=3DK_Repo stop ( On Repo serve= r > ) and > 3. sudo -u enterprisedb pgbackrest --stanza=3DK_Repo stop ( On the DB Ser= ver > M/C also ?) > > 4. sudo -u pgbackrest pgbackrest --stanza=3DK_Repo stanza-delete ( On R= epo > server ) do I need to repeat this on DB Server also as ( sudo -u > enterprisedb pgbackrest --stanza=3DK_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=E2=80=AFAM KK CHN wrot= e: >> >>> 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 =3D 'pgbackrest --stanza=3DK_Repo archive-push %p' i= n >>> postgresql.conf >>> >>> >>> Created stanza successfully : on my Repo server >>> [root@db01 ~]# sudo -u pgbackrest pgbackrest --stanza=3DK_Repo >>> --log-level-console=3Dinfo stanza-create >>> successful >>> >>> But info check fails multiple times no even success for one time >>> [root@db01 ~]# sudo -u pgbackrest pgbackrest --stanza=3DKerala_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 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-execute= d >>> 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=3D3775881-26b1d28c --log-level-console=3Dinfo --log-level-fil= e=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: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=3D3775955-a5353845 --log-level-console=3Dinfo --log-level-fil= e=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 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=3D3776006-fc68ed25 --log-level-console=3Dinfo --log-level-fil= e=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: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=3D3776015-5508d157 --log-level-console=3Dinfo --log-level-fil= e=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: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=3D3776065-a6d63fe2 --log-level-console=3Dinfo --log-level-fil= e=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 >>> >>> >>> >>> >>> >>> >>> >>> >>> --0000000000002fb049063c3ba63d Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi,=C2=A0

Simply update t= he postgres.conf with the desired stanza, and add the new one = in the pgbackrest.conf file.
After that, run stanza-create with the new name.
Once everything is OK, go to the repository directory and remove all files = related to that stanza.

With this approach, there=E2=80=99s no downtime in production (just make= sure beforehand that, in a production environment, if you don't need= =C2=A0the backups already done with old stanza name).


BR
=
R=C3=BAben Morais



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




=
On Wed= , Aug 13, 2025 at 1:24=E2=80=AFPM 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 h= ave in postgres.log file.

Created stanza=C2=A0 successfully :=C2=A0 =C2=A0 on my Repo server
[root@db01 ~]# sudo -u pgbackrest pgback= rest --stanza=3DK_Repo --log-level-console=3Dinfo stanza-create
successful
But=C2=A0 info check fails multiple t= imes no even success for one time
[root= @db01 ~]# sudo -u pgbackrest pgbackrest --stanza=3DKerala_Repo --log-level-= console=3Dinfo check=C2=A0 =C2=A0 <<< change Kerala_Repo to K_Repo= =C2=A0
fails always with error

R=C3= =BAben Morais


I think=C2= =A0 I messed up with Stanza names ...

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

1. Stop the DB cluster on the DB serv= er machine(This is a production server, so down time constraints )=C2=A0 is= this step mandatory if=C2=A0 I wish to recreate the stanza ?
( O= r can I do without stopping the DB cluster on the DB Server machine and fol= low the below steps )
2. sudo -u pgbackrest=C2=A0 pgbackers --sta= nza=3DK_Repo=C2=A0 stop=C2=A0 ( On Repo server )=C2=A0 and
3. sud= o -u enterprisedb pgbackrest --stanza=3DK_Repo stop ( On the DB Server M/C = also ?)=C2=A0

4. sudo -u pgbackrest pgbackrest=C2= =A0 --stanza=3DK_Repo=C2=A0 stanza-delete ( On Repo server )=C2=A0 do I nee= d to repeat this on=C2=A0 DB Server also as ( sudo -u enterprisedb pgbackre= st=C2=A0 --stanza=3DK_Repo=C2=A0 stanza-delete=C2=A0 =C2=A0?)=C2=A0=C2=A0


Then
5.=C2=A0 =C2=A0 Execu= te 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=C2=A0 in the steps 1 to 4 let me know.=C2=A0=C2= =A0


Krishane
=C2=A0
=
On Wed, = Aug 13, 2025 at 8:32=E2=80=AFAM KK CHN <kkchn.in@gmail.com> wrote:
Hi all,

=
I have configured=C2=A0 pgbackrest=C2=A0 on ( RHEL 9.3=C2=A0 , p= gbackrest 2.52.1=C2=A0 database version 16 ) for a remote repo machine (RHE= L 9.3, pgbackrest 2.52.1 )=C2=A0

I have created th= e stanza=C2=A0 =C2=A0K_repo

archive_command =3D &#= 39;pgbackrest --stanza=3DK_Repo archive-push %p'=C2=A0 =C2=A0 in postgr= esql.conf


Created stanza=C2=A0 succ= essfully :=C2=A0 =C2=A0 on my Repo server
[root@db01 ~]# sudo -u = pgbackrest pgbackrest --stanza=3DK_Repo --log-level-console=3Dinfo stanza-c= reate
successful

But=C2=A0 info check fa= ils multiple times no even success for one time
[root@db01 ~]# su= do -u pgbackrest pgbackrest --stanza=3DKerala_Repo --log-level-console=3Din= fo check
fails always with error

INFO: c= heck repo1 configuration (primary)
INFO: check repo1 archive for WAL (pr= imary)
ERROR: [082]: WAL segment 000000010000001D0000001E was not archiv= ed before the 60000ms timeout
=C2=A0 =C2=A0 =C2=A0 =C2=A0HINT: check the= archive_command to ensure that all options are correct (especially --stanz= a).
=C2=A0 =C2=A0 =C2=A0 =C2=A0HINT: check the PostgreSQL server log for= errors.
=C2=A0 =C2=A0 =C2=A0 =C2=A0HINT: run the 'start' comman= d if the stanza was previously stopped.
INFO: check command end: aborted= with exception [082]

I have done start, stop, sta= rt the stanza from Repo host and re-executed the=C2=A0 info check but faile= d.=C2=A0

What may be the issue, what will be the f= ix ?=C2=A0 any hints most welcome..



Thank you
Krishane


<= /div>
here the db server log.
025-08-13 12:20:29.488 P= 00 =C2=A0 INFO: archive-push command begin 2.52.1: [pg_wal/0000000100000017= 00000021] --archive-async --exec-id=3D3775881-26b1d28c --log-level-console= =3Dinfo --log-level-file=3Ddebug --pg1-path=3D/data/edb/as16/data --pg-vers= ion-force=3D16 --process-max=3D6 --repo1-host=3D10.50.2.202 --repo1-host-us= er=3Dpgbackrest --spool-path=3D/var/spool/pgbackrest --stanza=3DK_Repo
2= 025-08-13 12:20:42 IST LOG: =C2=A0checkpoint starting: time
2025-08-13 1= 2:20:43.691 P00 =C2=A0 INFO: pushed WAL file '000000010000001700000021&= #39; to the archive asynchronously
2025-08-13 12:20:43.691 P00 =C2=A0 IN= FO: archive-push command end: completed successfully (14205ms)
2025-08-1= 3 12:20:43.698 P00 =C2=A0 INFO: archive-push command begin 2.52.1: [pg_wal/= 000000010000001700000022] --archive-async --exec-id=3D3775955-a5353845 --lo= g-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 --stanz= a=3DK_Repo
2025-08-13 12:20:57.901 P00 =C2=A0 INFO: pushed WAL file '= ;000000010000001700000022' to the archive asynchronously
2025-08-13 = 12:20:57.901 P00 =C2=A0 INFO: archive-push command end: completed successfu= lly (14205ms)
2025-08-13 12:20:57.908 P00 =C2=A0 INFO: archive-push comm= and begin 2.52.1: [pg_wal/000000010000001700000023] --archive-async --exec-= id=3D3776006-fc68ed25 --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/va= r/spool/pgbackrest --stanza=3DK_Repo
2025-08-13 12:21:01.110 P00 =C2=A0 = INFO: pushed WAL file '000000010000001700000023' to the archive asy= nchronously
2025-08-13 12:21:01.110 P00 =C2=A0 INFO: archive-push comman= d end: completed successfully (3203ms)
2025-08-13 12:21:01.118 P00 =C2= =A0 INFO: archive-push command begin 2.52.1: [pg_wal/0000000100000017000000= 24] --archive-async --exec-id=3D3776015-5508d157 --log-level-console=3Dinfo= --log-level-file=3Ddebug --pg1-path=3D/data/edb/as16/data --pg-version-for= ce=3D16 --process-max=3D6 --repo1-host=3D10.50.2.202 --repo1-host-user=3Dpg= backrest --spool-path=3D/var/spool/pgbackrest --stanza=3DK_Repo
2025-08-= 13 12:21:15.321 P00 =C2=A0 INFO: pushed WAL file '000000010000001700000= 024' to the archive asynchronously
2025-08-13 12:21:15.321 P00 =C2= =A0 INFO: archive-push command end: completed successfully (14204ms)
202= 5-08-13 12:21:15.328 P00 =C2=A0 INFO: archive-push command begin 2.52.1: [p= g_wal/000000010000001700000025] --archive-async --exec-id=3D3776065-a6d63fe= 2 --log-level-console=3Dinfo --log-level-file=3Ddebug --pg1-path=3D/data/ed= b/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







--0000000000002fb049063c3ba63d--