Visual Studio启动dev-fabric Azure时挂起新的worker角色实例

Question

我已经创建了一个带有单个辅助角色的新Azure项目，其代码由项目向导生成。当我从Visual内部启动它(使用Ctrl-F5 -不是调试)，然后使用csrun.exe增加实例数时，新实例不能正常启动。如果我使用csrun.exe启动部署，那么一切都按预期进行。

详细信息

最初的实例很好地启动：

[fabric] Role Instance: deployment(237).Recon.WorkerRole1.0
[fabric] Role state Busy
[runtime] Role entrypoint . CALLING   OnStart()
[runtime] Role entrypoint . COMPLETED OnStart()
[runtime] Role entrypoint . CALLING   Run()
Information: WorkerRole1 entry point called
[fabric] Role state Started
Information: Working
Information: Working
....

若要添加实例，请增加ServiceConfiguration.cscfg中的数目并运行

csrun /update:237;ServiceConfiguration.cscfg

我可以在Windows Azure Compute仿真器中看到一个带有绿色点的新实例，但是新实例产生如下结果：

[fabric] Role Instance: deployment(237).Recon.WorkerRole1.3
[fabric] Role state Busy
[Diagnostics]: UpdateState(Microsoft.WindowsAzure.Diagnostics.DiagnosticMonitorStartupInfo, Microsoft.WindowsAzure.Diagnostics.DiagnosticMonitorConfiguration, )
[Diagnostics]: Acquired mutex
[Diagnostics] Information: C:\Users\oliver\AppData\Local\dftmp\s0\deployment(237)\res\deployment(237).Recon.WorkerRole1.3\directory\DiagnosticStore\Monitor
[Diagnostics] Information: C:\Recon\bin\Debug\Recon.csx\roles\WorkerRole1\diagnostics\x64\monitor\MonAgentHost.exe -LocalPath "C:\Users\oliver\AppData\Local\dftmp\s0\deployment(237)\res\deployment(237).Recon.WorkerRole1.3\directory\DiagnosticStore\Monitor" -StaticConfigFile "C:\Users\oliver\AppData\Local\dftmp\s0\deployment(237)\res\deployment(237).Recon.WorkerRole1.3\directory\DiagnosticStore\Monitor\Configuration\mastaticconfig.xml" -ConfigFile "C:\Users\oliver\AppData\Local\dftmp\s0\deployment(237)\res\deployment(237).Recon.WorkerRole1.3\directory\DiagnosticStore\Monitor\Configuration\maconfig.xml" -ShutDownEvent WADDM-ShutDown-f5dba0349f5d45769204950f21e9c6a5 -InitializedEvent WADM-StartUp-f5dba0349f5d45769204950f21e9c6a5 -parent 2328 -events
[Diagnostics]: Creating config channel server
[MonAgentHost] Output: Agent will exit when WADDM-ShutDown-f5dba0349f5d45769204950f21e9c6a5 is signaled.
[MonAgentHost] Output: Will signal WADM-StartUp-f5dba0349f5d45769204950f21e9c6a5 after the agent is initialized.
[MonAgentHost] Output: Registered as an event consumer.
[MonAgentHost] Output: Agent will exit when parent process 2328 exits.
[MonAgentHost] Output: Monitoring Agent Started
[Diagnostics]: Starting configuration channel polling

注意，角色状态永远不会“启动”，OnStart()也不会被调用。所以我看到了微软的指令，意识到这个新角色可能是被暂停的，所以我点击了绿色箭头。不幸的是，我收到了这条临时错误消息，但没有发生任何事情：

Failed to start service deploymentg deployment(237).  Start role failed for one or more roles.

我正在使用Visual 2010 SP1 w/AzureSDK1.4.1和WindowsAzureToolsforMicrosoftVisualStudio20101.3(最新版本，AFAIK)。我已经重新安装了所有Azure位，但都没有用。

(过了一段时间，我得到了这个额外的输出，它似乎是重新启动的诊断工具。我也不知道原因。我想我在其他项目中经常看到这些东西。

[Diagnostics]: Checking for configuration updates 17/05/2011 2:18:40 PM.
[Diagnostics]: Signalling process restart on event = WADDM-ShutDown-f5dba0349f5d45769204950f21e9c6a5
[MonAgentHost] Output: Exiting the monitoring agent after the shutdown event was signaled.
[MonAgentHost] Output: Monitoring Agent Stopped
[Diagnostics] Information: Diagnostic process exited with code: 0
[Diagnostics] Information: C:\Users\oliver\AppData\Local\dftmp\s0\deployment(237)\res\deployment(237).Recon.WorkerRole1.3\directory\DiagnosticStore\Monitor
[Diagnostics] Information: C:\Recon\bin\Debug\Recon.csx\roles\WorkerRole1\diagnostics\x64\monitor\MonAgentHost.exe -LocalPath "C:\Users\oliver\AppData\Local\dftmp\s0\deployment(237)\res\deployment(237).Recon.WorkerRole1.3\directory\DiagnosticStore\Monitor" -StaticConfigFile "C:\Users\oliver\AppData\Local\dftmp\s0\deployment(237)\res\deployment(237).Recon.WorkerRole1.3\directory\DiagnosticStore\Monitor\Configuration\mastaticconfig.xml" -ConfigFile "C:\Users\oliver\AppData\Local\dftmp\s0\deployment(237)\res\deployment(237).Recon.WorkerRole1.3\directory\DiagnosticStore\Monitor\Configuration\maconfig.xml" -ShutDownEvent WADDM-ShutDown-96f71a44d4b0434b8da78f1ac6f802c3 -InitializedEvent WADM-StartUp-96f71a44d4b0434b8da78f1ac6f802c3 -parent 2328 -events
[MonAgentHost] Output: Agent will exit when WADDM-ShutDown-96f71a44d4b0434b8da78f1ac6f802c3 is signaled.
[MonAgentHost] Output: Will signal WADM-StartUp-96f71a44d4b0434b8da78f1ac6f802c3 after the agent is initialized.
[MonAgentHost] Output: Registered as an event consumer.
[MonAgentHost] Output: Agent will exit when parent process 2328 exits.
[MonAgentHost] Output: Monitoring Agent Started
[Diagnostics]: Starting configuration channel polling
[Diagnostics]: Checking for configuration updates 17/05/2011 2:19:42 PM.

Answer 1

我已经看到，当你的临时路径，Azure放置的网站是太长。您可能需要检查您的EventViewer，看看正在发生什么。您将在EventViewer中看到比在Compute仿真程序中更多的信息。如果遇到路径太长的问题，可以将_CSRUN_STATE_DIRECTORY环境变量设置为c:\Azure这样的路径。您可以看到更多的信息，这里在这上面。您还可以检查Windows 这里的故障排除区域。

Answer 2

我能够通过使用这篇文章来自“只是另一个.NET的家伙”来解决挂起的Azure角色的问题。

该条的要点是：

• 检查EventViewer中与Azure相关的异常。在这里，您可能会看到类似于Provider Microsoft-Windows-Application Server-System Services IIS Manager{{SOME-GUID}} is missing channels under the channelreferances registry key.的东西(错误也存在:P )
• 导航到[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WINEVT\Publisher]并找到具有与上面相同GUID的文件夹。
• 检查您的开发机器是否具有与远程计算机上的工作人员角色相同的值。

遵循这些步骤后，我发现我有1，而另一台机器有3。一旦我更正了我的注册表，一切正常工作。