Skip to content
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

Exceptions "node exited with code -1" on function apps #3876

Closed
zeeshan-aym opened this issue Dec 11, 2018 · 2 comments
Closed

Exceptions "node exited with code -1" on function apps #3876

zeeshan-aym opened this issue Dec 11, 2018 · 2 comments

Comments

@zeeshan-aym
Copy link

zeeshan-aym commented Dec 11, 2018

We are having "node exited with code -1" exceptions on our different function apps. There is no much details being logged against this exception. also worth mentioning that triggered functions also working fine. There is no such issue observed to test on local env.
Please be informed that these exceptions are on and off, sometimes it happen one time when function gets trigger and sometimes it happen more than 2 times in an half an hour.

Investigative information

Please provide the following:

  • Timestamp: 2018-12-11T10:30:00.0051731+00:00
  • Function App version (1.0 or 2.0): 2.0.12210.0 (~2)
  • Function App name:
  • Function name(s) (as appropriate):
  • Invocation ID: 2da8d2f2-2d57-41df-8b7d-08b1324e8f43
  • Region:East US 2

Repro steps

Unfortunately we are unable to reproduce the problem because function itself triggered correctly but thrown exceptions so keen to know about this exception.

Expected behavior

Function triggered
Function completed successfully
No exceptions in application insights

Actual behavior

Function triggered
Function completed successfully
Exceptions thrown

Known workarounds

Function runtime version has been upgraded to latest one.

Related Information

Exception Type -> Microsoft.Azure.WebJobs.Script.Rpc.LanguageWorkerProcessExitException

@mhoeger
Copy link
Contributor

mhoeger commented Dec 14, 2018

You can safely ignore those exceptions as they are expected (root cause is this: #3415).

Those exceptions will go away after resolving #3415, but we should also look into seeing if we can get those logs out of the exceptions table in Application Insights too.

@pragnagopa
Copy link
Member

Closing this as host will log process exits with -1 as debug logs

_workerChannelLogger.LogDebug(exc, $"Language Worker Process exited.", _process.StartInfo.FileName);

@ghost ghost locked as resolved and limited conversation to collaborators Dec 31, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants