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 1sjfFb-002kYR-AH for pgsql-general@arkaria.postgresql.org; Thu, 29 Aug 2024 13:31:47 +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 1sjfFX-002Oi5-RO for pgsql-general@arkaria.postgresql.org; Thu, 29 Aug 2024 13:31:44 +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 1sjfFX-002Oed-Ay for pgsql-general@lists.postgresql.org; Thu, 29 Aug 2024 13:31:44 +0000 Received: from mail-yb1-xb2d.google.com ([2607:f8b0:4864:20::b2d]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1sjfFV-0021CK-12 for pgsql-general@postgresql.org; Thu, 29 Aug 2024 13:31:42 +0000 Received: by mail-yb1-xb2d.google.com with SMTP id 3f1490d57ef6-dff1ccdc17bso753263276.0 for ; Thu, 29 Aug 2024 06:31:40 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1724938300; x=1725543100; darn=postgresql.org; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=i1pRrhGfgyFhmHM3pHbaAd9umxqbDerOkbcJddEJ4Tg=; b=WbWf3h6uPag6zxPbIEauaOgkKtoteGAB60AUrnRK97iH4Wsk2fc5OrsAQ8ItKAXvdH bWDAsMixWemqiyW+Bi98BhzSXUCUqTNrErBAa5//OJctw3VPcMLlFkDNuMfr1k+y7UhS XcJAJG60+qCDMy2GE8Bo4H4LBeXlRuS0AIQNaDPDTrb8tm39e9/iLg1YYUH+bI2Lpnzd wkSEvg3FurOQswGrBK4t0GFtxJXTtkz0M5qJngLj1zAQefS8oGSR+npTMVKCJWEW5ELT +T8jucboqpf/O+obPnzjsQGjL9ldfQSN/5lhfa4OPNA+Cb5bSMReTQsRCHp8GSRGeM9y j4Lg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1724938300; x=1725543100; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=i1pRrhGfgyFhmHM3pHbaAd9umxqbDerOkbcJddEJ4Tg=; b=WX1cy7IId0+YoRCJVWFomsxBnQ3vBKM6wzsZ7wIcr/ua6OHNiG8yho16R8QPT+kLp3 B8ZCevPeWY3nD53r/83TvEtAZ+At7eh1aEXVXmz//9/L+S4M2kvyo9ma7qVcmMDyWLON twkkXnSyEZNFJdppTRZDa2Pm31o2AuHLG9TAK6Mo/hteI+y88Ssd9TRjmhfNLKPM4Y35 AwHk4Paboi0PlR7kKuN6TlCU4EunUMepOWIb6wzRwL6H6YGFA8YXcupSAJNO0msv1l+P ksDPqOGyTXQhXImXBYS9G/cVLEpIWvimjb4Hu3doUCDCXG8tWzZHLJs7VW/xmPhkdUbh YS0g== X-Gm-Message-State: AOJu0YyW0vwQA7+hBbq4CnF4SKXhPe7+oALm+sCA5vTJ9Ko6TIhbldG3 mz35VncAj3k6s+BvY/uQmEaNB1qBrwyjQugQr4ezqUn8IXGMzZlmb98TPkA33EmxiLXhGRCuWIA r3ofV5kiZIdVnmmvg9IjFmPE9NSTRYzNS X-Google-Smtp-Source: AGHT+IEtHy7LQ+Xa0YpmF3pj6h/4VFcJev3AZDkV9uyEjzFG43GqMtWrjQLtc55n3eIrzmJfuDCWTw43WZTeNMJ0s+M= X-Received: by 2002:a05:6902:726:b0:e13:ceaa:59d9 with SMTP id 3f1490d57ef6-e1a5ae01ff5mr3309201276.41.1724938299905; Thu, 29 Aug 2024 06:31:39 -0700 (PDT) MIME-Version: 1.0 From: KK CHN Date: Thu, 29 Aug 2024 19:01:48 +0530 Message-ID: Subject: PgBackRest client_loop: send disconnect: Connection reset To: pgsql-general Content-Type: multipart/alternative; boundary="000000000000a021a40620d27e7f" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000a021a40620d27e7f Content-Type: text/plain; charset="UTF-8" List, I am facing an Error : on a connection reset while PgBackRest is doing backup process for DB server to Repo Server. But the reissue of the pgbackrest backup command fails as follows... "Unable to acquire lock on file '/tmp/pgbackrest/Repo-backup.lock': Resource temporarily unavailable HINT: is another pgBackRest process running? After multiple attempts and during 8 to 10 minutes, the backup command from RepoServer starts working again.. How to avoid /what is the exact reason for "Resource temporarily unavailable"? HINT : Is another PgBackRest process running ? Please advise .. On Connection reset then issuing backup command I get out puts as below. ###################################################################### [root@dbtest ~]# sudo -u postgres pgbackrest --stanza=Repo --log-level-console=info backup 2024-08-29 16:38:13.922 P00 INFO: backup command begin 2.52.1: --delta --exec-id=658924-527c843b --log-level-console=info --log-level-file=debug --pg1-host=10.15.0.202 --pg1-host-user=enterprisedb --pg1-path=/data/edb/as16/data --pg-version-force=16 --process-max=5 --repo1-block --repo1-bundle --repo1-cipher-pass= --repo1-cipher-type=aes-256-cbc --repo1-path=/data/DB_BKUPS --repo1-retention-diff=2 --repo1-retention-full=2 --stanza=Repo --start-fast WARN: no prior backup exists, incr backup has been changed to full 2024-08-29 16:38:16.745 P00 INFO: execute non-exclusive backup start: backup begins after the requested immediate checkpoint completes 2024-08-29 16:38:18.003 P00 INFO: backup start archive = 00000001000000850000009A, lsn = 85/9A0000D8 2024-08-29 16:38:18.003 P00 INFO: check archive for prior segment 000000010000008500000099 WARN: resumable backup 20240829-105625F of same type exists -- invalid files will be removed then the backup will resume client_loop: send disconnect: Connection reset [root@dbtest ~]# sudo -u postgres pgbackrest --stanza=Repo --log-level-console=info backup 2024-08-29 18:45:06.630 P00 INFO: backup command begin 2.52.1: --delta --exec-id=691718-6c37ff5c --log-level-console=info --log-level-file=debug --pg1-host=10.15.0.202 --pg1-host-user=enterprisedb --pg1-path=/data/edb/as16/data --pg-version-force=16 --process-max=5 --repo1-block --repo1-bundle --repo1-cipher-pass= --repo1-cipher-type=aes-256-cbc --repo1-path=/data/DB_BKUPS --repo1-retention-diff=2 --repo1-retention-full=2 --stanza=Repo --start-fast ERROR: [050]: unable to acquire lock on file '/tmp/pgbackrest/Repo-backup.lock': Resource temporarily unavailable HINT: is another pgBackRest process running? 2024-08-29 18:45:06.631 P00 INFO: backup command end: aborted with exception [050] [root@dbtest ~]# sudo -u postgres pgbackrest --stanza=Repo --log-level-console=info backup 2024-08-29 18:45:14.531 P00 INFO: backup command begin 2.52.1: --delta --exec-id=691730-06e11989 --log-level-console=info --log-level-file=debug --pg1-host=10.15.0.202 --pg1-host-user=enterprisedb --pg1-path=/data/edb/as16/data --pg-version-force=16 --process-max=5 --repo1-block --repo1-bundle --repo1-cipher-pass= --repo1-cipher-type=aes-256-cbc --repo1-path=/data/DB_BKUPS --repo1-retention-diff=2 --repo1-retention-full=2 --stanza=Repo --start-fast ERROR: [050]: unable to acquire lock on file '/tmp/pgbackrest/Repo-backup.lock': Resource temporarily unavailable HINT: is another pgBackRest process running? 2024-08-29 18:45:14.531 P00 INFO: backup command end: aborted with exception [050] ########################################################################### After 10 minutes or so I issued the command again as follows it starts backing up as follows ? 2024-08-29 18:48:19.561 P00 INFO: backup command end: aborted with exception [050] [root@dbtest ~]# sudo -u postgres pgbackrest --stanza=Repo --log-level-console=info backup 2024-08-29 18:52:33.834 P00 INFO: backup command begin 2.52.1: --delta --exec-id=693517-4994fba1 --log-level-console=info --log-level-file=debug --pg1-host=10.15.0.202 --pg1-host-user=enterprisedb --pg1-path=/data/edb/as16/data --pg-version-force=16 --process-max=5 --repo1-block --repo1-bundle --repo1-cipher-pass= --repo1-cipher-type=aes-256-cbc --repo1-path=/data/DB_BKUPS_NGERSS --repo1-retention-diff=2 --repo1-retention-full=2 --stanza=Repo --start-fast WARN: no prior backup exists, incr backup has been changed to full 2024-08-29 18:52:36.813 P00 INFO: execute non-exclusive backup start: backup begins after the requested immediate checkpoint completes 2024-08-29 18:52:37.788 P00 INFO: backup start archive = 000000010000008600000063, lsn = 86/63000028 2024-08-29 18:52:37.788 P00 INFO: check archive for prior segment 000000010000008600000062 WARN: resumable backup 20240829-105625F of same type exists -- invalid files will be removed then the backup will resume Thank you, Krishane --000000000000a021a40620d27e7f Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
List,=C2=A0

I am facing an E= rror :=C2=A0 on a connection reset while=C2=A0 PgBackRest is doing backup p= rocess for DB server to Repo Server.=C2=A0

But the= reissue of the=C2=A0 =C2=A0 =C2=A0pgbackrest backup=C2=A0 command=C2=A0 fa= ils as follows...=C2=A0

"Unable to acquire lo= ck on file '/tmp/pgbackrest/Repo-backup.lock': Resource temporarily= unavailable=C2=A0 =C2=A0 =C2=A0 =C2=A0 HINT: is another pgBackRest process= running?


After multiple attempts= =C2=A0and=C2=A0 during=C2=A0 8 to 10 minutes,=C2=A0 =C2=A0the backup comman= d from RepoServer starts working again..=C2=A0 =C2=A0 How to avoid /what is= the exact reason for=C2=A0 =C2=A0"Resource temporarily unavailable&qu= ot;?=C2=A0 HINT : Is another PgBackRest process running ?


Please advise ..=C2=A0 =C2=A0

On Connection reset then issuing backup command I get out puts=C2=A0as b= elow.=C2=A0


#######################= ###############################################

[root@d= btest ~]# sudo -u postgres pgbackrest --stanza=3DRepo --log-level-console= =3Dinfo backup
2024-08-29 16:38:13.922 P00 =C2=A0 INFO: backup command b= egin 2.52.1: --delta --exec-id=3D658924-527c843b --log-level-console=3Dinfo= --log-level-file=3Ddebug --pg1-host=3D10.15.0.202 --pg1-host-user=3Denterp= risedb --pg1-path=3D/data/edb/as16/data --pg-version-force=3D16 --process-m= ax=3D5 --repo1-block --repo1-bundle --repo1-cipher-pass=3D<redacted> = --repo1-cipher-type=3Daes-256-cbc --repo1-path=3D/data/DB_BKUPS --repo1-ret= ention-diff=3D2 --repo1-retention-full=3D2 --stanza=3DRepo --start-fast
= WARN: no prior backup exists, incr backup has been changed to full
2024-= 08-29 16:38:16.745 P00 =C2=A0 INFO: execute non-exclusive backup start: bac= kup begins after the requested immediate checkpoint completes
2024-08-29= 16:38:18.003 P00 =C2=A0 INFO: backup start archive =3D 0000000100000085000= 0009A, lsn =3D 85/9A0000D8
2024-08-29 16:38:18.003 P00 =C2=A0 INFO: chec= k archive for prior segment 000000010000008500000099
WARN: resumable bac= kup 20240829-105625F of same type exists -- invalid files will be removed t= hen the backup will resume
client_loop: send disconnect: Connection reset


[root@d= btest ~]# sudo -u postgres pgbackrest --stanza=3DRepo --log-level-console= =3Dinfo backup
2024-08-29 18:45:06.630 P00 =C2=A0 INFO: backup command b= egin 2.52.1: --delta --exec-id=3D691718-6c37ff5c --log-level-console=3Dinfo= --log-level-file=3Ddebug --pg1-host=3D10.15.0.202 --pg1-host-user=3Denterp= risedb --pg1-path=3D/data/edb/as16/data --pg-version-force=3D16 --process-m= ax=3D5 --repo1-block --repo1-bundle --repo1-cipher-pass=3D<redacted> = --repo1-cipher-type=3Daes-256-cbc --repo1-path=3D/data/DB_BKUPS --repo1-ret= ention-diff=3D2 --repo1-retention-full=3D2 --stanza=3DRepo --start-fast
= ERROR: [050]: unable to acquire lock on file '/tmp/pgbackrest/Repo-back= up.lock': Resource temporarily unavailable
=C2=A0 =C2=A0 =C2=A0 =C2= =A0HINT: is another pgBackR= est process running?

2024-08-29 18:45:06.631 P00 =C2=A0 INFO:= backup command end: aborted with exception [050]
[root@dbtest ~]# sudo = -u postgres pgbackrest --stanza=3DRepo --log-level-console=3Dinfo backup2024-08-29 18:45:14.531 P00 =C2=A0 INFO: backup command begin 2.52.1: --de= lta --exec-id=3D691730-06e11989 --log-level-console=3Dinfo --log-level-file= =3Ddebug --pg1-host=3D10.15.0.202 --pg1-host-user=3Denterprisedb --pg1-path= =3D/data/edb/as16/data --pg-version-force=3D16 --process-max=3D5 --repo1-bl= ock --repo1-bundle --repo1-cipher-pass=3D<redacted> --repo1-cipher-ty= pe=3Daes-256-cbc --repo1-path=3D/data/DB_BKUPS --repo1-retention-diff=3D2 -= -repo1-retention-full=3D2 --stanza=3DRepo --start-fast
ERROR: [050]: una= ble to acquire lock on file '/tmp/pgbackrest/Repo-backup.lock': Res= ource temporarily unavailable
=C2=A0 =C2=A0 =C2=A0 =C2=A0HINT: is anothe= r pgBackRest process running?
2024-08-29 18:45:14.531 P00 =C2=A0 INFO: b= ackup command end: aborted with exception [050]

####= #######################################################################
After 10 minutes or so I issued the command again as follows it star= ts backing up as follows=C2=A0 ?



2024-08-29 18:48:19.561 P00 =C2=A0 INFO: backup command en= d: aborted with exception [050]
[root@dbtest ~]# sudo -u postgres pgback= rest --stanza=3DRepo --log-level-console=3Dinfo backup
2024-08-29 18:52:= 33.834 P00 =C2=A0 INFO: backup command begin 2.52.1: --delta --exec-id=3D69= 3517-4994fba1 --log-level-console=3Dinfo --log-level-file=3Ddebug --pg1-hos= t=3D10.15.0.202 --pg1-host-user=3Denterprisedb --pg1-path=3D/data/edb/as16/= data --pg-version-force=3D16 --process-max=3D5 --repo1-block --repo1-bundle= --repo1-cipher-pass=3D<redacted> --repo1-cipher-type=3Daes-256-cbc -= -repo1-path=3D/data/DB_BKUPS_NGERSS --repo1-retention-diff=3D2 --repo1-rete= ntion-full=3D2 --stanza=3DRepo --start-fast
WARN: no prior backup exists= , incr backup has been changed to full
2024-08-29 18:52:36.813 P00 =C2= =A0 INFO: execute non-exclusive backup start: backup begins after the reque= sted immediate checkpoint completes
2024-08-29 18:52:37.788 P00 =C2=A0 I= NFO: backup start archive =3D 000000010000008600000063, lsn =3D 86/63000028=
2024-08-29 18:52:37.788 P00 =C2=A0 INFO: check archive for prior segmen= t 000000010000008600000062
WARN: resumable backup 20240829-105625F of sa= me type exists -- invalid files will be removed then the backup will resume=


Thank you,
Krishane<= /div>
--000000000000a021a40620d27e7f--