-
Notifications
You must be signed in to change notification settings - Fork 454
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
getting Microsoft.Azure.WebJobs.Script.Workers.WorkerProcessExitException in some cases when the underlying machine starts up #8438
Comments
Thanks for the detailed info! From the logs for that function invocation, it looks like a worker failure (see below).
What you're seeing is the host reporting the worker failure, so the source is somewhere else. I'm seeing logs that show your function started executing, followed by a sudden worker failure and an attempt to dispose the channel for that worker. With the channel disposed, the execution fails and a restart begins. The worker failure could be caused by a number of things, and I'm not seeing any specific errors. I would suggest opening a ticket to investigate this fully with the Functions Node.js team (and to avoid any accidents sharing info on this public thread). Please let me know if you have any more questions, otherwise feel free to close this. |
@satvu thanks i've created a ticket there as well, i remember seeing that |
Investigative information
Please provide the following:
Repro steps
Provide the steps required to reproduce the problem:
i don't have exact steps to reproduce this issue, however it seems to happen during startup of each instance.
Expected behavior
Provide a description of the expected behavior.
no error
Actual behavior
Provide a description of the actual behavior observed.
i see an exception with the following call stack:
they all seem to have similar pattern like this one:
![image](https://user-images.githubusercontent.com/646428/172386646-6e026642-c7c8-4dea-9c65-ececdb9ae13a.png)
I also couldn't see any errors being reported using the context since it looks like it happens before my function runs.
Known workarounds
this error happens just once per machine, we have some try logic that handles it but ideally we shouldn't see any errors.
we have about 80k requests and 10 of them failed like this in the last 24 hours.
Related information
Provide any related information
The text was updated successfully, but these errors were encountered: