Azure App Service Failing Start - Angular App with Node - Failed During Startup

Question

Good morning,

Been looking for similar reports of this, we've been experiencing this since Sunday evening on the 5th May.

Started in our production service (no changes or deployments have been made in months just to add).

Whilst we were investigating production, our uat and pre-production slots started to fail in the same manner.

Our production slot came back online on Tuesday, and overnight has now failed again.

Currently our PREPROD slot has come to life again. All this without any changes.

All we've found is that Microsoft are running some planned maintenance, but at no point does it suggest it could lead to this kind of outage. https://portal.azure.com/#view/Microsoft_Azure_Health/DetailsPage.ReactView/fromDeeplink~/false/index~/0/selectedEventSummary~/%7B%22trackingId%22%3A%22WMNJ-7PZ%22%2C%22scope%22%3A%22Subscription%22%2C%22impactedSubscriptions%22%3A%5B%22e471fc84-ecdf-4123-af12-5e8b2c7d1cc5%22%2C%22bb1b30bc-86a8-4469-a3a1-438a0e70f480%22%5D%2C%22eventType%22%3A%22PlannedMaintenance%22%2C%22impactStartTime%22%3A%22Thu%20May%2002%202024%2021%3A05%3A19%20GMT%2B0100%20(British%20Summer%20Time)%22%7D/trackingId/WMNJ-7PZ/impactedSubs~/%5B%22e471fc84-ecdf-4123-af12-5e8b2c7d1cc5%22%2C%22bb1b30bc-86a8-4469-a3a1-438a0e70f480%22%5D/scope/Subscription/eventType/PlannedMaintenance/impactStartTime/Thu%20May%2002%202024%2021%3A05%3A19%20GMT%2B0100%20(British%20Summer%20Time)

We've concluded this is absolutely no way anything we have control over now, we've tried every possible option regarding ports, investigating issues in our app starting up, everything. Nothing works.

This 100% has to be microsoft azure.

The issue we get across all slots is below:

2024-05-08T14:46:43.793Z INFO - docker run -d --expose=8080 --name xxxxxx_xxxx -e WEBSITE_USE_DIAGNOSTIC_SERVER=true -e WEBSITE_SITE_NAME=xxxxxx_xxxx -e WEBSITE_AUTH_ENABLED=False -e WEBSITE_ROLE_INSTANCE_ID=0 -e WEBSITE_HOSTNAME=xxxxxx_xxxx -e WEBSITE_INSTANCE_ID=0aa548ea0f4ea47436874f2be441b45effba82346c7c36c96ad8174f8862466e -e HTTP_LOGGING_ENABLED=1 appsvc/node:20-lts_20240321.5.tuxprod node --trace-uncaught server.js

2024-05-08T14:46:44.320Z INFO - Initiating warmup request to container xxxxxx_xxxx for site xxxxxx_xxxx

2024-05-08T14:51:02.090Z ERROR - Container xxxxxx_xxxx for site xxxxxx_xxxx did not start within expected time limit. Elapsed time = 257.7705218 sec

2024-05-08T14:51:02.097Z ERROR - Container xxxxxx_xxxx didn't respond to HTTP pings on port: 8080, failing site start. See container logs for debugging.

2024-05-08T14:51:02.101Z INFO - Stopping site xxxxxx_xxxx because it failed during startup.

Just to confirm the container logs it refers to do not contain anything else other than the logs in the console as above. Absolutely blind, if this continues we'll be lifting this out of the App Service and planning migration to another provider or on prem VM over the weekend.

Unfortunately as we utilize a third party cloud managing company, we are awaiting them raising tickets with Microsoft so our hands have been tied majorly.

Answer 1

@Dave Jones , I’m sorry to hear about the issues you’re experiencing with your Azure App Service.

I understand you have tried different steps to isolate the issue. Based on the error message that you received "Container xxxxxx_xxxx for site xxxxxx_xxxx did not start within expected time limit. Elapsed time = 257.7705218 sec"

By default, if your container does not respond after 230 seconds, it will time out. (This time out can be increased by with the WEBSITES_CONTAINER_START_TIME_LIMIT app setting.) (up to a maximum of 1800)

If you’re running a (custom container) with Web App for Containers, use WEBSITES_PORT. Ensure that this is set to the port that’s also exposed in your Dockerfile through the EXPOSE instruction Vs On App Service Linux, using (Blessed Images) - use PORT, which directly influences the container port of the docker run command.

Checkout the other possible causes outlined this article to narrow-down the issue. Troubleshooting ‘Container didnt respond to HTTP pings on port, failing site start’

Kindly let us know how it goes, I will be happy to assist you further.

---

If the answer helped (pointed, you in the right direction) > please click Accept Answer