Flexible PostgreSQL server not responsive for unknown reason

Question

Our web server suddenly started to fail to connect to our PostgreSQL flexible server, and the portal is stuck with the message 'The server is currently in 'restarting' state. Please wait for the operation to complete. You can refresh to check status. Reach out to Microsoft support if the operation is taking too long.' In the resource health menu, I can download a PDF file with the title 'Resource health History Details,' and it says:

Location: koreacentral
Availability Status: undefined (Unplanned)
Title: UnknownReason
Timespan: 05/28/2024 21:27:46 (GMT +9)

Restarting or stopping the server with Azure CLI fails with the following errors.

az postgres flexible-server stop ...  

(InternalServerError) An unexpected error occured while processing the request. Tracking ID: 'a53e62a2-5645-4d38-909f-7841c10d9aea'
Code: InternalServerError
Message: An unexpected error occured while processing the request. Tracking ID: 'a53e62a2-5645-4d38-909f-7841c10d9aea'

az postgres flexible-server restart ...

(InternalServerError) An unexpected error occured while processing the request. Tracking ID: 'ced356e6-49d4-47fe-a740-fb1d92ad656a'
Code: InternalServerError
Message: An unexpected error occured while processing the request. Tracking ID: 'ced356e6-49d4-47fe-a740-fb1d92ad656a'  

If you need more information like the resource ID or the subscription ID, please let me know.

Answer 1

Hi paxbun,

Thanks for reaching out to Microsoft Q&A.

This is a dedicated community support forum. Here we don't have access to the backend as azure support engineers do.

I suggest you create a support request over here:

https://azure.microsoft.com/en-us/support/create-ticket/

The ticket enables you to work closely with the support engineers and get a quick resolution to your issue.

Please 'Upvote'(Thumbs-up) and 'Accept' as an answer if the reply was helpful. This will benefit other community members who face the same issue.

Answer 2

Hi paxbun,

If the server is in restart state, you may need to wait till comes online.

What causes long recovery on Azure Database for PostgreSQL- Recent checkpoints are critical for fast server recovery. Once a restart happens, either it was a new instance (failover to healthy instance) or same instance (in-place restart) will connect to disk that has all logs, all WAL logs after the last successful checkpoint need to be applied to the data pages before the server starts to accept connections again.

Or you can retry using CLI command https://learn.microsoft.com/en-us/azure/postgresql/flexible-server/how-to-restart-server-cli

Thank You!