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 1um9WT-00Aj8Z-Ij for pgsql-general@arkaria.postgresql.org; Wed, 13 Aug 2025 11:20:01 +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 1um9WQ-00EgoI-QO for pgsql-general@arkaria.postgresql.org; Wed, 13 Aug 2025 11:19:59 +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 1um9WQ-00Ego8-7r for pgsql-general@lists.postgresql.org; Wed, 13 Aug 2025 11:19:58 +0000 Received: from mail-yb1-xb2e.google.com ([2607:f8b0:4864:20::b2e]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1um9WN-000LrL-1D for pgsql-general@lists.postgresql.org; Wed, 13 Aug 2025 11:19:57 +0000 Received: by mail-yb1-xb2e.google.com with SMTP id 3f1490d57ef6-e930b0c1546so743034276.0 for ; Wed, 13 Aug 2025 04:19:55 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1755083995; x=1755688795; 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=fW+uyi+U/hQeydGXCPrhWz8yDdsgFp47/5tiLZuLEz4=; b=A8/DvCR5MiWJEZhv54+d0ZgWHE17Te5zI/+eHpelc/cOSEN1mxFCquZJi8wiy9UwSK VsjggVlYlwPd32jfxwcn9akfX10qJmmDf3s80dHQqgMnFslbApq/1auwwJQu/MpIPGE2 7S9fvxK/2IHFlCa+B0ffLynnhURxo3V7P8Gh2PmRkZXG2x9iiY31rDgnpSXIDeNakxEK r914QS57Kid5OwGlIxMbmKLm6A0SZoHXG053/J9PRIatos+ILkI1HD0sVJI0ifor75o3 5uDFbIeK59ab/P6Zs6iWyyA3lEPQj24EEqIce7eJDfGGDQG04bRrmZkZA38K2iJqRwDJ ldSw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1755083995; x=1755688795; 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=fW+uyi+U/hQeydGXCPrhWz8yDdsgFp47/5tiLZuLEz4=; b=prS9AU6nPxDdEiSegpqf8ZSX0cB78kTL8hkyhdEE6xBeyPI/jl6bMyxKru10pmMrct Q3R6xiEUUdisQxIkcsif1b1i+uzNwxRSn/r4jqDMLd10Gf51qyYpxxMq6z9cTtDobgV4 g5L0GszpbcqgIIWpqpObC31TyzieXcjEwibGrxu5ohUPKL+ZOFELlIH1zYExQU5ZKLH6 7Ih5jatZ/+YW1vNnUkNIzgFkbS+bDefmGUI48umtxp/BqJ2aD3Em2DD05/YbIoOooZMz qOD/5pOE8wbkJsyWZo/cmFlGbiacZP6WT4JSAezJyKs6o3bxEzJKP6OQHqnQg/3+PM20 2pVg== X-Gm-Message-State: AOJu0YwYNtIyp6Z0WfU/JMLRRoHs19gXcZ9TK6gMSell1CzKEvabbV8i mKvYDwXci4UyNluhcpHnayQDtiprCfOf8QhcqvHcrFB6Ns3p4T+CFw/dbpceF6MI/ki0jsNzUVM 7/uJ75NZAKbHRBHLLVkUxcZKeJLspr4w= X-Gm-Gg: ASbGncuXtgDAPmhw6KYuc5y3v2xcMv4PohoSnsv2WRYuOPvDeiuw3Jzybjeqg5KOJmk L+4SQJbI+ftM7auJik/0aVjTxtZMQjTqolrI7N+8SWVXqsue5q2GQjHluLy/HoKepohVdCUMO+V 6D+Rai1i4f4+Kz4cs4NGZqooPiyl96DU4skTVBfZ0qqN3OblE0Htov3/Mb6IynnWWuN8EpD4TI7 qnXMHjk X-Google-Smtp-Source: AGHT+IHm0oJEDr78j1d5PeyINSKFY3IYD9nAK9U4vJhbkBTBNj8ElAVfsxXeeYwYJJ/vB6BpOSFyu1J77nXr07jJ0+k= X-Received: by 2002:a05:690c:6887:b0:71b:6a28:8625 with SMTP id 00721157ae682-71d509214f9mr23835107b3.4.1755083994817; Wed, 13 Aug 2025 04:19:54 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: KK CHN Date: Wed, 13 Aug 2025 16:53:47 +0530 X-Gm-Features: Ac12FXxdqo6lLurmcK3ctdvs83TDrh6PsRscH-JCPCIExazScnaqTpfYHDN1Xwo Message-ID: Subject: Re: pgbackrest check info fails without success To: Ruben Morais Cc: pgsql-general@lists.postgresql.org Content-Type: multipart/alternative; boundary="0000000000000fe791063c3d5669" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --0000000000000fe791063c3d5669 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Wed, Aug 13, 2025 at 2:49=E2=80=AFPM Ruben Morais wrote: > 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 file= s > 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 the backu= ps > already done with old stanza name). > > BR > *R=C3=BAben Morais* > > > Done the new stanza creation, but the issue of stanza check fails still persists.... The pgbackrest stanza check info still fails with error : INFO: check repo1 configuration (primary) INFO: check repo1 archive for WAL (primary) ERROR: [082]: WAL segment 000000010000001D000000A1 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. seems the 60000ms the WAL files are not archived to the remote site. At DB Cluster side server N/W there we are experiencing latency issues. , so I suspect the WAL files are not archived to the remote repo server within this limit of 60s to the remote Repo server. Can we increase this limit to 60000ms? Is this advisable what the parameter to add in the pgbackrest.conf in DB Server ? [my_cluster] archive-timeout=3D120 io-timeout=3D120 ?? DB server log says 5-08-13 16:15:50.666 P00 INFO: archive-push command end: aborted with exception [062] 2025-08-13 16:15:50 IST LOG: archive command failed with exit code 62 2025-08-13 16:15:50 IST DETAIL: The failed archive command was: pgbackrest --stanza=3DK_Repo archive-push pg_wal/0000000100000018000000C8 2025-08-13 16:15:50 IST WARNING: archiving write-ahead log file "0000000100000018000000C8" failed too many times, will try again later INFO: archive-push command begin 2.52.1: [pg_wal/000000010000001900000010] --archive-async --compress-type=3Dzst --exec-id=3D4180767-84540d74 --log-level-console=3Dinfo --log-level-file=3Ddebug --log-level-stderr=3Din= fo --pg1-path=3D/data/edb/as16/data --pg-version-force=3D16 --process-max=3D6 --repo1-host=3D10.50.2.202 --repo1-host-user=3Dpgbackrest --repo1-path=3D/D= B_BKUP --spool-path=3D/var/spool/pgbackrest --stanza=3DK_Repo ERROR: [062]: stop file exists for stanza K_Repo INFO: archive-push command end: aborted with exception [062] 2025-08-13 16:25:51 IST LOG: archive command failed with exit code 62 2025-08-13 16:25:51 IST DETAIL: The failed archive command was: pgbackrest --stanza=3DK_Repo archive-push pg_wal/000000010000001900000010 2025-08-13 16:25:51 IST WARNING: archiving write-ahead log file "000000010000001900000010" failed too many times, will try again later So the N/W latency badly affects the Pgbackrest working ? > 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 >> and follow the below steps ) >> 2. sudo -u pgbackrest pgbackers --stanza=3DK_Repo stop ( On Repo serv= er >> ) and >> 3. sudo -u enterprisedb pgbackrest --stanza=3DK_Repo stop ( On the DB >> Server M/C also ?) >> >> 4. sudo -u pgbackrest pgbackrest --stanza=3DK_Repo stanza-delete ( On >> Repo 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 wro= te: >>> >>>> 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 >>>> 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-fi= le=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: complete= d >>>> 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-fi= le=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: complete= d >>>> 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-fi= le=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: complete= d >>>> 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-fi= le=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: complete= d >>>> 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-fi= le=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 >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> --0000000000000fe791063c3d5669 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


On Wed, Aug 13,= 2025 at 2:49=E2=80=AFPM Ruben Morais <ruben.gmorais@gmail.com> wrote:
Hi,=C2=A0
=

Simply update the postgres.conf with the des= ired stanza, and add the new one in the pgbackrest.conf file.<= br> 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
<= div dir=3D"ltr">
R=C3=BA= ben Morais


Done the new st= anza creation, but the issue of=C2=A0 stanza check fails still persists....= =C2=A0

The pgbackrest=C2=A0 stanza check info= still fails with error :=C2=A0

INFO: check repo1 = configuration (primary)
INFO: check repo1 archive for WAL (primary)
E= RROR: [082]: WAL segment 000000010000001D000000A1 was not archived before t= he 60000ms timeout
=C2=A0 =C2=A0 =C2=A0 =C2=A0HINT: check the archive_co= mmand to ensure that all options are correct (especially --stanza).
=C2= =A0 =C2=A0 =C2=A0 =C2=A0HINT: check the PostgreSQL server log for errors.


=C2=A0seems the 60000ms=C2=A0 = the WAL files are not archived to the remote site.=C2=A0 At DB Cluster side= server N/W there we are=C2=A0experiencing latency issues. ,=C2=A0 so I sus= pect the WAL files are not archived to the remote repo server within this l= imit of 60s=C2=A0 to the remote Repo server.=C2=A0 =C2=A0 =C2=A0 Can we inc= rease this limit to 60000ms? Is this advisable what the parameter to=C2=A0 = add in the pgbackrest.conf in=C2=A0DB Server ?
[my_cluster]
archive-timeout=3D120
io-timeout=3D120 ??



DB server log say= s
=C2=A05-08-13 16:15:50.666 P00 =C2=A0 INFO: archive-push comman= d end: aborted with exception [062]
2025-08-13 16:15:50 IST LOG: =C2= =A0archive command failed with exit code 62
2025-08-13 16:15:50 IST DETA= IL: =C2=A0The failed archive command was: pgbackrest --stanza=3DK_Repo arch= ive-push pg_wal/0000000100000018000000C8
2025-08-13 16:15:50 IST WARNING= : =C2=A0archiving write-ahead log file "0000000100000018000000C8"= failed too many times, will try again later


INFO: ar= chive-push command begin 2.52.1: [pg_wal/000000010000001900000010] --archiv= e-async --compress-type=3Dzst --exec-id=3D4180767-84540d74 --log-level-cons= ole=3Dinfo --log-level-file=3Ddebug --log-level-stderr=3Dinfo --pg1-path=3D= /data/edb/as16/data --pg-version-force=3D16 --process-max=3D6 --repo1-host= =3D10.50.2.202 --repo1-host-user=3Dpgbackrest --repo1-path=3D/DB_BKUP --spo= ol-path=3D/var/spool/pgbackrest --stanza=3DK_Repo
ERROR: [062]: stop fil= e exists for stanza K_Repo
INFO: archive-push command end: aborted with = exception [062]
2025-08-13 16:25:51 IST LOG: =C2=A0archive command faile= d with exit code 62
2025-08-13 16:25:51 IST DETAIL: =C2=A0The failed arc= hive command was: pgbackrest --stanza=3DK_Repo archive-push pg_wal/00000001= 0000001900000010
2025-08-13 16:25:51 IST WARNING: =C2=A0archiving write-= ahead log file "000000010000001900000010" failed too many times, = will try again later


So the N/W laten= cy badly affects the Pgbackrest working ?=C2=A0


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




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 dif= ferent stanza name from the configuration and from what you have in postgre= s.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=3Dinfo stanza-create
successful

But=C2=A0 info check fails multiple times no even = success for one time
[root@db01 ~]# sud= o -u pgbackrest pgbackrest --stanza=3DKerala_Repo --log-level-console=3Dinf= o check=C2=A0 =C2=A0 <<< change Kerala_Repo to K_Repo=C2=A0
<= div style=3D"text-align:left">fails always with error

<= /div>
R=C3=BAben Morais<= /b>
=


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

I want to=C2=A0 delete the w= rong stanza and recreate a new stanza.=C2=A0 =C2=A0 Please correct me if I&= #39;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 time constraints )=C2=A0 is this step mandato= ry 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 step= s )
2. sudo -u pgbackrest=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 stop ( On the DB Server M/C also ?)=C2=A0

4. sudo -u pgbackrest pgbackrest=C2=A0 --stanza=3DK_Re= po=C2=A0 stanza-delete ( On Repo server )=C2=A0 do I need to repeat this on= =C2=A0 DB Server also as ( sudo -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-c= reate step with correct stanza name .

If the= above 5 sequence are correct let me know, or if any thing repetition or no= t 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 , pgbackrest 2.52.1= =C2=A0 database version 16 ) for a remote repo machine (RHEL 9.3, pgbackres= t 2.52.1 )=C2=A0

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

archive_command =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 pg= backrest --stanza=3DK_Repo --log-level-console=3Dinfo stanza-create
successful

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

INFO: check repo1 co= nfiguration (primary)
INFO: check repo1 archive for WAL (primary)
ERR= OR: [082]: WAL segment 000000010000001D0000001E was not archived before the= 60000ms timeout
=C2=A0 =C2=A0 =C2=A0 =C2=A0HINT: check the archive_comm= and to ensure that all options 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=A0HINT: run the 'start' command if the sta= nza was previously stopped.
INFO: check command end: aborted with except= ion [082]

I have done start, stop, start the stanz= a from Repo host and re-executed the=C2=A0 info check but failed.=C2=A0

What may be the issue, what will be the fix ?=C2=A0 a= ny hints most welcome..



<= div>Thank you
Krishane


here the db server log.
025-08-13 12:20:29.488 P00 =C2=A0 IN= FO: 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=3D1= 6 --process-max=3D6 --repo1-host=3D10.50.2.202 --repo1-host-user=3Dpgbackre= st --spool-path=3D/var/spool/pgbackrest --stanza=3DK_Repo
2025-08-13 12:= 20:42 IST LOG: =C2=A0checkpoint starting: time
2025-08-13 12:20:43.691 P= 00 =C2=A0 INFO: pushed WAL file '000000010000001700000021' to the a= rchive asynchronously
2025-08-13 12:20:43.691 P00 =C2=A0 INFO: archive-p= ush command end: completed successfully (14205ms)
2025-08-13 12:20:43.69= 8 P00 =C2=A0 INFO: archive-push command begin 2.52.1: [pg_wal/0000000100000= 01700000022] --archive-async --exec-id=3D3775955-a5353845 --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:20:57.901 P00 =C2=A0 INFO: pushed WAL file '000000010000= 001700000022' to the archive asynchronously
2025-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.5= 2.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/pgb= ackrest --stanza=3DK_Repo
2025-08-13 12:21:01.110 P00 =C2=A0 INFO: pushe= d WAL file '000000010000001700000023' to the archive asynchronously=
2025-08-13 12:21:01.110 P00 =C2=A0 INFO: archive-push command end: comp= leted successfully (3203ms)
2025-08-13 12:21:01.118 P00 =C2=A0 INFO: arc= hive-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 --pro= cess-max=3D6 --repo1-host=3D10.50.2.202 --repo1-host-user=3Dpgbackrest --sp= ool-path=3D/var/spool/pgbackrest --stanza=3DK_Repo
2025-08-13 12:21:15.3= 21 P00 =C2=A0 INFO: pushed WAL file '000000010000001700000024' to t= he archive asynchronously
2025-08-13 12:21:15.321 P00 =C2=A0 INFO: archi= ve-push command end: completed successfully (14204ms)
2025-08-13 12:21:1= 5.328 P00 =C2=A0 INFO: archive-push command begin 2.52.1: [pg_wal/000000010= 000001700000025] --archive-async --exec-id=3D3776065-a6d63fe2 --log-level-c= onsole=3Dinfo --log-level-file=3Ddebug --pg1-path=3D/data/edb/as16/data --p= g-version-force=3D16 --process-max=3D6 --repo1-host=3D10.50.2.202 --repo1-h= ost-user=3Dpgbackrest --spool-path=3D/var/spool/pgbackrest --stanza=3DK_Rep= o







--0000000000000fe791063c3d5669--