Container didn't respond to HTTP pings on port: 8000

[andresravinet]

Can anyone help me? I'm getting an Application Error when browsing to the web app. And the below is what is showing up in the log.
Container infoasst-web-6cq0e_0_17db8b46 didn't respond to HTTP pings on port: 8000, failing site start. See container logs for debugging.

[lon-tierney]

Thanks for reporting this issue. What branch are you deploying from?

[andresravinet]

I'm pretty sure i deployed from the main branch.

[lon-tierney]

Please try restarting the app service in the portal, and verify that it is a B-class service (not S1).

[andresravinet]

I'm on PremiumV2 (P1v2) App Service Plan. I restarted the app service and still the same problem.

[lon-tierney]

I've seen some failures in deployment myself on the main branch, and unsure if it's a BICEP issue or an Azure issue. I was throttled on the App Service deployment for some reason yesterday, so it took hours to complete, but it did complete. If it's not right, I suggest the following:

1. Delete your Resource Group where you installed it
2. Change your deployment name in env variables
3. make deploy again

[lon-tierney]

@andresravinet I'm hoping that this has been resolved? Please let us know if this discussion can be closed.

[odaibert]

I deployed it today and I'm getting the same error:

`2024-07-17T17:02:09.324Z INFO - docker run -d --expose=8000 --name infoasst-web-sjgvk_0_8dd1ed73 -e WEBSITE_USE_DIAGNOSTIC_SERVER=false -e WEBSITE_CORS_ALLOWED_ORIGINS=https://portal.azure.com,https://ms.portal.azure.com -e WEBSITE_CORS_SUPPORT_CREDENTIALS=False -e WEBSITE_SITE_NAME=infoasst-web-sjgvk -e WEBSITE_AUTH_ENABLED=True -e WEBSITE_ROLE_INSTANCE_ID=0 -e WEBSITE_HOSTNAME=infoasst-web-sjgvk.azurewebsites.net -e WEBSITE_INSTANCE_ID=aa5da807acbfc559bca55ef24c1fd7d38ec19e63d1268fa63fb6c8ab6fa58858 -e HTTP_LOGGING_ENABLED=1 appsvc/python:3.10_20240619.2.tuxprod gunicorn --workers 2 --worker-class uvicorn.workers.UvicornWorker app:app --timeout 600

2024-07-17T17:02:27.044Z INFO - Initiating warmup request to container infoasst-web-sjgvk_0_8dd1ed73_msiProxy for site infoasst-web-sjgvk

2024-07-17T17:02:27.388Z INFO - Container infoasst-web-sjgvk_0_8dd1ed73_msiProxy for site infoasst-web-sjgvk initialized successfully and is ready to serve requests.

2024-07-17T17:02:27.394Z INFO - Initiating warmup request to container infoasst-web-sjgvk_0_8dd1ed73 for site infoasst-web-sjgvk

2024-07-17T17:02:28.495Z ERROR - Container infoasst-web-sjgvk_0_8dd1ed73 for site infoasst-web-sjgvk has exited, failing site start

2024-07-17T17:02:28.502Z INFO - Initiating warmup request to container infoasst-web-sjgvk_0_8dd1ed73_middleware for site infoasst-web-sjgvk

2024-07-17T17:02:34.249Z INFO - Container infoasst-web-sjgvk_0_8dd1ed73_middleware for site infoasst-web-sjgvk initialized successfully and is ready to serve requests.

2024-07-17T17:02:34.327Z ERROR - Container infoasst-web-sjgvk_0_8dd1ed73 didn't respond to HTTP pings on port: 8000, failing site start. See container logs for debugging.

2024-07-17T17:02:34.583Z INFO - Stopping site infoasst-web-sjgvk because it failed during startup.`

It's that any workaround?

Regards,
Osvaldo Daibert

[lon-tierney]

Please try to restart your "web" application service in the resource group.

[odaibert]

It worked now. Thanks.