Database system was interrupted. Possible reasons for a database to suddenly stop accepting connections?

From: "Buzenets, Yuriy (GE Renewable Energy, consultant)" <Yuriy(dot)Buzenets(at)ge(dot)com>
To: "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>
Subject: Database system was interrupted. Possible reasons for a database to suddenly stop accepting connections?
Date: 2020-11-09 13:53:28
Message-ID: AM0P101MB03375FAC5F568D3C62E826BCF3EA0@AM0P101MB0337.NAMP101.PROD.OUTLOOK.COM
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Some time ago the database at my work suddenly stopped accepting connections. In the logs there was a message "the database system was interrupted; last known up at 2020-10-29 12:03:16 PDT", followed by a lot of "the database system is starting up" messages. It seems like the database tried to recover from whatever failure occurred but recovery was not successful until the database process was shut down and restarted. The latest error message before "system was interrupted" occurs 13 minutes before so it's not clear to us what could cause this issue and why the database process had to be restarted. If anyone could help us understand what might've been the cause, we would greatly appreciate it. We're using PostgreSQL 9.4 on CentOS 6.8, we know it reached EOL and plan to upgrade to a newer version soon. I've also attached the log file from the time the database system was unavailable if it helps to figure out the cause of the outage

Thanks,
Yuriy Buzenets

Attachment Content-Type Size
postgresql-Thu.log application/octet-stream 92.1 KB

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Pavel Stehule 2020-11-09 14:20:48 Re: RAISE INFO in function
Previous Message Yambu 2020-11-09 13:46:06 RAISE INFO in function