We help IT Professionals succeed at work.

Frozen Hardware ESXI box

One of my ESXI servers is not responding,  however, the VM's are active.  Is there a command that I can run from SSH to restart services without interrupting the VM's or do I have to reboot the entire box? If so where do I begin?
Comment
Watch Question

Andrew Hancock (VMware vExpert / EE Fellow)VMware and Virtualization Consultant
Fellow 2018
Expert of the Year 2017

Commented:
can you get on the physical console ?

restart network management agents...

otherwise shutdown all the VMs (e.g. RDP if Windows), SSH if Linux/Unix

and power off the host

Author

Commented:
I can't that's the problem.  The box is frozen  If I click on F2 nothing happens.  I found this via SSH
/etc/init.d/hostd restart
/etc/init.d/vpxa restart

But I'm not sure if this is correct or what the result will be.
Andrew Hancock (VMware vExpert / EE Fellow)VMware and Virtualization Consultant
Fellow 2018
Expert of the Year 2017

Commented:
what is the version of ESXi ?

/sbin/services.sh restart

(does not affect VMs)

but to be honest with you, if the box is really not responding or well - time to shutdown VMs, or when you get some downtime, because the ESXi box is not well.

Author

Commented:
6.0 -  I'll reboot if I have to.  Just was trying to find a way around it.  Also, would this screw up VCenter too?  I can't even get into the box to shut down the VM's I can either shut it down (Hard boot) or command line...
VMware and Virtualization Consultant
Fellow 2018
Expert of the Year 2017
Commented:
nope, vCenter Server will just go into not responding for 60-120 seconds

try

/sbin/services.sh restart

Author

Commented:
Sysinfo error on operation returned status : Not found. Please see the VMkernel log for detailed error information
services.sh: stopped /etc/init.d/vmtoolsd
services.sh: stop /etc/init.d/vmsyslogd
Running vmsyslogd stop
Stopping vmsyslogd service using init is not supported
services.sh: stopped /etc/init.d/vmsyslogd
services.sh: stop /etc/init.d/xorg
Running xorg stop
services.sh: stopped /etc/init.d/xorg
services.sh: stop /etc/init.d/wsman
Running wsman stop
Stopping openwsmand
Openwsmand is not running.
services.sh: stopped /etc/init.d/wsman
services.sh: stop /etc/init.d/sfcbd
Running sfcbd stop
This operation is not supported.
Please use /etc/init.d/sfcbd-watchdog stop
services.sh: stopped /etc/init.d/sfcbd
services.sh: stop /etc/init.d/snmpd
Running snmpd stop
root: snmpd is not running.
services.sh: stopped /etc/init.d/snmpd
services.sh: stop /etc/init.d/sfcbd-watchdog
Running sfcbd-watchdog stop
Getting Exclusive access, please wait...
Exclusive access granted.

This is what comes up

Author

Commented:
I think that did it.  It appears at least with VCenter I can manage the box again.  Thanks.  But I think I'm going to reboot the ESXI box anyway.
Andrew Hancock (VMware vExpert / EE Fellow)VMware and Virtualization Consultant
Fellow 2018
Expert of the Year 2017

Commented:
looks sort of normal....

time to shutdown machines, when you can, reboot and patch the server!

Author

Commented:
Just and FYI I ran:
/etc/init.d/hostd restart
/etc/init.d/vpxa restart

And everything came back.
Andrew Hancock (VMware vExpert / EE Fellow)VMware and Virtualization Consultant
Fellow 2018
Expert of the Year 2017

Commented:
/sbin/services.sh restart includes that and more!