azure - 当 Visual Studio 启动 dev-fabric Azure 时，新辅助角色实例挂起

Question

我创建了一个具有单个辅助角色的新 Azure 项目，其代码由 Visual Studio Windows Azure 项目向导生成。当我从 Visual Studio 中启动它(使用 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 计算模拟器中看到一个带有绿点的新实例，但新实例会生成以下内容:

[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()。所以我看到了Microsoft's instructions并意识到也许新角色正在开始暂停，所以我单击了绿色箭头。不幸的是，我收到此暂时性错误消息，但没有任何反应:

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

我正在使用带有 Azure SDK 1.4.1 的 Visual Studio 2010 SP1 和适用于 Microsoft Visual Studio 2010 1.3 的 Windows Azure 工具(据我所知，是最新版本)。我已经重新安装了所有 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 放置站点的临时路径太长时，我就看到了这种情况。您可能需要检查事件查看器以了解发生了什么情况。您将在事件查看器中看到比计算模拟器更多的信息。如果遇到路径太长的问题，可以将 _CSRUN_STATE_DIRECTORY 环境变量设置为 c:\Azure 等路径。您可以查看更多信息here关于这一点。您还可以查看 Windows Azure 的故障排除区域 here .