Webrole 未启动且一直很忙 [英] Webrole is not starting and always busy
问题描述
我正在开发 Azure Web 应用程序.代码在我的本地机器上编译并运行良好.但是，当我在 Azure 平台中上传包时，webrole 不会启动并显示忙状态并显示消息:正在等待角色启动...系统正在初始化.[2012-04-30T09:19:08Z]"
I am working on a Azure Web application. The code compiles and runs fine on my local machine. But when I upload the package in Azure Platform, the webrole wouldn't start and gives Busy status with the message: "Waiting for role to start... System is initializing. [2012-04-30T09:19:08Z]"
Onstart() 和 Run() 都不包含任何代码.我没有阻止 OnStart 的返回.
Both Onstart() and Run() don't contain any code. I am not blocking the return of OnStart.
但是我在 javascript 中使用 window.setInterval.javascript 函数每 10 秒从数据库中检索一次值.
However I am using window.setInterval in javascript. The javascript function retrieves the values from Database every 10 seconds.
可以做些什么来解决这个问题?
What can be done to resolve this?
推荐答案
在大多数角色(Web 或 Worker)卡住的情况下，我发现以下步骤非常有用:
In most of the situation when a Role (Web or Worker) is stuck, I have found the following steps very useful:
始终为您的角色添加 RDP 访问权限，因为在某些情况下，当角色卡住时，您仍然可以 RDP 您的实例并自行调查问题.在某些情况下，您无法 RDP 到您的实例，因为依赖项服务尚未准备好让您进入.因此，如果您启用了 RDP 或可以 RDP 到您的实例，请尝试登录.
Always add RDP access to your role because in some cases when role is stuck you still have ability to RDP your instance and investigate the problem by yourself. In some cases you could not RDP to your instance because dependency services are not ready yet to let you in. So if you have RDP enabled or could RDP to your instance please try to log you in.
一旦您的实例拥有 RDP.获取本地机器 IP 地址并直接在浏览器中启动.在内部 IP 地址从 10.xxx 开始，因此您可以根据您的端点配置打开浏览器，即 http://10.xxx:80 或 https://10.xxx:443
Once you have RDP to your instance. Get the local machine IP address and launch directly in browser. In internal IP address starts from 10.x.x.x so you can open the browser based on your endpoint configuration i.e. http://10.x.x.x:80 or https://10.x.x.x:443
如果您无法通过 RDP 进入实例，那么最好的办法是获取诊断信息以了解问题可能出在哪里.诊断信息在你的实例中收集并发送到 Azure 存储，由你在 WebRole.cs(在 Web 角色中)或 WorkerRole.cs(在工作角色中)代码中进行配置.诊断在您的角色中起作用后，您可以在配置的 Azure Blob/表存储中收集诊断数据以了解问题.
If you could not get into the instance over RDP then your best bet are to get the diagnostics info to understand where the problem could be. The diagnostics info is collected in your instance and sent to Azure Storage, configured by you in your WebRole.cs (in Web Role) or WorkerRole.cs (in Worker Role) code. Once diagnostics is working in your role, you can collect the Diagnostics data at your configured Azure Blob/Table storage to understand the issue.
如果您没有 RDP 访问权限并且没有配置任何 Azure 诊断(或无法获得任何诊断数据来了解问题)，最好的办法是联系 Azure 支持团队(24x7 通过网络或电话)，他们将能够访问您的实例(在您的许可下)并为您提供根本原因.
If you don't have RDP access and don't have any Azure Diagnostics configured (or could not get any diagnostics data to understand the problem) your best bet is to contact Azure Support team (24x7 via web or phone) at the link below and they will have ability to access your instance (with your permission) and provide you root cause.
https://support.microsoft.com/oas/default.aspx?gprid=14928&st=1&wfxredirect=1&sd=gn
联系 Azure 支持时，请提供您的订阅 ID、部署 ID、您的 Azure Live 帐户 ID 和问题的简短描述.
When contacting Azure Support, please provide your Subscription ID, Deployment ID, your Azure Live Account ID and a small description of your problem.
这篇关于Webrole 未启动且一直很忙的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
