Host not usable due to freezing
search cancel

Host not usable due to freezing

book

Article ID: 408216

calendar_today

Updated On:

Products

VMware vSphere ESXi

Issue/Introduction

  • ESXi host becomes unresponsive in vCenter, via ESXi VAMI, and via DCUI.
  • Host rebooted unexpectedly
  • sudden power off of ESXi
  • Unable to manage via 3rd party remote management. 
  • No PSOD or core dumps are found on the host although core dump file or partition is configured. 
  • ESXi logs including vmkernel and vobd do not indicate issues with the kernel, storage, network, drivers, or firmware.
  • Host Unexpectedly reboots or has to be restarted as seen in the IPMI logs and cim-diagnostics.sh:
    Assert + System ACPI Power State S4/S5: soft-off
  • vobd.log may show the following error: 
    [vob.user.host.poweroff.reason.unavailable] The host is being powered off. The poweroff was not the result of a kernel error, deliberate reboot, or shut down. This could indicate a hardware issue. Hardware may reboot abruptly due to power outages, faulty components, and heating issues. To investigate further, engage the hardware vendor.
  • In hostd.log you see the following:
    0000-00-00T00:00:00.000Z In(166) Hostd[2100106]: [Originator@6876 sub=Hostsvc.VmkVprobSource] VmkVprobSource::Post event: (vim.event.EventEx) {
0000-00-00T00:00:00.000Z In(166) Hostd[2100066]: -->    key = 130,
0000-00-00T00:00:00.000Z In(166) Hostd[2100066]: -->    chainId = -945244864,
0000-00-00T00:00:00.000Z In(166) Hostd[2100066]: -->    createdTime = "1970-01-01T00:00:00Z",
0000-00-00T00:00:00.000Z In(166) Hostd[2100066]: -->    userName = "",
0000-00-00T00:00:00.000Z In(166) Hostd[2100066]: -->    host = (vim.event.HostEventArgument) {
0000-00-00T00:00:00.000Z In(166) Hostd[2100066]: -->       name = "hostfqdn",
0000-00-00T00:00:00.000Z In(166) Hostd[2100066]: -->       host = 'vim.HostSystem:ha-host'
0000-00-00T00:00:00.000Z In(166) Hostd[2100066]: -->    },
0000-00-00T00:00:00.000Z In(166) Hostd[2100066]: -->    eventTypeId = "esx.audit.host.poweroff.reason.unavailable",
0000-00-00T00:00:00.000Z In(166) Hostd[2100066]: -->    objectId = "ha-host",
0000-00-00T00:00:00.000Z In(166) Hostd[2100066]: -->    objectType = "vim.HostSystem",
0000-00-00T00:00:00.000Z In(166) Hostd[2100066]: --> }
0000-00-00T00:00:00.000Z In(166) Hostd[2100106]: [Originator@6876 sub=Vimsvc.ha-eventmgr] Event 259 : Host had been powered off. The poweroff was not the result of a kernel error, deliberate reboot, or shut
down. This could indicate a hardware issue. Hardware may reboot abruptly due to power outages, faulty components, and heating issues. To investigate further, engage the hardware vendor.

Environment

  • 8.x
  • 8.0 U3f

Cause

  • Abrupt hardware stop
  • Faulty physical components
  • Sudden cut/loss of power to the server
  • If the physical server has Automatic System Recovery enabled, this can sometimes mask a psod by rebooting the host before it gets a chance to generate a core dump.

Resolution

  1. Contact the server hardware vendor to further investigate the issue on the hardware.
  2. Check with the datacenter were the physical server is located for power issues.
  3. Disabling automatic system recovery may help investigation by allowing the host to psod. 
Powered by Wolken Software