Share via

SQL server won't start

green-msl 0 Reputation points
2025-12-03T15:40:41.51+00:00

I tried to scale up my mysql flexible server yesterday, it failed, and then took nearly 12 hours to exit the updating state when it was recovering from the failed scale, now I can't start it at all. 

PS C:\WINDOWS\system32> az mysql flexible-server start -g [resource group] -n [resource name]
(InternalServerError) An unexpected error occured while processing the request. Tracking ID: '24fe6076-3d4a-4c60-8518-59dbcdfdb18b'
Code: InternalServerError
Message: An unexpected error occured while processing the request. Tracking ID: '24fe6076-3d4a-4c60-8518-59dbcdfdb18b'
Azure Database for MySQL

2 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Q&A Assist
    2025-12-03T15:40:50.9133333+00:00
    AI generated content. This question contains an answer created with AI from Q&A Assist. Learn more

    It seems that you are experiencing issues starting your Azure Database for MySQL Flexible Server after a failed scaling operation. The error message you received indicates an InternalServerError, which could be due to several factors, including ongoing maintenance or issues with the server state after the failed scale operation.

    Here are a few steps you can take to troubleshoot the issue:

    1. Check Azure Status: Verify if there are any ongoing issues with Azure services that might be affecting your server.
    2. Wait and Retry: Sometimes, after a failed operation, the server may need additional time to recover. Wait for a while and try starting the server again.
    3. Review Logs: Check the error logs for any diagnostic messages that might provide more insight into the issue. You can access the error logs in the Azure portal under Server logs.
    4. Contact Support: If the issue persists, consider reaching out to Azure support for assistance, especially if the server remains unresponsive after several attempts.

    If you need to perform management operations on the server, ensure that it is in a running state first.

    References:

    0 comments
  2. Manoj Kumar Boyini 1,330 Reputation points Microsoft External Staff Moderator
    2025-12-03T16:38:00.6933333+00:00

    Hi green-msl,

    Thank you for reaching out to Microsoft QA.
    it sounds like you're dealing with a frustrating issue where your MySQL flexible server won't start after a failed scaling attempt. Here’s what you can try to resolve it:

    1.Check the Server Status: Verify that your server is actually in a failed state. You can do this by navigating to the Azure portal and checking the status of your MySQL flexible server.

    2.Review Resource Limits: Ensure that you're not exceeding the subscription or service limits for MySQL servers in your Azure account. This can sometimes prevent the server from starting.

    3.Restart the Server via Portal: If you haven’t already, try starting the server via the Azure portal. Go to your resource group, select the MySQL flexible server, and look for the option to start it there.

    4.Check for Ongoing Maintenance: Sometimes, Azure performs maintenance on servers, so check Azure’s status page or your notifications in the portal to see if there are any ongoing issues.

    5.View Detailed Logs: Since you received an InternalServerError, obtaining more detailed logs might point to what specifically is failing. You can do this via the Azure portal by checking the Monitoring and Diagnostic logs.

    Follow-Up Questions:

    1. Have you checked the Azure portal for any maintenance notifications or the status of the MySQL server?
    2. Did you encounter any specific error messages before the server entered the failed state?
    3. Are there any ongoing operations or alerts in the Azure subscription that might impact the server?
    4. Have you tried any other commands or approaches to start the server from Azure CLI besides what you've shared?
    0 comments

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.