The next time is happens you should review the vmkernel.log, vobd.log in /var/run through console. The number one reason for hostd crashing is storage issues, APDs (all paths down),PDLs (permanent device loss) etc. If there was some flapping storage connection or transient loss of access to storage this can crash hostd. If using iSCSI maybe the firmware/drivers need updating on the physical NICs.
thank you for your reply!
I tried to open the logfiles, but it seems that they are empty (or not readable):
I configured the host to save logfile not locally but on our SAN. I am not able to download these files - when I try to, I get this error (message means "file operation failed"):
Do you know this behaviour?
Try below cmds to check/start hostd service
/etc/init.d/hostd status >>>> /etc/init.d/hostd start
Check hostd status , if it's not started then check /var/log/vmkernel.log , /var/log/hostd.log and /var/log/vpxa.log (take action accordingly as per error in log)
When esxcli cmd not working you can run localcli cmd instead of esxcli .
# localcli network firewall get
# localcli network firewall set --enable false
# localcli system maintenanceMode set --enable true
# localcli vm process list
# localcli vm process kill -w <World ID> -t soft (Shutdown VMs)