-
Notifications
You must be signed in to change notification settings - Fork 21.5k
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
Exceeded language worker restart retry count for runtime:node. Shutting down Functions Host #42379
Comments
@geoffbrucepayne Thank you for your feedback! We will review and update as appropriate. |
same problem here |
What version of Node.js are you running? |
@ggailey777 Same here, the versions node: v10.14.1 |
Im getting the same for a function that was working earlier today. From Visual Studio Code: I don't even know what update has caused this so that i can roll it back. was it the azure functions tools? visual studio? node? |
We had 3 people all get this error starting at roughly the same time, all on Windows using Visual Studio Code. The problem for us was identified in the log as: which is the output of the call to Running: After shutting down Code and running Looks like the Azure Functions extension was updated within the last week adding some support for Functions v3 which may have caused this issue: |
Still same problem here, last week all functions were running fine: Can somebody help me please? Really stuck here and cannot find working solution on the internet. |
I have started to have the same issue. That was no issues prior to today Version: 1.40.0 (user setup) |
Any updates on this @mike-urnun-msft? |
Also getting this since yesterday Node: v8.11.1 |
Same problem here.
Still get the "Exceeded language worker restart retry count for runtime:node" error. I've seen this before when there was a dangling node.js process inside VS Code, and I manually killed it and it was fine, but that was intermittent and this happens all the time. |
Everyone, sorry for the delay on this. We're having this investigated now. |
For anyone experiencing the issue, I closed VSCode and reopened it. I see the same thing as @gertjanschokkaert: Starting inspector on 127.0.0.1:9229 failed: address already in use I think closing VSCode releases something that allows it to work again. Not a permanent fix, but something to you going potentially. |
Same issue while doing a demo |
Ive tried restarting VSCode and laptop, but neither help. |
Hi folks - Sorry for the delay. I was able to reproduce this only once in my first attempt (core tools 2.7.1724 build) but running |
Downgrading VSCode to version 1.39.2 will fix this. |
Thanks @ibenjemia i was facing same issue , but your suggestion help me to fix it. |
Facing this problem myself, I started debugging. Process Explorer showed me that the ExtensionHost was opening port 9229. For me disabling the Azure Pipelines extension fixed the issue. I'm going to check the Azure Pipelines extensions on why it seems to start with "debugging enabled". |
I'm on VS Code 1.40.1 and facing the same problem. |
I downgraded my VS code to 1.39.2 and the Azure Functions Plugin to 0.19.0 and it worked for me. |
Created this issue in VS Code: microsoft/vscode#85328 |
Hello everyone - We're proceeding to close this issue as (a) this repo is more for driving improvements towards MS Docs and (b) we're now tracking the issue in the repo referenced above in @EricJizbaMSFT's comment. |
Hello @geoffbrucepayne & everyone else who hit this issue - If you're still experiencing this issue, please refer to the various workarounds shared here while the team rolls out the fix (already available in VSCode insiders version) in a matter of a week or two at the latest (exact date is TBD & subject to change). |
Having the same issue here, not using VS Code. Any workaround? |
Hello, i'm having the same issue here, not using VS Code. |
Same issue still using VS Code |
@tohagan. This may not work for you due to the nature of every configuration being different, but I had tried most everything recommended here and on other sites. I switched from miniconda to an alternative app for virtual environments and somehow not everything associated with miniconda was properly removed. I am not sure why but after I uninstalled miniconda, it left remnants inside my powershell profile script. I removed the remnants of miniconda code inside my powershell profile script and VS Code debugger began working with Azure Functions again. |
This issue is related to local proxy. We should add below line to your local.settings.json
Once you add this line to you json file, you can see you grpc automatically started running Your file should look like this:- { |
FWIW i dance between WSL and Windows. Since i was testing in WSL, i negelected to pick the linux node version. So it wsa just vomitting over and over.. I used 'nvm list' then changed from 'system' to one of the local linux node versions that works (e.g. nvm use 10.22.1). then it started. |
Still suffering from this. Is the only way downgrading to a two-year-old version of Visual Studio Code???! |
@AndreasPirker I have followed your question in the SO forum, and it is currently impossible to reproduce your situation. If possible, it is recommended to upload your sample code and pay attention to hiding confidential information so that I can reply to you after the test. |
@AndreasPirker In addition, please note your vscode version and function tools version, and tell me the local pc is linux, macos or windows? |
|
I have the same problem a two weeks ago, and today, I understand why. One reason, possibly, it's because the connection the database. I'm using postgreSQL and redis, and if redis don't running, the application show this error. Maybe it's happening to you too. |
Just in-case anyone is still trying to fix this, I just encountered the error with an API call triggering SharePoint Graph API uploads. My intake trigger would run twice then run a third time and shut down with this error. I fixed it entirely by just removing all errors in my console. I just had 'can't read from undefined' error, which wasn't enough to stop the entire thing running but it was making it fail with this exact error after three API submissions. |
For some reason I keep getting this error and cannot run the function locally as a result. I am running Linux Mint 19.1 Cinnamon
Terminal output:
[2019-11-07 9:40:47 p.m.] Starting JobHost
[2019-11-07 9:40:47 p.m.] Starting Host (HostId=gbpid79c-1222241483, InstanceId=a71693a8-f0ed-4f39-9ed0-7e394b04957b, Version=2.0.12858.0, ProcessId=6055, AppDomainId=1, InDebugMode=False, InDiagnosticMode=False, FunctionsExtensionVersion=(null))
[2019-11-07 9:40:47 p.m.] Loading functions metadata
[2019-11-07 9:40:47 p.m.] 1 functions loaded
[2019-11-07 9:40:47 p.m.] Loading proxies metadata
[2019-11-07 9:40:47 p.m.] Initializing Azure Function proxies
[2019-11-07 9:40:48 p.m.] 0 proxies loaded
[2019-11-07 9:40:48 p.m.] Starting worker process:node --inspect=9229 "/usr/lib/azure-functions-core-tools/workers/node/dist/src/nodejsWorker.js" --host 127.0.0.1 --port 40881 --workerId 11529386-f795-4041-ad52-06d10ca5d65a --requestId 313565dc-8d3f-4d05-92ee-b797cd2f8b35 --grpcMaxMessageLength 134217728
[2019-11-07 9:40:48 p.m.] node process with Id=6086 started
[2019-11-07 9:40:48 p.m.] Starting worker process:node --inspect=9229 "/usr/lib/azure-functions-core-tools/workers/node/dist/src/nodejsWorker.js" --host 127.0.0.1 --port 40881 --workerId fca4a346-2822-4472-b48c-4a4ac8bd5c6b --requestId 9a73268e-32a0-4fd9-8927-c0e1963b16b2 --grpcMaxMessageLength 134217728
[2019-11-07 9:40:48 p.m.] node process with Id=6095 started
[2019-11-07 9:40:48 p.m.] Starting worker process:node --inspect=9229 "/usr/lib/azure-functions-core-tools/workers/node/dist/src/nodejsWorker.js" --host 127.0.0.1 --port 40881 --workerId 344469b4-e6a5-4e73-9697-30cb2b99aede --requestId 9e2a8138-e8d8-4f31-9949-a1e08b972103 --grpcMaxMessageLength 134217728
[2019-11-07 9:40:48 p.m.] node process with Id=6104 started
[2019-11-07 9:40:48 p.m.] Exceeded language worker restart retry count for runtime:node. Shutting down Functions Host
[2019-11-07 9:40:48 p.m.] Generating 1 job function(s)
[2019-11-07 9:40:49 p.m.] Found the following functions:
[2019-11-07 9:40:49 p.m.] Host.Functions.HttpTrigger
[2019-11-07 9:40:49 p.m.]
[2019-11-07 9:40:49 p.m.] Initializing function HTTP routes
[2019-11-07 9:40:49 p.m.] Mapped function route 'api/HttpTrigger' [get,post] to 'HttpTrigger'
[2019-11-07 9:40:49 p.m.]
[2019-11-07 9:40:49 p.m.] Host initialized (1533ms)
[2019-11-07 9:40:49 p.m.] Host started (1550ms)
[2019-11-07 9:40:49 p.m.] Job host started
[2019-11-07 9:40:49 p.m.] Starting inspector on 127.0.0.1:9229 failed: address already in use
[2019-11-07 9:40:49 p.m.] Starting inspector on 127.0.0.1:9229 failed: address already in use
[2019-11-07 9:40:49 p.m.] Starting inspector on 127.0.0.1:9229 failed: address already in use
Hosting environment: Production
Content root path: /home/gbp/projects/test
Now listening on: http://0.0.0.0:7071
Application started. Press Ctrl+C to shut down.
Http Functions:
[2019-11-07 9:40:49 p.m.] Stopping host...
[2019-11-07 9:40:49 p.m.] Stopping JobHost
[2019-11-07 9:40:49 p.m.] Job host stopped
[2019-11-07 9:40:49 p.m.] Host shutdown completed.
Application is shutting down...
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.
The text was updated successfully, but these errors were encountered: