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 1um6Jv-009wij-W0 for pgsql-general@arkaria.postgresql.org; Wed, 13 Aug 2025 07:54:52 +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 1um6Ju-00DOUH-ET for pgsql-general@arkaria.postgresql.org; Wed, 13 Aug 2025 07:54:50 +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 1um6Jt-00DOU5-QE for pgsql-general@lists.postgresql.org; Wed, 13 Aug 2025 07:54:50 +0000 Received: from mail-pf1-x42a.google.com ([2607:f8b0:4864:20::42a]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1um6Jr-000KJ9-1A for pgsql-general@lists.postgresql.org; Wed, 13 Aug 2025 07:54:49 +0000 Received: by mail-pf1-x42a.google.com with SMTP id d2e1a72fcca58-76e1ff326bbso542414b3a.1 for ; Wed, 13 Aug 2025 00:54:47 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1755071687; x=1755676487; 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=15iBJc66ZnQMrNaI5pP0RN0msBHl/cLkJCKS97+UQ0I=; b=LmMlvoTEe1M4czxKgUlhJw7jQgGqabF2liyC3SZCyhv6seSKaI98Kjf8623SZE7dFR We961NMDGQvC6vJFRPA2xTndzUyM13196Qj55siEs1q3WcMlafIm8sjtU//hamB11V+e N6RM34cw9vwbGU5hhXhYOKIsFaIj/l/icOC7HEyWktA8OCHSV4GJ1TD3O0fbvBfI5KiK 5tghxUOn2RXlCpnLot/EYiuSmFnI1yydMDnnR0Q9BtuSH6XQ+D8g4pOTniGgEQIMzcql hcau1PUww56R6Dypi02IjY6AtBQwCpueWwxCtwXdcTpjn+ayYjP3mHtJl7OgtPbxbUFC IHlw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1755071687; x=1755676487; 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=15iBJc66ZnQMrNaI5pP0RN0msBHl/cLkJCKS97+UQ0I=; b=FF1C+qpeKJuI0GKDM5CJ5loronQ2SDtpp+QuRiu8IOhk4UCdxfoytzD4qpEX4OUPQg x+TTJ2iRUtGYX3Uk4sAOu2LcaMpQWWtFP1RTCJtwi0CKxyHP7i2rUCniRFAGFrHj/CZa 9negW2xhPRullLJC2dcjFa2q64ITAfSpaYr1wJZ3CBcp0R1tDIKYXrrNz+xjbyuOLaHv rR6oXwMfKZjDIUfh1pQygdKyLLVR6zSUtjg1Q8t3yN6i90CP746gNCHYqUswPt9StKIZ PckiPzzXY+HK21PKIBADSM3/N3AjY0Vy9j8fRdH2Y90HGncveCGaIgRGnFuH54hlfPEE HT5A== X-Gm-Message-State: AOJu0YzfeXnX2JJUo1z/zOUZtEP/Caekx2eIf6vLlehCuoJibqViyJO9 ByB74bw9Adnh3D+dEMR1Eb0X3eW3Z/sm6EtcOSp0FXfkBOJVtla5qntLzhCJGSo7U0z4wgEnvRZ wwSgDWzTicGeWQjMSFf6w8wI1MZGnYkvXwnFU X-Gm-Gg: ASbGnctMaJvHiMc9HmJsepDNZ1TFrXoo7E2so8xWhJcifu6if8i54O521cXcnRHL4Y6 h+T/3xEPqxPNasQk6cINAhxERQpP2xFtAOkkt11rf9SJsHMHTLJsmkAWkGn7luse22gx9VObv1p /SA/LFlUH3pKRe5jkuCkkpgNpZEj/yRSdf3TNiWhhqFgVj79pn0uhSml20ftaethBrNGxsx9GiW /mU1VHp7Mlt9unn X-Google-Smtp-Source: AGHT+IEHR3Fg9OxXn2Mu51G8iptT3o/L+GYfqbC9IYPQSV/7m6SrkMZWtNkQgTvtsii/aG+3+DDeve+baRL4J2imUZo= X-Received: by 2002:a17:902:e882:b0:240:3dfd:99a2 with SMTP id d9443c01a7336-2430e9970a1mr25758575ad.10.1755071686736; Wed, 13 Aug 2025 00:54:46 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Ruben Morais Date: Wed, 13 Aug 2025 08:54:35 +0100 X-Gm-Features: Ac12FXzlXIzPplxBzjDa0jMlTLY46fHtLbVX8br11Wcv28l3xRdBtzhlbNCUXbI Message-ID: Subject: Re: pgbackrest check info fails without success To: KK CHN Cc: pgsql-general@lists.postgresql.org Content-Type: multipart/alternative; boundary="000000000000717d32063c3a7863" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000717d32063c3a7863 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable 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* 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 befor= e > 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=3D3775881-26b1d28c --log-level-console=3Dinfo --log-level-file= =3Ddebug > --pg1-path=3D/data/edb/as16/data --pg-version-force=3D16 --process-max=3D= 6 > --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=3D= 6 > --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=3D= 6 > --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=3D= 6 > --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=3D= 6 > --repo1-host=3D10.50.2.202 --repo1-host-user=3Dpgbackrest > --spool-path=3D/var/spool/pgbackrest --stanza=3DK_Repo > > > > > > > > > --000000000000717d32063c3a7863 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi,

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

Created stanza=C2=A0 successfully :=C2=A0 =C2=A0 on m= y Repo server
[root@db01 ~]# sudo -u pg= backrest pgbackrest --stanza=3DK_Repo --log-level-console=3Dinfo stanza-cre= ate
successful

But=C2=A0 info check f= ails multiple times no even success for one time
[root@db01 ~]# sudo -u pgbackrest pgbackrest --stanza=3DKerala_Re= po --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


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 ma= chine (RHEL 9.3, pgbackrest 2.52.1 )=C2=A0

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

archive_comm= and =3D 'pgbackrest --stanza=3DK_Repo archive-push %p'=C2=A0 =C2=A0= in postgresql.conf


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=3Din= fo stanza-create
successful

But=C2=A0 in= fo check fails multiple times no even success for one time
[root@= db01 ~]# sudo -u pgbackrest pgbackrest --stanza=3DKerala_Repo --log-level-c= onsole=3Dinfo check
fails always with error

<= div>INFO: check repo1 configuration (primary)
INFO: check repo1 archive = for WAL (primary)
ERROR: [082]: WAL segment 000000010000001D0000001E 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 (especia= lly --stanza).
=C2=A0 =C2=A0 =C2=A0 =C2=A0HINT: check the PostgreSQL ser= ver log for errors.
=C2=A0 =C2=A0 =C2=A0 =C2=A0HINT: run the 'start&= #39; command if the stanza was previously stopped.
INFO: check command e= nd: aborted with exception [082]

I have done start= , stop, start the stanza from Repo host and re-executed the=C2=A0 info chec= k but failed.=C2=A0

What may be the issue, what wi= ll be the fix ?=C2=A0 any hints most welcome..


Thank you
Krishane


here the db server log.
025-08-13 12:= 20:29.488 P00 =C2=A0 INFO: archive-push command begin 2.52.1: [pg_wal/00000= 0010000001700000021] --archive-async --exec-id=3D3775881-26b1d28c --log-lev= el-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 --rep= o1-host-user=3Dpgbackrest --spool-path=3D/var/spool/pgbackrest --stanza=3DK= _Repo
2025-08-13 12:20:42 IST LOG: =C2=A0checkpoint starting: time
20= 25-08-13 12:20:43.691 P00 =C2=A0 INFO: pushed WAL file '000000010000001= 700000021' to the archive asynchronously
2025-08-13 12:20:43.691 P00= =C2=A0 INFO: archive-push command end: completed successfully (14205ms)2025-08-13 12:20:43.698 P00 =C2=A0 INFO: archive-push command begin 2.52.1= : [pg_wal/000000010000001700000022] --archive-async --exec-id=3D3775955-a53= 53845 --log-level-console=3Dinfo --log-level-file=3Ddebug --pg1-path=3D/dat= a/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/pgbackre= st --stanza=3DK_Repo
2025-08-13 12:20:57.901 P00 =C2=A0 INFO: pushed WAL= file '000000010000001700000022' to the archive asynchronously
2= 025-08-13 12:20:57.901 P00 =C2=A0 INFO: archive-push command end: completed= successfully (14205ms)
2025-08-13 12:20:57.908 P00 =C2=A0 INFO: archive= -push command begin 2.52.1: [pg_wal/000000010000001700000023] --archive-asy= nc --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 P= 00 =C2=A0 INFO: pushed WAL file '000000010000001700000023' to the a= rchive asynchronously
2025-08-13 12:21:01.110 P00 =C2=A0 INFO: archive-p= ush 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/00000001000000= 1700000024] --archive-async --exec-id=3D3776015-5508d157 --log-level-consol= e=3Dinfo --log-level-file=3Ddebug --pg1-path=3D/data/edb/as16/data --pg-ver= sion-force=3D16 --process-max=3D6 --repo1-host=3D10.50.2.202 --repo1-host-u= ser=3Dpgbackrest --spool-path=3D/var/spool/pgbackrest --stanza=3DK_Repo
= 2025-08-13 12:21:15.321 P00 =C2=A0 INFO: pushed WAL file '0000000100000= 01700000024' to the archive asynchronously
2025-08-13 12:21:15.321 P= 00 =C2=A0 INFO: archive-push command end: completed successfully (14204ms)<= br>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-a= 6d63fe2 --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








--000000000000717d32063c3a7863--