Re: Failover Testing Failures: invalid resource manager ID in primary checkpoint record

From: Don Seiler <don(at)seiler(dot)us>
To: Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>
Cc: pgsql-admin <pgsql-admin(at)postgresql(dot)org>
Subject: Re: Failover Testing Failures: invalid resource manager ID in primary checkpoint record
Date: 2023-01-19 15:57:17
Message-ID: CAHJZqBABdEP-kzBAfQEnoeYAgx3R87tOkm+7AfOqCz3iUGEw=w@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

On Thu, Jan 19, 2023 at 9:50 AM Don Seiler <don(at)seiler(dot)us> wrote:

> I'm going to have to review what chef might have done. I was relying on
> chef to deploy the configs before attempting to restart but it may have
> tried to start the service early
>

Reviewing the chef recipe, this does seem to be the case. The code
to determine whether or not to place the standby.signal file comes after it
already attempts to start the PG service. Another self-inflicted wound
apparently.

Don.
--
Don Seiler
www.seiler.us

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Don Seiler 2023-01-19 17:23:23 Re: Failover Testing Failures: invalid resource manager ID in primary checkpoint record
Previous Message Don Seiler 2023-01-19 15:50:34 Re: Failover Testing Failures: invalid resource manager ID in primary checkpoint record