postgreSQL server is stuck in starting status

Jesse B 0 Reputation points
2026-09-23T17:27:41.3633333+00:00

It has been stuck for hours now. Can not restart or stop using CLI because the server is still in starting status and command gets rejected. What is the fix for this?

Azure Database for PostgreSQL
0 comments

2 answers

Sort by: Oldest
Most helpful Newest Oldest
  1. Taz 10,126 Reputation points MVP Volunteer Moderator
    2026-09-27T13:48:19.48+00:00

    Hi Jesse,

    If an Azure Database for PostgreSQL Flexible Server has been stuck in Starting for several hours, stop and restart will be rejected because those operations are only available when the server is in the appropriate Ready or Stopped state. Microsoft documents this behavior directly.

    There is no supported CLI command to force-cancel the pending startup operation. Recent Microsoft Q&A cases with the same Starting/ServerBusyWithOtherOperation behavior were caused by a service-side startup hang and were resolved through backend intervention.

    So, if it has remained Starting for hours, this is a platform-side issue, not something you can fix with another stop or restart command. Check Resource Health and the Activity Log for the failed/long-running operation, then use the latest operation timestamp and correlation ID when opening the PostgreSQL support case.

    Was this answer helpful?

    0 comments
  2. Maksood Ahmed 15 Reputation points Microsoft External Staff Moderator
    2026-09-29T12:47:02.7666667+00:00

    Hello Jesse,

    If the Azure Database for PostgreSQL Flexible Server has remained in Starting state for hours and Stop/Restart operations are being rejected because another operation is in progress, repeatedly issuing start/stop/restart commands is unlikely to resolve the current operation.

    I recommend checking the following first:

    1. In the Azure portal, open the PostgreSQL Flexible Server and check Resource Health and Service Health for any platform-related issue.
    2. Review the server's Activity Log and capture the latest Start operation, timestamp, status, and correlation/tracking ID.
    3. Under Diagnose and solve problems, review the available troubleshooting information for the server. Microsoft provides built-in troubleshooting guides for PostgreSQL Flexible Server in the Azure portal.

    If the server continues to remain in Starting and management operations are still rejected, please open an Azure Support request and provide the resource ID, region, Activity Log details, and correlation/tracking ID so that the stuck operation can be investigated.

    If recovery of the existing server is not acceptable for a production workload, you can also consider point-in-time recovery (PITR) to a new Flexible Server, provided the required restore point is within the configured backup retention period. Microsoft documents that PostgreSQL Flexible Server automatically performs backups and supports point-in-time recovery within the configured retention period.

    Microsoft documentation:

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.