Message-ID: <2874e719d29908405c46ddd4273222aa3544afde.camel@cybertec.at>
Subject: Re: fails to start - pg_stat_tmp ?
From: Laurenz Albe <laurenz.albe@cybertec.at>
To: lejeczek <peljasz@yahoo.co.uk>, pgsql-admin@lists.postgresql.org
Date: Fri, 10 Nov 2023 13:20:19 +0100
In-Reply-To: <3c1964cc-ac89-4378-9b4f-841d8cb0fe01@yahoo.co.uk>
References: <3c1964cc-ac89-4378-9b4f-841d8cb0fe01.ref@yahoo.co.uk>
	 <3c1964cc-ac89-4378-9b4f-841d8cb0fe01@yahoo.co.uk>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
User-Agent: Evolution 3.48.4 (3.48.4-1.fc38) 
MIME-Version: 1.0
Archived-At: 
 <https://www.postgresql.org/message-id/2874e719d29908405c46ddd4273222aa3544afde.camel%40cybertec.at>
Precedence: bulk

On Fri, 2023-11-10 at 11:33 +0100, lejeczek wrote:
> I have simple cluster managed by a popular toolset, I believe, and I get =
a standby/slave node which
> after it was shutdown, rebooted, is unable to start, not by the that clus=
ter-manager nor manually.

Thatks for telling us all the detail...

> =C2=A0FATAL:=C2=A0 could not open directory "/var/run/postgresql/14-paf.p=
g_stat_tmp": No such file or directory
> =C2=A0LOG:=C2=A0 startup process (PID 54860) exited with exit code 1
>=20
> Indeed that dir, that path does not exist on the node - from what I can s=
ee, among the nodes
> comprising the cluster this path exists only on the _master_ node.

Looks like somebody randomly deleted directories on that machine.

Create it again, and make sure it belongs to the postgres user and
nobody else has write access.

Yours,
Laurenz Albe