今天,我发现我无法远程进入我的Azure VM规模集实例(赢得2016 Nano Server)。然后我尝试使用powershell重新启动VM scale set实例,但是出现了类似的错误:
Restart-AzureRmVmss : Long running operation failed with status 'Failed'. Additional Info:'VM 'master-vmss_0' has not
reported status for VM agent or extensions. Please verify the VM has a running VM agent, and can establish outbound
connections to Azure storage.'
ErrorCode: VMAgentStatusCommunicationError
ErrorMessage: VM 'master-vmss_0' has not reported status for VM agent or extensions. Please verify the VM has a
running VM agent, and can establish outbound connections to Azure storage.
我们的VM规模集已经正常运行了近一年。在VMSS上发生了什么? Azure最近是否对VMSS进行了更改?
使用NSG出站规则进行更新:
{
"name": "AllowVnetOutBound",
"properties": {
"provisioningState": "Succeeded",
"description": "Allow outbound traffic from all VMs to all VMs in VNET",
"access": "Allow",
"priority": 65000,
"direction": "Outbound",
}
},
{
"name": "AllowInternetOutBound",
"properties": {
"provisioningState": "Succeeded",
"description": "Allow outbound traffic from all VMs to Internet",
"access": "Allow",
"priority": 65001,
"direction": "Outbound",
}
},
{
"name": "DenyAllOutBound",
"etag": "W/\"a8e5e396-4f92-4118-b8ea-9b7d0111079f\"",
"properties": {
"provisioningState": "Succeeded",
"description": "Deny all outbound traffic",
"access": "Deny",
"priority": 65500,
"direction": "Outbound",
}
}
答案 0 :(得分:0)
检查网络安全组是否阻止来自VM的出站连接? VM代理和扩展已更新
如果此存储帐户阻止了HTTPS,则会收到此错误消息。更多信息,请http://www.deployazure.com/compute/virtual-machines/azure-vm-agent-extensions-deep-dive-part-3/
答案 1 :(得分:0)
我们的VM规模集已经正常运行了近一年。什么 发生在VMSS上? Azure最近是否对VMSS进行了更改?
最近,Azure中有一些维护,将主机操作系统更新到Windows Server 2016.我们可以在Azure门户中找到维护信息,如下所示:
在您的方案中,我们可以在VMSS的vnet中创建新VM ,然后使用该VM远程访问VMSS实例,以检查VM代理状态。
如果VM代理状态为关闭,我们应该启动它。
更新
最近,您在计划的维护VM重新启动后遇到了启动VM故障的问题。这是由于后端的容器故障问题 我们的后端工程师检查了故障租户并应用了缓解措施。你能再试一次重启VMss吗?如果这不起作用,请为Azure创建支持服务单。
再次,抱歉给您带来的所有不便。