-
Notifications
You must be signed in to change notification settings - Fork 436
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
Failed to start language worker process for node #3614
Comments
@sunxinhuan what is the value of your app setting: WEBSITE_NODE_DEFAULT_VERSION ? |
+1, Updatedit turns out to be ok if I changed it to |
I'm getting this error. My node version (by default, I haven't changed it), is 11.something. I don't think the solution is to change it back to 8.11.1, right? That was the solution for people who where on an older version (6.x). Any other ideas? |
For the brave souls who have gone the Linux route: ls /opt/nodejs from the console or Kudu will show you available versions. At the time of writing 10.1.0 is the highest available version and this one works for me. |
Every time this error appears, I change the node version and refresh the page. This is a efemerous repair but allows me to keep working. |
What a stupid bug... |
Same thing here. Refreshing Node version did the trick. |
Same happens for us after each deployment |
I've started seeing this as well post deploy for one of my function apps. Changing any application setting appears to resolve this which is easier than messing around with the set of valid values for WEBSITE_NODE_DEFAULT_VERSION. Just restarting the function app doesn't appear to work. |
Several folks are having different issues from different symptoms. Please open a new issue if you can still reproduce the issue. The supported node versions are version 8.x and 10.x. As of today we have support for WEBSITE_NODE_DEFAULT_VERSION -> |
Ibiza portal URL: https://aka.ms/antuxstage
Runtime version: 2.0.12134.0 (~2)
Browser: Chrome
Hosting Plan: Consumption
For V2 function app, failed to start language worker process for node.
Please refer to the snapshot:
![nodefailed](https://user-images.githubusercontent.com/39791546/46943508-5f7b5e00-d0a2-11e8-928a-6f892147030d.PNG)
Repro steps:
1. Open a V2 function app;
2. Add the app setting to running JS scenarios in Azure: FUNCTIONS_WORKER_RUNTIME=node
3. Add a HttpTrigger template;
4. Click "Run" button and Verify the Logs.
The text was updated successfully, but these errors were encountered: