Internal server error occurred. correlation ID: c0deed67-b864-4c94-ad64-29f402af841a

James Kavanagh 0 Reputation points
2024-06-14T21:14:52.5733333+00:00

My container app was stuck after pushing an update to the azure container registary. I ended up having to delete the container app, with the hopes of just creating a new container app for the same container from the registary.

Now, whenever I try to create a new container app. the deployment instantly says: 

{
    "status": "Failed",
    "error": {
        "code": "InternalServerError",
        "message": "Internal server error occurred. correlation ID: c0deed67-b864-4c94-ad64-29f402af841a"
    }
}

It will stay in the running state for about 10 minuets, and the duration counter will stop, but it wil still appear as if the deployment is still active.

I can't seem to fix this, and all the client devices for this server are now offline. Any help will be greatly appreciated, thank you in advance.

Azure Container Apps
Azure Container Apps
An Azure service that provides a general-purpose, serverless container platform.
323 questions
0 comments

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Sina Salam 6,496 Reputation points
    2024-06-15T17:07:37.3733333+00:00

    Hello James Kavanagh,

    Welcome to the Microsoft Q&A and thank you for posting your questions here.

    Problem

    I understand that you are having an issue while attempting to redeploy a container app using an updated image from the Azure Container Registry (ACR) due to the previous deletion of the original container app due to it being stuck, any subsequent attempts to create a new container app fail, returning an "InternalServerError" with a specific correlation ID. Also, I made to understand through your provided information that the deployment process appears active but is non-responsive, causing all client devices relying on this server to go offline.

    Solution

    To solve this problem there are couple of things we would need to review and get to the root of the issue at once.

    • Firstly, you would need to review logs and Azure status and ensure there is no ongoing issues with Azure services, then you will have to analyze the logs for more information about the error. Especially, your deployment logs.
    • Secondly, run the container image locally using Docker to confirm it works: docker run -d -p 8080:80 <image-url> Then check the ACR for the image's correct tag and repository path.
    • Thirdly, you will also need to double-check the configuration settings for the container app to ensure environment variables, ports, and secrets are set correctly and also verify the container image path and tag in the Azure Portal.
    • Check if the container app is allowed to communicate with other services and the ACR in your firewall.
    • Check the quotas and limits in your Azure subscription, specifically for CPU, memory, and number of resources.
    • Finally, if all the above could not give use specific information to solve this, use the correlation ID to get more detailed information: To use this correlation ID for troubleshooting:
      1. Go to the Azure portal.
      2. Navigate to the Help + support section.
      3. Create a new support request.
      4. Include the correlation ID in your support request details.

    I would have said you should recreate or redeploy using Azure CLI but by taking your time to go through all the above steps, you find the root cause and solution for this issue. Going through Azure CLI is only to generate more report.

    Accept Answer

    I hope this is helpful! Do not hesitate to let me know if you have any other questions.

    ** Please don't forget to close up the thread here by upvoting and accept it as an answer if it is helpful ** so that others in the community facing similar issues can easily find the solution.

    Best Regards,

    Sina Salam

    0 comments