Strange Host Responsiveness Issues

[isaacwd]

- Recently upgraded hosts to 6.7 and vCenter to 6.7a

- Hosts are 'not responding' in vCenter Server

- Can ping

- Cannot acess web interface or login via SSH

- Can access it via console, but after you enter login information and press enter it freezes (cursor is still blinking)

- If you remove the host from the inventory and shut down a virtual machine on the host it brings everything back online and the host can be re-added to vCenter

- Four identical hosts, has happened on three of the four (twice on one)

- The host that had this issue twice now will not come back after trying the above method and is completely unresponsive at the console

[RajeevVCP4]

Plz provide vmkernel.log and hostd.log file

and exact date/time when server went not responding

what is back end storage ( is it boot from SAN or Local)

What hardware type

[msripada]

This issue is fixed in 6.7 Update 2

VMware ESXi 6.7 Update 2 Release Notes

PR 2235031: An ESXi host becomes unresponsive and you see warnings for reached maximum heap size in the vmkernel.log

Due to a timing issue in the VMkernel, buffers might not be flushed, and the heap gets exhausted. As a result, services such as hostd, vpxa and vmsyslogd might not be able to write logs on the ESXi host, and the host becomes unresponsive. In the /var/log/vmkernel.log, you might see a similar warning:WARNING: Heap: 3571: Heap vfat already at its maximum size. Cannot expand.

This issue is resolved in this release.

Host unresponsive can happen due to multiple reasons, if you experience this issue in 6.7 U2 and above, it needs to be validated by GSS if you are hitting same issue .. Most likely a different issue I believe

Thanks,

MS