Azure PostgreSQL database Flexible Server Stuck in Starting Status

Question

We've an Azure Flexible Postgresql Server that is showing as being 'Stuck' in a starting state.

Following MS guidance to try Azure CLI, it fails to start/stop or restart the server with the same error each time:

At this point I'm now tearing my hair out (or would if I had any!) because the process for raising a support ticket just sends me round and round in a circle with no ability to actually raise a request for support ....not even to pick the actual issue.

Can anyone direct me to how to resolve, or the best option to select to be able to raise a ticket ......rather than just telling me the server is in a 'Stopped' State....arghhhh!!!

PS Sorry for the dramatics but it is so frustrating.

Answer 1

Hello CHAPMAN, David

Thanks for reaching out! If your Azure Database for PostgreSQL Flexible Server is stuck (e.g., in “Stopping” or “Updating” state), here are some troubleshooting steps you can try.

1. Check Server Status via CLI

az postgres flexible-server show --name <server-name> --resource-group <resource-group>

Look for the state property to confirm the current status.

2. Attempt a Manual Restart

az postgres flexible-server restart --name <server-name> --resource-group <resource-group>

3. Inspect for Resource Locks

az resource lock list --resource-name <server-name> --resource-group <resource-group> --resource-type "Microsoft.DBforPostgreSQL/flexibleServers" 

If locks are found, remove them:

az resource lock delete --ids <lock-id>

4. Scale Up Temporarily (if resource exhaustion is suspected)

az postgres flexible-server update --name <server-name> --resource-group <resource-group> --sku-name GP_Gen5_4
 

5. Check for Blocking Queries Once the server is responsive, connect via psql and run:

SELECT pid, state, query FROM pg_stat_activity WHERE state != 'idle';SELECT pg_terminate_backend(pid) FROM pg_stat_activity WHERE state != 'idle';
 

6. Review Azure Monitor Logs Use Azure Monitor to check for errors or blockers that may be affecting server operations.
7. Confirm Platform Health Visit Azure Status to ensure there are no ongoing outages in your region.

If these steps don’t resolve the issue, please send us a private message with:

• Server name

• Azure region

We’ll investigate further and help get your server unstuck

Please "Accept as Answer" if the answer provided is useful, so that you can help others in the community looking for remediation for similar issues.

Thanks

Pratyush