Closed aleksandraloka closed 1 year ago
update: this seems to be an issue in EastUs region. We have tried the same functions in other region, and it worked ok.
As a further note, we observed that the host version in eastus2 that has no problems has the following version: "version": "4.21.1.1", "versionDetails": "4.21.1+85b2144d318ea423fb58c2a07f001dd81750d267", "platformVersion": "100.0.7.287"
However, the eastus host version is 4.21.1.0.
Thanks for reporting the issue. Will check and update you.
@aleksandraloka I check same in east us region after deployed working fine as per your repro steps.Can you try once again.
This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment.
Our Azure Function, deployed on Dedicated plan (AppServicePlan) experienced a sudden error:
Did not find any initialized language workers
. Previously, it was working without any issue. It's a simple TimerTriggered function. We only redeployed the app with a simple change of the scheduled time, and the problems started. It's a dockerized python function.What we tried? We changed the
FUNCTIONS_EXTENSION_VERSION
to ~4. Previously it was ~3. We added theFUNCTIONS_WORKER_RUNTIME
to python. Previously, we did not add this because it is a dockerized app. We created new appServicePlan only for these azureFunctions. Previously, other appSerivces were part of the same Plan. Also, we recreated the FunctionApp via CDKTF code.So, after doing these changes, the function starts working for few executions, but after some time it generates again the same error. Our main function app has several TimerTriggered functions (several init.py functions) as part of the AzureFunctions. Some of them may even have same schedule time. Therefore we added the following env var, too, thinking it could help with the execution of the several functions:
FUNCTIONS_WORKER_PROCESS_COUNT
=4Also, the same functions are working all right on an environment (different tenant, same configs) that was not updated (the function was not redeployed there). And, what seems to be working for one function on one tenant, does not work on the other. It's an inconsistent behaviour.
We even tried changing the init.py with a generic Timer code, but the problem persisted.
More configuration
host.json file:
Dockerfile:
Investigative information
Repro steps
The problem started with redeploying the app with different scheduled time: example: "schedule": "0 /1 *"
So it's not a configuration/dependency change of any kind.
The following generic error occured:
Did not find any initialized language workers
Exception type -
System.InvalidOperationException
Failed method -
Microsoft.Azure.WebJobs.Script.Workers.Rpc.RpcFunctionInvocationDispatcherLoadBalancer.GetLanguageWorkerChannel
Contents of the requirements.txt file:
Provide the requirements.txt file to help us find out module related issues.
requirements.txt: