Azure Database for PostgreSQL
An Azure managed PostgreSQL database service for app development and deployment.
1,207 questions
Azure Database for PostgreSQL - Flexible Server unavailable twice a day
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(259.20000000000005, 11%, 35%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EMG%3C/text%3E%3C/svg%3E)
Martin Gubis
0
Reputation points
We are running Azure Database for PostgreSQL - Flexible Server. According to the metrics, the system is not under heavy load at all (memory is constantly at approx. 60%, CPU 12% with no peaks). Database is not available approx. twice a day - this problem is documented in the Activity log of the Resource as Health event (details: "An unexpected problem is preventing restoring access to your Azure Database for PostgreSQL - Flexible server. We are working on resolving the problem."). The problem lasts for couple of minutes - and of course disrupts all requests made to our application.
Is there any way to report this problem to Microsoft (we don't have support plan for Technical assistance)? Do you have any idea, what can be done to fix this problem?
Thank you for the assistance.
{count} votes
-
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(19.2, 46%, 11%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ETB%3C/text%3E%3C/svg%3E)
Taduturu Balaji 0 Reputation points Microsoft Vendor2025-02-21T07:53:21.2+00:00 Hi @Martin Gubis ,
Follow below steps to troubleshoot your issue.
- Check for Scheduled Maintenance or Known Issues:
- Visit Azure Service Health to check if there are any ongoing incidents or planned maintenance for your region.
- Also check the Azure status page to see if other users are reporting similar PostgreSQL issues.
- Review Server Logs and Diagnostic Settings:
- Query Performance Insights: Look at long-running queries and deadlocks that might cause database unavailability.
- Check the Server Logs: Enable Query Store and Slow Query Logs to see if there are problematic queries around the downtime.
- Investigate High Availability (HA) and Failover Events:
- If you have Geo-Redundant HA enabled, Azure might be failing over between instances. Run SELECT * FROM pg_stat_activity; during a failure to check active connections. Also check failover events using - SELECT * FROM pg_stat_replication;
I hope this information helps. Please do let us know if you have any further queries.
Kindly consider upvoting the comment if the information provided is helpful. This can assist other community members in resolving similar issues.
- Check for Scheduled Maintenance or Known Issues:
-
Martin Gubis 0 Reputation points
2025-02-21T09:38:00.26+00:00 Thank you very much for the response. I've turned on Server Logs with verbosity INFO. Logging of the queries is not enabled, but I think, that the Server Logs gives the strong hint pointing to the problems with connectivity. There are no special entries in the time of outage (like the database is restarting or having any other difficulties), but there are entries showing the problem with network:
2025-02-21 08:20:43 UTC-67b8375a.713d-LOG: connection received: host=XXX.XXX.XXX.X port=49202 2025-02-21 08:20:43 UTC-67b8375a.713e-LOG: connection received: host=XXX.XXX.XXX.X port=49210 2025-02-21 08:20:48 UTC-67b8375e.7140-LOG: connection received: host=XXX.XXX.XXX.X port=33610 2025-02-21 08:20:57 UTC-67b83767.7141-LOG: connection received: host=XX.XXX.X.XXX port=52144 2025-02-21 08:20:57 UTC-67b83767.7142-LOG: connection received: host=XX.XXX.X.XXX port=52152 2025-02-21 08:21:06 UTC-67b83770.7144-LOG: connection received: host=XX.XXX.X.XXX port=52166 2025-02-21 08:21:09 UTC-67b83767.7142-LOG: could not accept SSL connection: EOF detected 2025-02-21 08:21:09 UTC-67b83767.7141-LOG: could not accept SSL connection: EOF detected 2025-02-21 08:21:09 UTC-67b836dd.7021-LOG: could not receive data from client: Connection reset by peer 2025-02-21 08:21:09 UTC-67b836dd.7021-LOG: unexpected EOF on client connection with an open transaction 2025-02-21 08:21:09 UTC-67b83775.7145-LOG: connection received: host=XX.XXX.X.XXX port=38724 2025-02-21 08:21:09 UTC-67b83775.7146-LOG: connection received: host=XX.XXX.X.XXX port=38726 2025-02-21 08:21:11 UTC-67b836dd.7021-LOG: disconnection: session time: 0:02:34.362 user=XXX-prod database=XXX-prod host=XX.XXX.X.XXX port=39732 2025-02-21 08:21:18 UTC-67b8377c.7147-LOG: connection received: host=XX.XXX.X.XXX port=48818 2025-02-21 08:21:21 UTC-67b8377f.7148-LOG: connection received: host=XX.XXX.X.XXX port=48830 2025-02-21 08:21:22 UTC-67b83782.714a-LOG: connection received: host=XX.XXX.X.XXX port=48836 2025-02-21 08:21:32 UTC-67b836dd.7020-LOG: could not receive data from client: Connection reset by peer 2025-02-21 08:21:32 UTC-67b83775.7145-LOG: could not accept SSL connection: Broken pipe 2025-02-21 08:21:32 UTC-67b83770.7144-LOG: could not accept SSL connection: Broken pipe 2025-02-21 08:21:32 UTC-67b8377c.7147-LOG: could not receive data from client: Connection reset by peer 2025-02-21 08:21:32 UTC-67b83775.7146-LOG: could not accept SSL connection: Broken pipe 2025-02-21 08:21:32 UTC-67b8377f.7148-LOG: could not receive data from client: Connection reset by peer 2025-02-21 08:21:32 UTC-67b836dd.7022-LOG: could not receive data from client: Connection reset by peer 2025-02-21 08:21:32 UTC-67b836dd.7020-LOG: unexpected EOF on client connection with an open transaction 2025-02-21 08:21:32 UTC-67b836dd.7020-LOG: disconnection: session time: 0:02:55.092 user=XXX-prod database=XXX-prod host=XX.XXX.X.XXX port=39718 2025-02-21 08:21:32 UTC-67b836dd.7022-LOG: unexpected EOF on client connection with an open transaction 2025-02-21 08:21:32 UTC-67b836dd.7022-LOG: disconnection: session time: 0:02:54.923 user=XXX-prod database=XXX-prod host=XX.XXX.X.XXX port=39746Any ideas what can be the cause for these network interruptions? I don't think it is something I can do by deadlocking database (database continues running, no information about start postgre again is in the log file).
Thank you.
-
Martin Gubis 0 Reputation points
2025-02-21T09:45:21.2766667+00:00 Thank you for the response. I have turned on server logs (level INFO). There were three outages today and the logs indicates, that the problem is network related. There are no deadlocks or database problems (restart) indicated, but following is in the log file at the time of outage:
2025-02-21 08:20:43 UTC-67b8375a.713d-LOG: connection received: host=XXX.XXX.XXX.X port=492022025-02-21 08:20:43 UTC-67b8375a.713e-LOG: connection received: host=XXX.XXX.XXX.X port=492102025-02-21 08:20:48 UTC-67b8375e.7140-LOG: connection received: host=XXX.XXX.XXX.X port=336102025-02-21 08:20:57 UTC-67b83767.7141-LOG: connection received: host=XX.XXX.X.XXX port=521442025-02-21 08:20:57 UTC-67b83767.7142-LOG: connection received: host=XX.XXX.X.XXX port=521522025-02-21 08:21:06 UTC-67b83770.7144-LOG: connection received: host=XX.XXX.X.XXX port=521662025-02-21 08:21:09 UTC-67b83767.7142-LOG: could not accept SSL connection: EOF detected2025-02-21 08:21:09 UTC-67b83767.7141-LOG: could not accept SSL connection: EOF detected2025-02-21 08:21:09 UTC-67b836dd.7021-LOG: could not receive data from client: Connection reset by peer2025-02-21 08:21:09 UTC-67b836dd.7021-LOG: unexpected EOF on client connection with an open transaction2025-02-21 08:21:09 UTC-67b83775.7145-LOG: connection received: host=XX.XXX.X.XXX port=387242025-02-21 08:21:09 UTC-67b83775.7146-LOG: connection received: host=XX.XXX.X.XXX port=387262025-02-21 08:21:11 UTC-67b836dd.7021-LOG: disconnection: session time: 0:02:34.362 user=XXX-prod database=XXX-prod host=XX.XXX.X.XXX port=397322025-02-21 08:21:18 UTC-67b8377c.7147-LOG: connection received: host=XX.XXX.X.XXX port=488182025-02-21 08:21:21 UTC-67b8377f.7148-LOG: connection received: host=XX.XXX.X.XXX port=488302025-02-21 08:21:22 UTC-67b83782.714a-LOG: connection received: host=XX.XXX.X.XXX port=488362025-02-21 08:21:32 UTC-67b836dd.7020-LOG: could not receive data from client: Connection reset by peer2025-02-21 08:21:32 UTC-67b83775.7145-LOG: could not accept SSL connection: Broken pipe2025-02-21 08:21:32 UTC-67b83770.7144-LOG: could not accept SSL connection: Broken pipe2025-02-21 08:21:32 UTC-67b8377c.7147-LOG: could not receive data from client: Connection reset by peer2025-02-21 08:21:32 UTC-67b83775.7146-LOG: could not accept SSL connection: Broken pipe2025-02-21 08:21:32 UTC-67b8377f.7148-LOG: could not receive data from client: Connection reset by peer2025-02-21 08:21:32 UTC-67b836dd.7022-LOG: could not receive data from client: Connection reset by peer2025-02-21 08:21:32 UTC-67b836dd.7020-LOG: unexpected EOF on client connection with an open transaction2025-02-21 08:21:32 UTC-67b836dd.7020-LOG: disconnection: session time: 0:02:55.092 user=XXX-prod database=XXX-prod host=XX.XXX.X.XXX port=397182025-02-21 08:21:32 UTC-67b836dd.7022-LOG: unexpected EOF on client connection with an open transaction2025-02-21 08:21:32 UTC-67b836dd.7022-LOG: disconnection: session time: 0:02:54.923 user=XXX-prod database=XXX-prod host=XX.XXX.X.XXX port=39746I think this indicates client connection problems. We are connecting to the database from App plan hosted on Azure. App doesn't crash - it properly (after certain time) report back to the client, that the database operation timed out (Exception while reading from stream -> System.TimeoutException). Do you have any idea what can I do to resolve this problem? It seems to be related to the Azure infrastructure.
Thank you for your time.
Sign in to comment
Sign in to answer