[英]Assembly changes detected. Restarting host
My Azure Functions were running fine and all of a sudden I am getting several "Assembly changes detected. Restarting host..." messages that is preventing my functions from completing. 我的Azure功能运行正常,突然间我收到了几个“检测到程序集更改。重新启动主机...”消息,导致我的功能无法完成。
I am not deploying new code so not sure what is triggering the Assembly Change event to fire. 我没有部署新代码,因此不确定是什么触发了Assembly Change事件。 I was running on the latest version of the runtime and have since reverted to version 1.0.10947 thinking that maybe the underlying runtime was updated, but I'm still getting that line showing up in the logs.
我正在运行最新版本的运行时,并且已经恢复到版本1.0.10947,认为可能是基础运行时已更新,但我仍然在日志中显示该行。
Update Now that @Alexey has helped me track down what is causing the Assembly changes to be detected. 立即更新 @Alexey帮助我找出导致检测到装配更改的原因。 I would like to ask if anyone can tell me WHY an assembly change is being detected even-tough I have not changed/redeployed my application.
我想问一下,是否有人可以告诉我为什么检测到装配更改,即使很难,我也没有更改/重新部署我的应用程序。
After looking in your logs we opened an issue https://github.com/Azure/azure-webjobs-sdk-script/issues/1533#issuecomment-303595960 . 查看日志后,我们打开了一个问题https://github.com/Azure/azure-webjobs-sdk-script/issues/1533#issuecomment-303595960 。
Your functions had multiple restores but now issue is gone. 你的功能有多个恢复,但现在问题已经消失。 Restores could be initiated by changing
project.json
. 可以通过更改
project.json
来启动还原。
If you are stuck with the multiple 如果你坚持多重
Assembly changes detected. Restarting host
I fixed my issue by deleted the log file in the Kudu services: 我通过删除Kudu服务中的日志文件修复了我的问题:
https://[FunctionAppName].scm.azurewebsites.net/
and follow on the top menu: 并按照顶部菜单操作:
Debug Console >> powerShell
And the file log is : 文件日志是:
LogFiles >> Application >> Functions >> function >> [Function name]
You can remove the log file. 您可以删除日志文件。
my 2c. 我的2c。
I was struggling with this issue for ages and not sure what was causing it. 多年来我一直在努力解决这个问题而不确定是什么导致了这个问题。 I believe I may have the answer.
我相信我可能有答案。
Our solution has been toying with consumption plans, but pulled back to full App Service Plans because the initiation times were too long for our rather unique usage patterns. 我们的解决方案一直在考虑消费计划,但由于启动时间对于我们相当独特的使用模式来说太长,所以我们已经退回到完整的应用服务计划。
But 2 of the appsetting params were still in place: WEBSITE_CONTENTSHARE And WEBSITE_CONTENTAZUREFILECONNECTIONSTRING. 但其中2个appsetting params仍然存在:WEBSITE_CONTENTSHARE和WEBSITE_CONTENTAZUREFILECONNECTIONSTRING。
per: https://docs.microsoft.com/en-us/azure/azure-functions/functions-app-settings#websitecontentazurefileconnectionstring these are ONLY for consumption plans. per: https : //docs.microsoft.com/en-us/azure/azure-functions/functions-app-settings#websitecontentazurefileconnectionstring这些仅适用于消费计划。
I removed them and... touch wood, the issue seems to be resolved. 我删除了它们......触摸木头,这个问题似乎得到了解决。
声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.