Service Unavailable 503vim-cmd commands fail to complete with: Failed to login: Connection refused: The remote service is not running, OR is overloaded, OR a firewall is rejecting connectionsesxcli commands fail to complete.services.sh restart appears to succeed, but the host remains unresponsive.VMware vSphere ESXi
Underlying storage issues can cause the hostd service to enter a degraded state, eventually becoming unresponsive and causing the host to show as "not responding" in vCenter. Specifically, one of the LUNs the host has access to may have encountered a hardware failure.
The following failure is repetitively logged in the host's vmkernel logs (observable via Out-of-Band Management Systems like iLO/iDRAC/CIMC):
H:0x0 D:0x2 P:0x0 Valid sense data: 0x4 0x8 0x00x4: Hardware Error08/00: Logical Unit Communication Failurevmkernel logging.esxcli storage core adapter rescan --allvmkfstools -VImportant Note: If hosts become unresponsive after unpresenting the LUN, ensure they are running on ESXi 7.0 U3 P10, 8.0 U2, or later. For environments requiring a fix for LUN unmapping handling, consult your release notes for the appropriate patch levels.