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 1sjgR9-002x1j-08 for pgsql-general@arkaria.postgresql.org; Thu, 29 Aug 2024 14:47: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 1sjgR6-003MOn-SL for pgsql-general@arkaria.postgresql.org; Thu, 29 Aug 2024 14:47:45 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sjgR6-003MOe-F1 for pgsql-general@lists.postgresql.org; Thu, 29 Aug 2024 14:47:45 +0000 Received: from mail-ot1-x331.google.com ([2607:f8b0:4864:20::331]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1sjgQz-00263A-Bm for pgsql-general@postgresql.org; Thu, 29 Aug 2024 14:47:44 +0000 Received: by mail-ot1-x331.google.com with SMTP id 46e09a7af769-70941cb73e9so310428a34.2 for ; Thu, 29 Aug 2024 07:47:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1724942856; x=1725547656; darn=postgresql.org; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :from:to:cc:subject:date:message-id:reply-to; bh=lwJGKCiKr/08SXt22ebw1V5o4S+JMeSvPPSJcUtbc/0=; b=XJVpFc8wTQaF1ybtIb7bP1bijFrCIHNxzCIhZJVxRsaQWHY1B5jcc7jBMBrXzmEYmY wA8uBvFXdjleF9Tov/wn5JwNRX/h5xaXtFdYY4bvAMTBr087VTHWq8AdAPIsk0UD3aC2 VBTpIkgt1X3YqsJJHyYa8vILkUkqVzmMTjItbNjmrP8RgrwZIukEWhTm8ivJE2urqkxv rx1ME0nY9f5Cion+ykk9/qzyICdI4hp9U0iOH0q4PpLsM6+Gz8IPLN/EpleGRgqFhf/N SMs6hrIya7vfS6zpmumVCnilXmqWdt9XQpLJE5Z8aBGNI6snLkClbsb5wtaW8UNJmiqN ShQA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1724942856; x=1725547656; h=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=lwJGKCiKr/08SXt22ebw1V5o4S+JMeSvPPSJcUtbc/0=; b=ly7ZuEr+cSqNAcALUmqsdnG2Qoj45tWMRNJramrDvBftqgY1BTMwv6KIe1/KRLHqut atC+FZiJz5tmsySWOyquWv+9q7bTlRc6Aro5Ggtpmz5aSMTrx6BWb6+RBdCPAQaiKnnC o4U8CbZM8QtAPu8nWtVGvNWR3UeqFc83IOKmct8vyh9nTgjn/3hoVyj8GSNznMEa3w4o 5egJmjpBmwfi2aAjF+bpl/6y2AP9RKYNTxPLWCCYF6M8giNEhqv310p1OSoHTERqmdn7 y6QWPzcwsVWHswhzXeea0lE4atmOm5nxc6rdu371OCI5NAlf0LgFa5R5t3mIT4VRGNuL wBZw== X-Gm-Message-State: AOJu0YwdmAziQMVtM4is5LsDsPLbRHt9PNRq9tSr/12/mtogSObBgpq7 40QTsLyjNibjlBhEIevzSHwjqg95k9VxcusZN3nR4VPS+6qVArXjBYA0cmXwDU5QSMB9LMoL7+a 8/kxQGd6Dt5wuWCBQB4L5BNJ1RhydAg== X-Google-Smtp-Source: AGHT+IHEU1BZXpGLmXndtPyYOGlvKLyZzEuOC4NCU3ClHp29+WGPSiKF/+LKqyq/Dddn5fKjkvXKlwq4xX6kPX4E6ZE= X-Received: by 2002:a05:6808:2182:b0:3d9:30a2:f8f1 with SMTP id 5614622812f47-3df05c4d65amr2842155b6e.8.1724942856245; Thu, 29 Aug 2024 07:47:36 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Ron Johnson Date: Thu, 29 Aug 2024 10:47:23 -0400 Message-ID: Subject: Re: PgBackRest client_loop: send disconnect: Connection reset To: pgsql-general Content-Type: multipart/alternative; boundary="0000000000003458f30620d38eb5" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --0000000000003458f30620d38eb5 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Thu, Aug 29, 2024 at 10:12=E2=80=AFAM Greg Sabino Mullane wrote: > On Thu, Aug 29, 2024 at 9:31=E2=80=AFAM KK CHN 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.) --=20 Death to America, and butter sauce. Iraq lobster! --0000000000003458f30620d38eb5 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Thu, Aug 29, 2024 at 10:12=E2=80=AFAM = Greg Sabino Mullane <htamfids@gmai= l.com> wrote:
On Thu, = Aug 29, 2024 at 9:31=E2=80=AFAM KK CHN <kkchn.in@gmail.com> wrote:
"Unable to acquire lock on file '/tmp/pgbackrest/R= epo-backup.lock'

When this = happens, take a look inside this file. If there is another pgbackrest proce= ss running, the pid will be inside that file. Kill that process before tryi= ng to run another backup.

Or don't run pgbackrest when another instance is running.= =C2=A0 This is what I do:
pgrep -a pgbackrest | grep -q "pgbackres= t backup" && { echo "another pgbackrest back is running&q= uot;; exit 1; }

(There's probably a b= etter way to check that, but this works.)

--
Death to America, and butter sauce.
Iraq lob= ster!
--0000000000003458f30620d38eb5--