MIME-Version: 1.0
From: KK CHN <kkchn.in@gmail.com>
Date: Tue, 24 Feb 2026 15:55:15 +0530
Message-ID: <CAKgGyB_4kn5Sec8jtY4MfvKcaeXTPdsVQd5m8TU3GF4mGcnBMA@mail.gmail.com>
Subject: pgbackrest after a network outage unable to perform backup [fails always]
To: pgsql-general <pgsql-general@postgresql.org>
Content-Type: multipart/alternative; boundary="00000000000052c64c064b8f369c"
Archived-At: <https://www.postgresql.org/message-id/CAKgGyB_4kn5Sec8jtY4MfvKcaeXTPdsVQd5m8TU3GF4mGcnBMA%40mail.gmail.com>
Precedence: bulk

--00000000000052c64c064b8f369c
Content-Type: text/plain; charset="UTF-8"

list,

After a n/w link outage my pgbackrest to a remote repo server down for a
few days. Once the link is established,  my pgbackrest always fails for
diff, full backups it starts then fails with error  "unable  to archive
before 600000ms timeout. "


I have copied the already existing  archive to a safe location (another
folder )on the reposerver, Then I stopped the  stanza from the reposerver,
and   done a stanza-delete --force     on the reposerver.

Then I recreated the  stanza again with the same stanza name and did the
info  check command, but it also fails with the 60000ms time out.


 I am checking the    Repo-archive-push-async.log  it says

[root@db1 ~]# tail -f /var/log/pgbackrest/TM_Repo-archive-push-async.log
2026-02-24 12:29:37.826 P00   WARN: local-2 process terminated unexpectedly
on signal 11
2026-02-24 12:29:37.827 P00   WARN: unable to wait on child process: [10]
No child processes
2026-02-24 12:29:37.827 P00   WARN: unable to wait on child process: [10]
No child processes
2026-02-24 12:29:37.827 P00   WARN: local-4 process terminated unexpectedly
on signal 6
2026-02-24 12:29:37.827 P00   WARN: local-5 process terminated unexpectedly
on signal 11
2026-02-24 12:29:37.827 P00   WARN: local-6 process terminated unexpectedly
on signal 11

-------------------PROCESS START-------------------
2026-02-24 12:43:59.302 P00   INFO: archive-push:async command begin
2.52.1: [/data/postgres/data/pg_wal] --archive-async --compress-type=zst
--exec-id=2537881-b2a35ac0 --log-level-console=off --log-level-stderr=off
--pg1-path= /data/postgres/data   --pg-version-force=16 --process-max=6
--repo1-host=10.25.0.202 --repo1-host-user=pgbackrest
--spool-path=/var/spool/pgbackrest --stanza=TM_Repo
2026-02-24 12:43:59.325 P00   INFO: push 10141 WAL file(s) to archive:
0000000100000BD9000000F9...0000000100000C0100000097

This goes for hours now, not yet finished. Is this normal behaviour ?    [
My bandwidth is limited btw  DBServer and repo server is only 20Mbps )

How can I overcome this copying of all the old piled up WAL files to the
reposerver (becoz it takes long hours, maybe a day / two  ? by the time the
new transactional WALs  grew ?) .


My goal is to initiate a full backup afresh on the reposerver , so it
doesn't matter all the old piled up WAL files to async to my repo server
right [ I know I am going to lose the database transaction consistency by
this act. any other way ? ]

But before a full backup when I do the info check
$ sudo -u pgbackrest pgbackrest --stanza=TM_Repo --log-level-console=info
check
it does not succeed, always fails with   60000 ms timeout error[82] ..


Any hints  to solve this much appreciated ..

Thank you,
Krishane


More info  below.. .


[root@db1 data]# cat /etc/pgbackrest/pgbackrest.conf
[TM_Repo]
pg1-path=/data/postgres/data
pg1-port=5444
pg1-user=postgres
pg-version-force=16
pg1-database=postgres

[global]
repo1-host=10.25.0.202
repo1-host-user=pgbackrest
archive-async=y
spool-path=/var/spool/pgbackrest
log-level-console=info
#log-level-file=debug
log-level-stderr=info
delta=y
compress-type=zst

[global:archive-get]
process-max= 4

[global:archive-push]
process-max= 6

[root@db1 data]#


------------

pgBackRest 2.52.1
OS   RHEL 9.4
Postgres 16

--00000000000052c64c064b8f369c
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>list,=C2=A0</div><div><br></div><div>After a n/w link=
 outage my pgbackrest to a remote repo server down for a few days. Once the=
 link is established,=C2=A0 my pgbackrest always fails for diff, full backu=
