Bala G comments

Results 45 comments of


                                            Bala G

Random "The service is unavailable." and "Azure Functions runtime is unreachable" errors

Sorry for the delay in responding. Yes, there was a regression due to a recent update in the region which caused intermittent errors. The fix rollout has already started and...

Log the request latency between host and worker

Atleast for python, I think we are able to figure this out currently though it is not straightforward. @Hazhzeng might know the exact details.

ModuleNotFoundError: No module named 'aiohttp'

@neethumoltp What errors are you seeing when running the app in App service?

ModuleNotFoundError: No module named 'aiohttp'

I found the following exception but haven't investigated what this means. _Container daq3_0_0adbda65 didn't respond to HTTP pings on port: 8000, failing site start. See container logs for debugging._ Pasting...

Change Linux Elastic Premium to do run from package = 1 by default

Yes it is supported and there is a PR open as well - https://github.com/Azure/azure-functions-core-tools/pull/2529/files

Azure functions Http triggers getting down and throws 503/502 and sometimes even requests are not reaching to Http trigger

If you can share the appname we can investigate. https://github.com/Azure/azure-functions-host/wiki/Sharing-Your-Function-App-name-privately

Azure functions Http triggers getting down and throws 503/502 and sometimes even requests are not reaching to Http trigger

It could be due to the worker restarting. But we can only guess without the appname :)

Azure functions Http triggers getting down and throws 503/502 and sometimes even requests are not reaching to Http trigger

You can follow these steps to report the app name privately. https://github.com/Azure/azure-functions-host/wiki/Sharing-Your-Function-App-name-privately

Azure functions Http triggers getting down and throws 503/502 and sometimes even requests are not reaching to Http trigger

@RizwanSharp Took a quick look and found a few storage exceptions but looks like they might have been transient. If you see similar errors again, please open a new issue...

Azure functions Http triggers getting down and throws 503/502 and sometimes even requests are not reaching to Http trigger

@eaquiler Looks like the errors were due to an issue with the recent functions runtime update (3.0.15960) That update has now been rolled back and I can see this app...