Where to find the actual error instead of "exception while executing function: ... System.Private.CoreLib: One or more errors occurred ...."

[Bazeloth]

Hi everyone,

Im executing a nodejs function in Azure and im getting the following error:

Exception while executing function: Functions.getSheet. System.Private.CoreLib: One or more errors occurred. (Worker process with pid 393 exited with code 1) (Worker process with pid 407 exited with code 1) (Worker process with pid 420 exited with code 1). Worker process with pid 393 exited with code 1.

Ofcourse this doesnt help me at all to consider whats wrong with the following piece of code:

var http = require('http');

http.createServer(function (req, res) {
res.writeHead(200, {'Content-Type': 'text/plain'});
res.end('Hello World!');
}).listen(8080);

The above piece of code is a simple hello world example. Could anyone tell me whats wrong with this?

Im on the West-European server by the way. Running on 2.0.1 beta runtime version and node version 8.4.0.
By default it's sets to 6.5.0, even though the latest version has been updated to 8.4.0:

7a31023

Are there more specific logs to be found somewhere?

[Bazeloth]

Source

var http = require('http');
http.createServer(function (req, res) {
res.writeHead(200, {'Content-Type': 'text/plain'});
res.end('Hello World!');
}).listen(8080);

[christopheranderson]

This is a known bug we plan on addressing soon in v2. Restarting the Function App mostly works to address this as a temporary work around. Your code is fine, it's a bug in our state machine for the node process on the worker.

[christopheranderson]

Probably a dupe of #2244

@pragnagopa, could you confirm?

[Bazeloth]

@christopheranderson ah thats unfortunate. Any ETA on a fix?

[Bazeloth]

@paulbatum Since @christopheranderson isnt responding. Do you have an ETA when 2.0 goes live? We are kind of waiting for this to work properly.

[paulbatum]

@isualize As neither @pragnagopa or @christopheranderson have picked this up for an upcoming sprint, I can't give you an ETA for this particular issue to be fixed. Functions 2.0 is already in preview, and we will make sure this is fixed prior to GA for v2 (but I don't have a GA date either).

[pragnagopa]

Submitted PR with a fix for this.

[ghost]

Just got the same issue.

Region: East Asia
Azure Function version: 2.x (beta)
Nodejs version: 8.9.4

[brusMX]

+1

Region EastUS
func --version
2.0.1-beta.26
Docker image:
microsoft/azure-functions-python3.6:v2.0.11651-alpha

[ghost]

@paulbatum @pragnagopa @christopheranderson I insist to reopen this issue, I continuously getting this again and again. Even restart doesn't help... No confidence to run in production, bad experience for development, and this really frustrating.

[pragnagopa]

Fix is not rolled out yet. Fix is part of 2.0.11737-alpha. We are currently working on this release. Should be out soon.

[pragnagopa]

@brusMX - For python can you try using the latest docker image from sample repo: https://github.com/Azure/azure-functions-docker-python-sample/blob/master/Dockerfile

[ghost]

@pragnagopa Thank you for the fast response, hopefully waiting for the next build to be published very soon. Any workaround you can suggest for now until version 2.0.11737-alpha? Restart, full redeploy, full redeploy with different app service name - none of this helped me :(

[pragnagopa]

@iredjee - Moved investigation to Azure/azure-functions-nodejs-worker#68

[anton-bot]

Yes please, any workaround currently until the issue is fixed?

[pragnagopa]

Please check Kudu diagnostic logs.