ps it starts then fails with error=C2=A0 &quot;unable=C2=A0 to archive befo=
re 600000ms timeout. &quot;</div><div><br></div><div><br></div><div>I have =
copied the already existing=C2=A0 archive to a safe location (another folde=
r )on the reposerver, Then I stopped the=C2=A0 stanza from the reposerver, =
and=C2=A0 =C2=A0done a stanza-delete --force=C2=A0 =C2=A0 =C2=A0on the repo=
server.=C2=A0</div><div><br></div><div>Then I recreated the=C2=A0 stanza ag=
ain with the same stanza name and=C2=A0did the info=C2=A0 check command, bu=
t it also fails with the 60000ms time out.=C2=A0</div><div><br></div><div><=
br></div><div>=C2=A0I am checking the=C2=A0 =C2=A0 Repo-archive-push-async.=
log=C2=A0 it says</div><div><br></div><div>[root@db1 ~]# tail -f /var/log/p=
gbackrest/TM_Repo-archive-push-async.log<br>2026-02-24 12:29:37.826 P00 =C2=
=A0 WARN: local-2 process terminated unexpectedly on signal 11<br>2026-02-2=
4 12:29:37.827 P00 =C2=A0 WARN: unable to wait on child process: [10] No ch=
ild processes<br>2026-02-24 12:29:37.827 P00 =C2=A0 WARN: unable to wait on=
 child process: [10] No child processes<br>2026-02-24 12:29:37.827 P00 =C2=
=A0 WARN: local-4 process terminated unexpectedly on signal 6<br>2026-02-24=
 12:29:37.827 P00 =C2=A0 WARN: local-5 process terminated unexpectedly on s=
ignal 11<br>2026-02-24 12:29:37.827 P00 =C2=A0 WARN: local-6 process termin=
ated unexpectedly on signal 11<br><br>-------------------PROCESS START-----=
--------------<br>2026-02-24 12:43:59.302 P00 =C2=A0 INFO: archive-push:asy=
nc command begin 2.52.1: [/data/postgres/data/pg_wal] --archive-async --com=
press-type=3Dzst --exec-id=3D2537881-b2a35ac0 --log-level-console=3Doff --l=
og-level-stderr=3Doff --pg1-path=3D

/data/postgres/data=C2=A0=C2=A0=C2=A0--pg-version-force=3D16 --process-max=
=3D6 --repo1-host=3D10.25.0.202 --repo1-host-user=3Dpgbackrest --spool-path=
=3D/var/spool/pgbackrest --stanza=3DTM_Repo</div><div>2026-02-24 12:43:59.3=
25 P00 =C2=A0 INFO: push 10141 WAL file(s) to archive: 0000000100000BD90000=
00F9...0000000100000C0100000097</div><div><br></div>This goes for hours now=
, not yet finished. Is this normal behaviour ?=C2=A0 =C2=A0 [ My bandwidth =
is limited btw=C2=A0 DBServer and repo server is only 20Mbps )=C2=A0<div><b=
r></div><div>How can I overcome this copying of all the old piled up WAL fi=
les to the reposerver (becoz it takes long hours, maybe a day / two=C2=A0 ?=
 by the time the new=C2=A0transactional=C2=A0WALs=C2=A0 grew ?) .</div><div=
><br></div><div><br></div><div>My goal is to initiate a full backup afresh =
on the reposerver , so it doesn&#39;t matter all the old piled up WAL files=
 to async to my repo server right [ I know I am going to lose the database =
transaction consistency by this act. any other way ? ]</div><div><br></div>=
<div>But before a full backup when I do the info check=C2=A0=C2=A0</div><di=
v>$ sudo -u pgbackrest pgbackrest --stanza=3DTM_Repo --log-level-console=3D=
info check=C2=A0=C2=A0</div><div>it does not succeed, always fails with=C2=
=A0 =C2=A060000 ms timeout error[82] ..</div><div><br></div><div><br></div>=
<div>Any hints=C2=A0 to solve this much appreciated ..</div><div><br></div>=
<div>Thank you,</div><div>Krishane</div><div><br></div><div><br></div><div>=
More info=C2=A0 below.. .</div><div><br></div><div><br></div><div><br></div=
><div>[root@db1 data]# cat /etc/pgbackrest/pgbackrest.conf<br>[TM_Repo]<br>=
pg1-path=3D/data/postgres/data<br>pg1-port=3D5444<br>pg1-user=3Dpostgres<br=
>pg-version-force=3D16<br>pg1-database=3Dpostgres<br><br>[global]<br>repo1-=
host=3D10.25.0.202<br>repo1-host-user=3Dpgbackrest<br>archive-async=3Dy<br>=
spool-path=3D/var/spool/pgbackrest<br>log-level-console=3Dinfo<br>#log-leve=
l-file=3Ddebug<br>log-level-stderr=3Dinfo<br>delta=3Dy<br>compress-type=3Dz=
st<br><br>[global:archive-get]<br>process-max=3D 4<br><br>[global:archive-p=
ush]<br>process-max=3D 6<br><br>[root@db1 data]#<br></div><div><br></div><d=
iv><br><br>------------</div><div><br></div><div>pgBackRest 2.52.1</div><di=
v>OS=C2=A0 =C2=A0RHEL 9.4</div><div>Postgres 16</div></div>

--00000000000052c64c064b8f369c--