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 1um79w-00A8ml-1p for pgsql-general@arkaria.postgresql.org; Wed, 13 Aug 2025 08:48:36 +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 1um79u-00Dh38-Ep for pgsql-general@arkaria.postgresql.org; Wed, 13 Aug 2025 08:48:34 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1um79t-00Dh2z-S8 for pgsql-general@lists.postgresql.org; Wed, 13 Aug 2025 08:48:34 +0000 Received: from mail-yw1-x112d.google.com ([2607:f8b0:4864:20::112d]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1um79r-000Kmy-0v for pgsql-general@lists.postgresql.org; Wed, 13 Aug 2025 08:48:33 +0000 Received: by mail-yw1-x112d.google.com with SMTP id 00721157ae682-71a38e35674so44910037b3.3 for ; Wed, 13 Aug 2025 01:48:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1755074910; x=1755679710; 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=MUs9DAQZh0sOkj0+MGSPKPsjYkvMSAAdHkOLzOeykUM=; b=P4qIhF0yFeTkJYPALzZZ4qQUP53WqrAQxY+J29HlYQRs0rjSmoLbBO9I2ygK8X6jXY F6oxHmkdJ+PcTApVbMKl0cvXL+BOsp8B/rDc7v0bTWzg7TZdMeX7KotdTI3eRSKmwOUY 2DcPvePzBatGpBDYBTRp2YBaSMS8Em7uHq8PiJ2Di7apQP5ZG9IPGVzbB2z5qQacQbP/ MvN69u+16w0Qzg5VvJ3CwCtYK9pcTlzCknXx2+1elP6zlVrHRIVrOdtFlQBsC2sl+ZGB K0xQQz6sDB60Pk27kJr3diNMWit45GZ/j0sc9yJIvFtS/IH+TRhlZRbXZNpk5JyavFdX LrEg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1755074910; x=1755679710; 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=MUs9DAQZh0sOkj0+MGSPKPsjYkvMSAAdHkOLzOeykUM=; b=QwvOIuP06zpS/DIzCweToQrrqy1cCUx7J6T803RY4rtRHU06c1IgOb6/dFZbf5UttX xb61tOCLviupk5iBRa6AbWDkUllgjXrAr5f/ZrpJyWqLylSWHmOI8E0+Rz6ltfsbIFQ9 LzkcNvCPNRCIdP/9/iRf/x/P51zpbw+w76TLzvHkjKC/OcQs5E3Uht5/34kBmnP64Hs9 SOF/CFQPkNoWvmhDweUOSsG0na3NXnp3iaaNWUcNdfVyY8MQ7MeMSKBsiVhGIiuOtRaX +WSAK37yXruuaoUqNp3ClaVRCn5HNg9kMspdBPYW4pGyTNcf9dCxfLxi+IltLnIczTsZ Twyw== X-Gm-Message-State: AOJu0Yx8ewSaR/ZJSgEnh++OqXvOjmCmxRdTZIeWhq8DTeI//zvuaVIr K2SZi5rRC+XL0KrYYZCopRNWSdhbDNDQHf9a7B6yl45epiqXvUexpGgkC2k65wEEb7MuNUSyirO mfxXpIUI3MzqxRNddNGeO8PDcWJKbGTzlpz92 X-Gm-Gg: ASbGncvEctwqhcQwqBff+eIzogaTlRX2UFiD5MmE6LPC24IO8LW36WqUemhxVlcL3w8 veBXmRvRPVdt7nHlLaiuc8I/9N5qGHzZRj5okue4lXMldTUys9U79INDjo9u2OuYPX3Z6WHD1+k WDxkN169zOZS8V2snmKqyX9zJsW1HHTJh4BqHsPJWcdbNi/DVPEbob3X3NhXfji3UmIBy1AmFvM MyoPx67 X-Google-Smtp-Source: AGHT+IEEejd0aeiAsUiYgvCgU/3BxvbhhgxD0R5jYl547ejF1e4nsYtKY+JGwWCoiJ4hMzQOUnfJNJRjG5YNq/bFVAc= X-Received: by 2002:a05:690c:724a:b0:71b:6635:df1b with SMTP id 00721157ae682-71d4e55a4cdmr25899937b3.27.1755074909751; Wed, 13 Aug 2025 01:48:29 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: KK CHN Date: Wed, 13 Aug 2025 14:22:22 +0530 X-Gm-Features: Ac12FXzWIDd-4ze5N6T4-zmouvRk2Q5bJjnJ1lon4h9KIS6bheB9-yFlrpyvw10 Message-ID: Subject: Re: pgbackrest check info fails without success To: Ruben Morais Cc: pgsql-general@lists.postgresql.org Content-Type: multipart/alternative; boundary="0000000000008ccf96063c3b380e" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --0000000000008ccf96063c3b380e Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable 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 and follow the below steps ) 2. sudo -u pgbackrest pgbackers --stanza=3DK_Repo stop ( On Repo server = ) and 3. sudo -u enterprisedb pgbackrest --stanza=3DK_Repo stop ( On the DB Serve= r M/C also ?) 4. sudo -u pgbackrest pgbackrest --stanza=3DK_Repo stanza-delete ( On Rep= o 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 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 =3D 'pgbackrest --stanza=3DK_Repo archive-push %p' in >> 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 stoppe= d. >> 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=3D3775881-26b1d28c --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: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-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 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-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: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-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: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-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 >> >> >> >> >> >> >> >> >> --0000000000008ccf96063c3b380e Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable





On Wed, Aug 13, 2025 at 1:24=E2=80= =AFPM Ruben Morais <ruben.gmo= rais@gmail.com> wrote:
Hi,

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

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

But=C2= =A0 info check fails multiple times no even success for one time
[root@db01 ~]# sudo -u pgbackrest pgbackrest --st= anza=3DKerala_Repo --log-level-console=3Dinfo check=C2=A0 =C2=A0 <<&l= t; change Kerala_Repo to K_Repo=C2=A0
f= ails 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 server machine(This is a production server, so down t= ime constraints )=C2=A0 is this step mandatory if=C2=A0 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 pgback= rest=C2=A0 pgbackers --stanza=3DK_Repo=C2=A0 stop=C2=A0 ( On Repo server )= =C2=A0 and
3. sudo -u enterprisedb pgbackrest --stanza=3DK_Repo s= top ( On the DB Server M/C also ?)=C2=A0

4. sudo -= u pgbackrest pgbackrest=C2=A0 --stanza=3DK_Repo=C2=A0 stanza-delete ( On Re= po server )=C2=A0 do I need to repeat this on=C2=A0 DB Server also as ( sud= o -u enterprisedb pgbackrest=C2=A0 --stanza=3DK_Repo=C2=A0 stanza-delete=C2= =A0 =C2=A0?)=C2=A0=C2=A0


Then
=
5.=C2=A0 =C2=A0 Execute fresh stanza-create step with correct stanza n= ame .

If the above 5 sequence are correct le= t 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


Krish= ane
=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 , pgbackrest 2.52.1=C2=A0 database version 16 ) for= a remote repo machine (RHEL 9.3, pgbackrest 2.52.1 )=C2=A0

<= /div>
I have created the stanza=C2=A0 =C2=A0K_repo

=
archive_command =3D 'pgbackrest --stanza=3DK_Repo archive-push %p&= #39;=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-le= vel-console=3Dinfo stanza-create
successful

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

INFO: check repo1 configuration (primary)
INFO: chec= k repo1 archive for WAL (primary)
ERROR: [082]: WAL segment 000000010000= 001D0000001E was not archived before the 60000ms timeout
=C2=A0 =C2=A0 = =C2=A0 =C2=A0HINT: check the archive_command to ensure that all options are= correct (especially --stanza).
=C2=A0 =C2=A0 =C2=A0 =C2=A0HINT: check t= he PostgreSQL server log for errors.
=C2=A0 =C2=A0 =C2=A0 =C2=A0HINT: ru= n 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 th= e=C2=A0 info check but failed.=C2=A0

What may be t= he issue, what will be the fix ?=C2=A0 any hints most welcome..
<= br>


Thank you
Krishane


here the db server log.
<= div>025-08-13 12:20:29.488 P00 =C2=A0 INFO: archive-push command begin 2.52= .1: [pg_wal/000000010000001700000021] --archive-async --exec-id=3D3775881-2= 6b1d28c --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:20:42 IST LOG: =C2=A0checkpoint sta= rting: time
2025-08-13 12:20:43.691 P00 =C2=A0 INFO: pushed WAL file = 9;000000010000001700000021' to the archive asynchronously
2025-08-13= 12:20:43.691 P00 =C2=A0 INFO: archive-push command end: completed successf= ully (14205ms)
2025-08-13 12:20:43.698 P00 =C2=A0 INFO: archive-push com= mand 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/v= ar/spool/pgbackrest --stanza=3DK_Repo
2025-08-13 12:20:57.901 P00 =C2=A0= INFO: pushed WAL file '000000010000001700000022' to the archive as= ynchronously
2025-08-13 12:20:57.901 P00 =C2=A0 INFO: archive-push comma= nd end: completed successfully (14205ms)
2025-08-13 12:20:57.908 P00 =C2= =A0 INFO: archive-push command begin 2.52.1: [pg_wal/0000000100000017000000= 23] --archive-async --exec-id=3D3776006-fc68ed25 --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:01.110 P00 =C2=A0 INFO: pushed WAL file '000000010000001700000= 023' to the archive asynchronously
2025-08-13 12:21:01.110 P00 =C2= =A0 INFO: archive-push command end: completed successfully (3203ms)
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-5508d157= --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:21:15.321 P00 =C2=A0 INFO: pushed WAL file= '000000010000001700000024' to the archive asynchronously
2025-0= 8-13 12:21:15.321 P00 =C2=A0 INFO: archive-push command end: completed succ= essfully (14204ms)
2025-08-13 12:21:15.328 P00 =C2=A0 INFO: archive-push= command begin 2.52.1: [pg_wal/000000010000001700000025] --archive-async --= exec-id=3D3776065-a6d63fe2 --log-level-console=3Dinfo --log-level-file=3Dde= bug --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








--0000000000008ccf96063c3b380e--