From: | Ron Johnson <ronljohnsonjr(at)gmail(dot)com> |
---|---|
To: | pgsql-general <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: PgBackRest client_loop: send disconnect: Connection reset |
Date: | 2024-08-29 14:47:23 |
Message-ID: | CANzqJaCR28GEWA_NsfBwzpFJpjakKcX5HsPT9=N+VPpsdRGamA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Thu, Aug 29, 2024 at 10:12 AM Greg Sabino Mullane <htamfids(at)gmail(dot)com>
wrote:
> On Thu, Aug 29, 2024 at 9:31 AM KK CHN <kkchn(dot)in(at)gmail(dot)com> wrote:
>
>> "Unable to acquire lock on file '/tmp/pgbackrest/Repo-backup.lock'
>>
>
> When this happens, take a look inside this file. If there is another
> pgbackrest process running, the pid will be inside that file. Kill that
> process before trying to run another backup.
>
Or don't run pgbackrest when another instance is running. This is what I
do:
pgrep -a pgbackrest | grep -q "pgbackrest backup" && { echo "another
pgbackrest back is running"; exit 1; }
(There's probably a better way to check that, but this works.)
--
Death to America, and butter sauce.
Iraq lobster!
From | Date | Subject | |
---|---|---|---|
Next Message | KK CHN | 2024-08-29 16:07:39 | Re: PgBackRest Full backup and N/W reliability |
Previous Message | Greg Sabino Mullane | 2024-08-29 14:11:26 | Re: PgBackRest client_loop: send disconnect: Connection reset |