Content-Type: multipart/alternative;
 boundary="------------ZtfUHmiikln1G0LuKeWFIsTk"
Message-ID: <3c1964cc-ac89-4378-9b4f-841d8cb0fe01@yahoo.co.uk>
Date: Fri, 10 Nov 2023 11:33:31 +0100
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
To: pgsql-admin@lists.postgresql.org
Content-Language: en-US
From: lejeczek <peljasz@yahoo.co.uk>
Subject: fails to start - pg_stat_tmp ?
References: <3c1964cc-ac89-4378-9b4f-841d8cb0fe01.ref@yahoo.co.uk>
Content-Length: 5092
Archived-At: 
 <https://www.postgresql.org/message-id/3c1964cc-ac89-4378-9b4f-841d8cb0fe01%40yahoo.co.uk>
Precedence: bulk

This is a multi-part message in MIME format.
--------------ZtfUHmiikln1G0LuKeWFIsTk
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit

Hi guys.

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 
cluster-manager nor manually.
I get:
...
2023-11-10 10:18:45.491 UTC [54858] LOG:  starting 
PostgreSQL 14.9 (Ubuntu 14.9-0ubuntu0.22.04.1) on 
x86_64-pc-linux-gnu, compiled by gcc (Ubuntu 
11.4.0-1ubuntu1~22.04) 11.4.0, 64-bit
2023-11-10 10:18:45.491 UTC [54858] LOG:  listening on IPv4 
address "0.0.0.0", port 5433
2023-11-10 10:18:45.491 UTC [54858] LOG:  listening on IPv6 
address "::", port 5433
2023-11-10 10:18:45.495 UTC [54858] LOG:  listening on Unix 
socket "/var/run/postgresql/.s.PGSQL.5433"
2023-11-10 10:18:45.505 UTC [54860] LOG:  database system 
was interrupted while in recovery at log time 2023-11-10 
09:53:18 UTC
2023-11-10 10:18:45.505 UTC [54860] HINT:  If this has 
occurred more than once some data might be corrupted and you 
might need to choose an earlier recovery target.
2023-11-10 10:18:45.540 UTC [54862] 
drwszelakiadmmdisc@drwszelaki_discourse FATAL:  the database 
system is starting up
2023-11-10 10:18:45.545 UTC [54863] 
drwszelakiadmmdisc@drwszelaki_discourse FATAL:  the database 
system is starting up
2023-11-10 10:18:45.795 UTC [54860] LOG:  entering standby mode
2023-11-10 10:18:45.799 UTC [54860] FATAL:  could not open 
directory "/var/run/postgresql/14-paf.pg_stat_tmp": No such 
file or directory
2023-11-10 10:18:45.800 UTC [54858] LOG:  startup process 
(PID 54860) exited with exit code 1
2023-11-10 10:18:45.800 UTC [54858] LOG:  aborting startup 
due to startup process failure
2023-11-10 10:18:45.802 UTC [54858] LOG:  database system is 
shut down


Indeed that dir, that path does not exist on the node - from 
what I can see, among the nodes comprising the cluster this 
path exists only on the _master_ node.

What would that specific errors be suggesting or meaning - 
do I have something mis-configured, perhaps the toolset 
itself does not deal with "mere" reboot well, or at all.
Toolset is HA/pcs(pacemaker) cluster tools.

many thanks, L.
--------------ZtfUHmiikln1G0LuKeWFIsTk
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 8bit

<!DOCTYPE html>
<html>
  <head>

    <meta http-equiv="content-type" content="text/html; charset=UTF-8">
  </head>
  <body>
    <font size="2" face="Courier 10 Pitch">Hi guys.<br>
      <br>
      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 cluster-manager nor manually.<br>
      I get:<br>
      ...<br>
      2023-11-10 10:18:45.491 UTC [54858] LOG:  starting PostgreSQL 14.9
      (Ubuntu 14.9-0ubuntu0.22.04.1) on x86_64-pc-linux-gnu, compiled by
      gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0, 64-bit<br>
      2023-11-10 10:18:45.491 UTC [54858] LOG:  listening on IPv4
      address "0.0.0.0", port 5433<br>
      2023-11-10 10:18:45.491 UTC [54858] LOG:  listening on IPv6
      address "::", port 5433<br>
      2023-11-10 10:18:45.495 UTC [54858] LOG:  listening on Unix socket
      "/var/run/postgresql/.s.PGSQL.5433"<br>
      2023-11-10 10:18:45.505 UTC [54860] LOG:  database system was
      interrupted while in recovery at log time 2023-11-10 09:53:18 UTC<br>
      2023-11-10 10:18:45.505 UTC [54860] HINT:  If this has occurred
      more than once some data might be corrupted and you might need to
      choose an earlier recovery target.<br>
      2023-11-10 10:18:45.540 UTC [54862]
      drwszelakiadmmdisc@drwszelaki_discourse FATAL:  the database
      system is starting up<br>
      2023-11-10 10:18:45.545 UTC [54863]
      drwszelakiadmmdisc@drwszelaki_discourse FATAL:  the database
      system is starting up<br>
      2023-11-10 10:18:45.795 UTC [54860] LOG:  entering standby mode<br>
      2023-11-10 10:18:45.799 UTC [54860] FATAL:  could not open
      directory "/var/run/postgresql/14-paf.pg_stat_tmp": No such file
      or directory<br>
      2023-11-10 10:18:45.800 UTC [54858] LOG:  startup process (PID
      54860) exited with exit code 1<br>
      2023-11-10 10:18:45.800 UTC [54858] LOG:  aborting startup due to
      startup process failure<br>
      2023-11-10 10:18:45.802 UTC [54858] LOG:  database system is shut
      down<br>
      <br>
      <br>
      Indeed that dir, that path does not exist on the node - from what
      I can see, among the nodes comprising the cluster this path exists
      only on the _master_ node.<br>
      <br>
      What would that specific errors be suggesting or meaning - do I
      have something mis-configured, perhaps the toolset itself does not
      deal with "mere" reboot well, or at all.<br>
      Toolset is HA/pcs(pacemaker) cluster tools.<br>
      <br>
      many thanks, L.<br>
    </font>
  </body>
</html>

--------------ZtfUHmiikln1G0LuKeWFIsTk--