-
Notifications
You must be signed in to change notification settings - Fork 758
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Container didn't respond to HTTP pings on port: 8000 #286
Comments
Hi, I've encountered the same issue I believe - does your web app report I looked through the logs and found this error being throw: 2023-10-18T23:03:41.225856898Z azure.core.exceptions.ClientAuthenticationError: DefaultAzureCredential failed to retrieve a token from the included credentials. and then I checked my Tenant ID, Subscription ID and the Secret key, all are correct. I also tried creating a new secret key and updating the config but the result was the same. |
No, my error looks more like a port issue. |
OK. In my instance the authentication fails and then a few seconds later the ping error is reported. 2023-10-18T23:03:42.877Z INFO - Container infoasst-web-umvck_0_abb22b68_middleware for site infoasst-web-umvck initialized successfully and is ready to serve requests. |
@andresravinet , Can you please check the following and post your logs here please.
|
Hi, I'm receiving the same error for the Delta release, I'm receiving the error: App Container Failed to Start, please see logs below: Container infoasst-web-xmlub_0_8673eeee couldn't be started: Logs = 2023-11-16T01:26:46.775410689Z _____ I've also noticed the following error: 2023-11-16T02:57:24.321084250Z Updated PYTHONPATH to '/opt/startup/app_logs:/tmp/8dbe641779eb75a/antenv/lib/python3.10/site-packages' 2023-11-16T02:57:34.205065170Z worker.init_process() 2023-11-16T02:57:34.205070870Z self.load_wsgi() 2023-11-16T02:57:34.205076270Z self.wsgi = self.app.wsgi() 2023-11-16T02:57:34.205081770Z self.callable = self.load() 2023-11-16T02:57:34.205086970Z return self.load_wsgiapp() 2023-11-16T02:57:34.205092470Z return util.import_app(self.app_uri) 2023-11-16T02:57:34.205107070Z mod = importlib.import_module(module) 2023-11-16T02:57:34.205112870Z return _bootstrap._gcd_import(name[level:], package, level) 2023-11-16T02:57:34.205155170Z File "/tmp/8dbe641779eb75a/antenv/lib/python3.10/site-packages/azure/core/exceptions.py", line 165, in map_error 2023-11-16T02:57:34.205158170Z raise error** 2023-11-16T02:57:34.205160870Z azure.core.exceptions.ResourceNotFoundError: (NotFound) Specified resource '/subscriptions/3d6eaea2-84d4-4caa-ad14-3af7da82a431/resourceGroups/infoasst-icazcolde04/providers/Microsoft.CognitiveServices/accounts/infoasst-aoai-xmlub/deployments/chat' cannot be found. 2023-11-16T02:57:34.205164770Z Code: NotFound 2023-11-16T02:57:34.205180371Z [2023-11-16 02:57:34 +0000] [76] [INFO] Worker exiting (pid: 76) |
I'm receiving the same error. |
My initial deployment were to existing Azure resources and resource groups. I deployed from scratch to create new resources and I no longer ran into the issues. Hope it helps. |
Thanks Andres, I've tried re-deploying but had the same issue. I think the error below was showing it couldn't find a model named 'chat', I may have missed a variable or placeholder in the config/script files, but can't see where. 2023-11-16T02:57:34.205160870Z azure.core.exceptions.ResourceNotFoundError: (NotFound) Specified resource '/subscriptions/3d6eaea2-84d4-4caa-ad14-3af7da82a431/resourceGroups/infoasst-icazcolde04/providers/Microsoft.CognitiveServices/accounts/infoasst-aoai-xmlub/deployments/chat I got it working by going into OpenAi Studio and creating a new deployment called 'chat' for the 'gpt-35-turbo' model. Then restarted the Web service. Hope this helps if anyone else has the same issue. |
Duplicate of #344 |
Discussed in #285
Originally posted by andresravinet October 18, 2023
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.
The text was updated successfully, but these errors were encountered: