Postgres Flexible Server stuck in “starting” state for two days

Jonathan Craft 0

Hello, everyone. I started my Postgres Flexible DB server Wednesday morning, and it remains stuck in the “starting” state. How can a restart this server? The “stop” and “restart” buttons are all greyed out. Can I “self-rescue” by running a restart/stop command via the Azure CLI? Please advise.

Thank you,

Jonathan

Mahesh Kurva 2,830 Reputation points Microsoft Vendor

2025-02-21T12:38:13.26+00:00
Hi Jonathan Craft,

Welcome to Microsoft Q&A forum.

As I understand it, you're facing an issue with a PostgreSQL Flexible Server in Azure, where the server is stuck in a 'starting' state and the restart/stop buttons are greyed out in the portal.

Yes, you should be able to manage the server through the Azure CLI to perform a restart or stop. Here’s how you can proceed:

You can attempt to restart/ stop the server using the Azure CLI.

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

az postgres flexible-server stop --resource-group <resource_group> --name <server>

Sometimes, the server might be performing recovery operations. You can check the server status using:

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

For more information, please refer the document: https://learn.microsoft.com/en-us/azure/postgresql/flexible-server/how-to-start-server?tabs=cli-start-server#steps-to-start-a-server

can you check the following article for the issue especially long-running transaction may cause this problem:
https://techcommunity.microsoft.com/blog/adforpostgresql/why-restarting-azure-database-for-postgresql-took-long/1885780

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

This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Jonathan Craft 0 Reputation points

2025-02-21T18:20:37.9566667+00:00

Please accept my apologies for my prior comment (deleted). It appears I provided far too much information of my environment and my post was deleted due to security concerns, which is understandable.

I'm running the "az postgres flexible-server [ start | stop | restart ]" commands, and I consistently get an error in the following format for all three (3) commands:

(InternalServerError) An unexpected error occured while processing the request. Tracking ID: 'REDACTED'

Code: InternalServerError

Message: An unexpected error occured while processing the request. Tracking ID: 'REDACTED'

I can provided the redacted Tracking IDs upon request.

Any suggestions for next steps?

Thanks, Jonathan
Jonathan Craft 0 Reputation points

2025-02-21T18:31:18.3333333+00:00

It appears my last post contained too much information about my environment and was deleted due to security concerns (understandably). My apologies.

I'm running the az postgres flexible-server commands start, stop, restart and show. Show works just fine. But for the other three (3) commands I receive an error message in the format of:

(InternalServerError) An unexpected error occured while processing the request. Tracking ID: 'redacted'

Code: InternalServerError

Message: An unexpected error occured while processing the request. Tracking ID: 'redacted'

Any suggestions on next steps? This situation occurred when I attempted to start the server Wednesday, and it remains stuck in the "starting" state.

Thanks, Jonathan

Share via

Postgres Flexible Server stuck in “starting” state for two days

Your answer