Find cause for Primary failover

Skip to first unread message

Tamar Nirenberg

May 9, 2021, 5:16:12 AMMay 9
to repmgr


My Primary performed a failover to the standby.
This is what I see in the logs:

WARNING:  terminating connection because of crash of another server process
DETAIL:  The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory.
HINT:  In a moment you should be able to reconnect to the database and repeat your command.
[2021-05-09 05:34:21] [WARNING] unable to ping "user=octepmgr password=xxx host= dbname=repmgr port=5000 connect_timeout=5"
[2021-05-09 05:34:21] [DETAIL] PQping() returned "PQPING_NO_RESPONSE"
[2021-05-09 05:34:21] [WARNING] connection to node "octopuspg-0" (ID: 1000) lost
[2021-05-09 05:34:21] [DETAIL]
server closed the connection unexpectedly
        This probably means the server terminated abnormally
        before or while processing the request.

How can I determine what caused this?

I can see nothing in the server /var/log/messages for the crash time (the server is Debian 10)


Ian Barwick

May 26, 2021, 7:53:29 PMMay 26
to, Tamar Nirenberg
Have you tried looking in the PostgreSQL logs?


Ian Barwick

Ian Barwick
PostgreSQL Development, 24x7 Support, Training & Services
Reply all
Reply to author
0 new messages