-
Notifications
You must be signed in to change notification settings - Fork 44
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 #597
Comments
Sarah mentioned this error This is likely caused by something you're doing in your code, as opposed to something on our side. If your code is open source or you're comfortable sharing it here, we can take a look and see if we notice anything. |
We also encountered the I'm not sure if the error is related to our own NodeJS code or the underlying Azure infra, but here some possible places in our code that could be related to the problem:
Unfortunately we don't have comprehensive logging so targeting the place exactly is not possible. We're continuing investigations and will report back if we find something. Also, we can provide more information if it helps your investigation. |
Yeah this kind of error (where node exits quickly) is hard because you don't always get helpful stack traces and whatnot. If you can add more comprehensive logging I'm sure that would help. If the issue is happening consistently, another helpful option is to try to create a sample app with the minimum amount of code needed to reproduce. As an aside, @hossam-nasr mentioned he has seen this error before when people use axios. Are you using axios by chance? |
I think I can't build a sample app as this problem occurs very rarely, once in a few months or so. We'll need to add more logging and follow this issue for more clues. Yes, we're using axios in this function app, but not in the failing function. So, the deployment zip package does contain axios, but it's not necessarily loaded to memory in this function.. 🤔 |
@ronkot There's a good chance axios might be what's causing your app to crash. What version of axios and node are you using? For some versions, axios is known to cause node to crash with this error code. See axios issue here: axios/axios#3396 and node issue here: nodejs/node#36325 |
@hossam-nasr thanks for pointers, those look quite interesting indeed! I just started my 3 week summer holidays but will reach back after that! |
so we are running on node.js 16 LTS and we do have axios dependency |
Hi again 😎 Just checked our error logs from past 4 months and this problem have occurred only once. The problem is so rare that we won't put more effort to find out the root cause. Thanks a lot for the kind advice, I'll come back if the issue pops up again 🙏 |
@tonakai Did you check if the axios dependency was updated? Are you still seeing this error? |
@hossam-nasr sorry i was a bit sidetracked i looked at the last 7 days and it is still there 4 out of 500k requests failed. but not sure if it is somehow related since this one mentioned node-pg library, but we didn't observe this error before as well. |
We believe the root cause here was the axios dependency as @hossam-nasr mentioned. We have a separate work item to help users solves these kinds of issues much faster. Closing in favor of #593 |
Original ticket was created here: it is suggested that i should ask here for more details: Azure/azure-functions-host#8438
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:
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: