Webrole没有启动，还总是很忙 [英] Webrole is not starting and always busy
问题描述
我工作的一个Azure的Web应用程序。在code编译和运行我的本地机器的罚款。但是，当我把软件包上传在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（）中不包含任何code。我不堵的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或工人）被卡住的情况下，我发现下面的步骤非常有用：
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（在Worker角色）code。一旦诊断是在自己的角色时，您可以在您的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支持团队（全天候或电话）下面的链接，他们将访问您的实例（与你的许可），并提供您根源的能力。
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.
<一个href=\"https://support.microsoft.com/oas/default.aspx?gprid=14928&st=1&wfxredirect=1&sd=gn\">https://support.microsoft.com/oas/default.aspx?gprid=14928&st=1&wfxredirect=1&sd=gn
在接触Azure支持，请提供您的订阅ID，ID的部署，您的Azure真实账户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屋！
