Launching soon: The world's first vendor agnostic bug scrubLearn more & join waitlist
OPERATIONAL DEFECT DATABASE
...
...
Entering maintenance mode on an ESXi 5.5/6.x host fails at 67% with a timeout errorThe ESXi 5.5/6.x hosts High Availability status becomes uninitializedCannot start the virtual machine.In the C:\ProgramData\VMware\VMware VirtualCenter\Logs\vpxd.log or /var/log/vmware/vpx/ file, you see entries similar to: <YYYY-MM-DD>T<time> [09740 info 'commonvpxLro' opID=8eebd10] [VpxLRO] -- BEGIN task-1194 -- host-223 -- vim.HostSystem.enterMaintenanceMode -- 56d678e6-e3a2-258c-349c-ae14202d7a81(527a7310-f00f-c68c-fdbe-6f3a68f7125f) </time><YYYY-MM-DD>T<time> [09740 error 'vpxdvpxdMoHost' opID=8eebd10] [HostMo::EnterMaintenanceMode] operation aborted due to class Vim::Fault::Timedout::Exception(vim.fault.Timedout) <YYYY-MM-DD>T<time> [09740 info 'vpxdvpxdMoHost' opID=8eebd10] [HostMo::UpdateDasState] VC state for host host-223 (HA disabled -> uninitialized), FDM state (UNKNOWN_FDM_HSTATE -> UNKNOWN_FDM_HSTATE), src of state (null -> null) <YYYY-MM-DD>T<time> [09740 error 'vpxdvpxdMoHost' opID=8eebd10] [HostMo] Enter maintenance mode failed for host01: class Vim::Fault::Timedout::Exception(vim.fault.Timedout) In the hostd.log file, you see entries similar to: <YYYY-MM-DD>T<time> [59C7DB70 verbose 'Hostsvc.HaHost' opID=8eebd10-b9 user=vpxuser] ModeMgr::Begin: op = normal, current = normal, count = 1 <YYYY-MM-DD>T<time> [59C7DB70 info 'Hostsvc.HaHost' opID=8eebd10-b9 user=vpxuser] ModeMgr::Enter: next = maintenance, current = normal, count = 2, timeout = 0 <YYYY-MM-DD>T<time> [5B780B70 verbose 'Hostsvc.HaHost' opID=8eebd10-b9 user=vpxuser] ModeMgr::End: op = normal, current = normal, count = 2</time></time></time></time></time></time>
This issue occurs when: A virtual machine is shutdown from the guest operating systemThe virtual machine summary tab is opened from the vSphere Web Client at about the same time as the shutdown.After the virtual machine is powered off the host begins entering maintenance mode. This causes the host to hang on a pending task for the virtual machine and fails to enter maintenance mode.
This issues is resolved in ESXi 6.5 U2, available at VMware Downloads. To work around the issue, restart the management agents. For more information, see Restarting the Management agents on an ESXi or ESX host (1003490). If the ESXi host's status remains uninitialized after restarting the management agents agent, disable HA and then enable HA on the cluster.Disable HA on the cluster To disable vSphere HA in the vSphere Client: Log in to the vSphere Client.From the Home screen, click on Hosts and Clusters.Locate the cluster.Right-click the cluster and click Edit Settings.Deselect the Turn On VMware HA option.Click OK. Note: The process may take some time to complete.To disable vSphere HA in the vSphere Web Client: Log in to the vSphere Web Client. The default URL is: https://vCenter_Server_FQDN:9443/vsphere-client In the Home screen, click Hosts and Clusters.Locate the cluster.Right-click the cluster and click Settings.Click vSphere HA located under Services.Click Edit.Deselect the Turn On vSphere HA option.Click OK. To enable HA on the Cluster repeat the steps selecting Turn On vSphere HA instead of deselecting. To avoid this issue: Do not open the Summary tab of the virtual machine in the vSphere Web Client while it is powering down from a operating system initiated shutdown.Power off the virtual machine from the vSphere Web Client.
To be alerted when this document is updated, click the Subscribe to Article link in the Actions boxRestarting the Management agents in ESXiESXi 5.5 ホストがメンテナンス モードに入るプロセスが 67% で失敗する