Re: BUG #17954: Postgres startup fails with `could not locate a valid checkpoint record`

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: srivastavautkarsh8097(at)gmail(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #17954: Postgres startup fails with `could not locate a valid checkpoint record`
Date: 2023-06-12 04:56:21
Message-ID: ZIaldUjDrK8D45db@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Thu, Jun 01, 2023 at 01:11:20PM +0000, PG Bug reporting form wrote:
> - What could be the root cause of this issue?
> - Is this a known issue (I did search the archives but couldn't find it
> though)? If yes, is this fixed in a PG 13, 14, 15?

Hard to say for sure, but it looks like your host has a few problems.
This part from your logs refers to something that should not happen,
to begin with:

> 2023-05-14 05:13:13.678 UTC [1] LOG: received smart shutdown request
> 2023-05-14 05:13:36.692 UTC [1] LOG: could not open file "postmaster.pid":
> No such file or directory
> 2023-05-14 05:13:36.692 UTC [1] LOG: performing immediate shutdown because
> data directory lock file is invalid
> 2023-05-14 05:13:36.692 UTC [1] LOG: received immediate shutdown request
> 2023-05-14 05:13:36.692 UTC [1] LOG: could not open file "postmaster.pid":
> No such file or directory

This LOG would come from either AddToDataDirLockFile() or
RecheckDataDirLockFile(). Still, the third entry I am quoting refers
to a recheck of the PID file, meaning that the postmaster has bumped
into what looks like a corrupted PID file.
--
Michael

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Michael Paquier 2023-06-12 05:04:53 Re: Server crash with parallel workers with Postgres 14.7
Previous Message Michael Paquier 2023-06-12 01:28:33 Re: BUG #17953: Libpq can stall indefinitely with non-tls localhost (127.0.0.1) connection