Description: We are experiencing critical issues with our Azure PostgreSQL Flexible Server (Region: West Europe). Issue Details: Service Unavailability: The server is currently inaccessible, and the Azure Service Health dashboard indicates the service is unavailable with no clear reason provided. Failed Restart Attempts: Initial restart via Azure Portal resulted in the operation stalling indefinitely. Subsequent restart attempt using Azure CLI failed with the error: "Internal Server Error" (Message: An unexpected error occured while processing the request. Tracking ID: '870dfd49-026b-45ad-b635-9c66380190ba'). Resource Metrics: CPU, memory, and storage utilization are all within normal limits, ruling out resource exhaustion as the cause. Actions Taken: Followed Azure’s troubleshooting guidance to avoid excessive restarts (only 2 attempts made total: 1 via Portal, 1 via CLI). Verified network configurations (firewall rules, VNet settings) are intact. Impact: This is causing significant disruption to our operations. We urgently require assistance to: Investigate the root cause of the service unavailability. Resolve the restart failure and restore server functionality. Provide a timeline for resolution.

Hi Mohamed, Thanks for reaching out to Microsoft Q&A. Kindly go through below document on the actions which you can take due to service health issue https://learn.microsoft.com/en-us/azure/postgresql/flexible-server/concepts-business-continuity Please do not forget to "Accept the answer” and “up-vote” wherever the information provided helps you, this can be beneficial to other community members.

As the CEO of the company suffering from a this technical issue on Azure, the reply above is completely unacceptable as a "service response".. No account has been taken of our actual problem. Our "developer" support scheme has been downgraded - without notice - so that a significant problem cannot be addressed with a support ticket - which is clearly what is needed. We need MS to take notice of this technical issue and offer us a technical fix from an engineer. I am making a request for a formal support ticket to be opened for this issue.

Azure PostgreSQL Flexible Server Unavailable - Restart Failures and Connection Issues

Mohamed 5

Description:

We are experiencing critical issues with our Azure PostgreSQL Flexible Server (Region: West Europe).

Issue Details:

Service Unavailability: The server is currently inaccessible, and the Azure Service Health dashboard indicates the service is unavailable with no clear reason provided.
Failed Restart Attempts:
- Initial restart via Azure Portal resulted in the operation stalling indefinitely.
- Subsequent restart attempt using Azure CLI failed with the error: "Internal Server Error" (Message: An unexpected error occured while processing the request. Tracking ID: '870dfd49-026b-45ad-b635-9c66380190ba').
Resource Metrics: CPU, memory, and storage utilization are all within normal limits, ruling out resource exhaustion as the cause.

Actions Taken:

Followed Azure’s troubleshooting guidance to avoid excessive restarts (only 2 attempts made total: 1 via Portal, 1 via CLI).
Verified network configurations (firewall rules, VNet settings) are intact.

Impact:

This is causing significant disruption to our operations. We urgently require assistance to:

Investigate the root cause of the service unavailability.
Resolve the restart failure and restore server functionality.
Provide a timeline for resolution.

2 answers

Shikha Ghildiyal 4,295 Reputation points Microsoft Employee

2025-03-04T14:21:05.2866667+00:00

Hi Mohamed,

Thanks for reaching out to Microsoft Q&A.

Kindly go through below document on the actions which you can take due to service health issue

https://learn.microsoft.com/en-us/azure/postgresql/flexible-server/concepts-business-continuity

Please do not forget to "Accept the answer” and “up-vote” wherever the information provided helps you, this can be beneficial to other community members.
Please sign in to rate this answer.
Mohamed 5 Reputation points

2025-03-04T17:00:04.7766667+00:00

Thank you for sharing the documentation. However, it only covers backups, High Availability (HA), and auto-restarts during failures or upgrades, which don’t apply to our issue.

Our server is stuck in the "restarting" state for hours, despite healthy datacenters, no outages, and low resource consumption. Manual restarts via the Portal and CLI have both failed ("Internal Server Error").

This appears to be a platform-level issue. Please investigate urgently and provide steps to restore functionality.

Best regards,

Vijayalaxmi Kattimani 1,640 Reputation points Microsoft External Staff

2025-03-05T09:17:12.16+00:00

Hi Mohamed,

Welcome to the Microsoft Q&A Platform! Thank you for asking your question here.

We sincerely apologize for the inconvenience caused.

In addition to the response provided by @Shikha Ghildiyal, I would like to add the following information.

As we understand that, you are experiencing an issue with your Azure PostgreSQL Flexible Server in the West Europe region.

Could you please confirm if you are still experiencing the server restart issue?

In some cases, server restart failures can occur due to storage reaching 100% utilization, which may prevent the server from completing the restart process. Increasing the storage size via the Azure CLI has proven to be a successful workaround in such scenarios. Additionally, long-running transactions or queries impacting database performance could also contribute to restart issues.

Here are some insights and steps you can take to address the problem:

Azure periodically performs maintenance on services, which can lead to temporary unavailability. Ensure you've checked for any notifications regarding scheduled maintenance for your server. You can manage and view maintenance schedules as described in Scheduled maintenance in Azure Database for PostgreSQL - Flexible Server.

Navigate to the "Resource Health" section of your PostgreSQL server in the Azure Portal. This section provides insights into the current health status and any detected issues that might be affecting your server's performance or availability.

Access the server logs to identify any errors or anomalies that occurred prior to or during the service disruption. Detailed logging can offer clues about potential causes and guide troubleshooting efforts.

Ensure that regular backups are configured and consider geo-redundant storage options. This practice safeguards your data and allows for restoration in different regions if necessary.

Utilize Azure's monitoring tools to set up alerts for metrics such as CPU usage, memory consumption, and connection failures. Proactive monitoring can help detect and address issues before they escalate. Refer to Monitor metrics on Azure Database for PostgreSQL – Flexible Server for guidance.

By following these steps, you can systematically address the current unavailability issue and implement measures to enhance the resilience of your PostgreSQL server.

If the issue still persists, please let us know here. We will respond with more details and try to help you.

Please refer to the below mentioned links for more information.

https://learn.microsoft.com/en-us/azure/reliability/reliability-postgresql-flexible-server

https://learn.microsoft.com/en-us/azure/postgresql/flexible-server/concepts-business-continuity

I hope this information helps. Please do let us know if you have any further queries.

Vijayalaxmi Kattimani 1,640 Reputation points Microsoft External Staff

2025-03-06T09:07:18.2166667+00:00

Hi @Mohamed,

Following up to see, we haven’t heard from you on the last response.
If the issue still persists, could you please share the requested details in order to troubleshoot your issue via private message.

Thank you,
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.
DJ Hamblin-Brown 0 Reputation points

2025-03-04T16:37:27.2466667+00:00

As the CEO of the company suffering from a this technical issue on Azure, the reply above is completely unacceptable as a "service response".. No account has been taken of our actual problem.

Our "developer" support scheme has been downgraded - without notice - so that a significant problem cannot be addressed with a support ticket - which is clearly what is needed.

We need MS to take notice of this technical issue and offer us a technical fix from an engineer.

I am making a request for a formal support ticket to be opened for this issue.
Please sign in to rate this answer.

0 comments No comments
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

Share via

Azure PostgreSQL Flexible Server Unavailable - Restart Failures and Connection Issues

2 answers

Your answer