Closed Olivier-0 closed 1 year ago
Thanks for reporting will check and update pls share the proper function name,app name.
Hello, thanks for the answer. Are the information shared following this link information: https://github.com/Azure/azure-functions-host/wiki/Sharing-Your-Function-App-name-privately not enough to get the function app name?
@Olivier-0 pls create the support request using this link :https://learn.microsoft.com/en-us/azure/azure-portal/supportability/how-to-create-azure-support-request
This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment.
Was this issue ever resolved? I am running into the same issue
Hello, in the end the issue is somewhat solved, not sure why. The current setup we currently have is version 4.27.5 of the function runtime with version 4.9.0 for the extension bundle. The functions are configured with the flag Always-on. We still see sometimes the issue, but only once in a while after update of the running image. Hope this help for what it is
@Olivier-0 I am encountering the same issue while deployed through a custom docker container in AKS. Please share the possible workaround.
Hello, we are currently using Python Azure Function within a custom built docker container. For some reasons, sometimes we are getting the following error message:
When this error is happening, we notice on the graph of the memory working set the function seems unstable and permanently goes from 0 to 300MB used. We can resolve this issue by restarting (sometimes multiple times) the Function App.
Investigative information
Please provide the following:
Other details:
Exception type:
Failed Method:
Call Stack:
Repro steps
Provide the steps required to reproduce the problem:
We are creating a Python Function App using docker runtime based on RHEL9 and using the Azure-function-host v4.24.3, and sometimes we get this error. It was also observed on previous versions of the function host.
Expected behavior
Provide a description of the expected behavior.
When getting this error we would expect a clearer error message. Or we would want to not have the error at all.
Actual behavior
Provide a description of the actual behavior observed.
Randomly getting the mentioned error.
Known workarounds
Provide a description of any known workarounds.
Restart the function until not getting the error.
Contents of the requirements.txt file:
Provide the requirements.txt file to help us find out module related issues.
Related information
Provide any related information
Thank you for your help, please tell me me if you need more details