Service mgmt-vmware restart may not restart hostd
VMware KB Article: 1005566
Symptoms
•The command service mgmt-vmware restart does not restart hostd.
•The script gets stuck when stopping the service.
•The SSH session to the ESX host becomes unresponsive.
•hostd fails to restart.
Resolution
You must manually stop the stuck service and restart it.
To stop the service and restart it:
1.Log in as root to the ESX host command-line via the physical console or via KVM connection.
2.Navigate to the /var/run/vmware directory with the command:
# cd /var/run/vmware
3.Run this command to list the files vmware-hostd.PID and watchdog-hostd.PID :
# ls -l vmware-hostd.PID watchdog-hostd.PID
4.Determine the Process ID (PID) management service. View the contents of the vmware-hostd.PID file with the command:
# cat vmware-hostd.PID
For example:
[root@vmware]# cat vmware-hostd.PID
1191[root@vmware]#
5.Use the resulting PID to kill the process.
Caution: Use the kill -9 command with care. It kills the process of the supplied PID without exception or confirmation.
# kill -9
In this example, you run kill -9 1191.
6.Delete the vmware-hostd.PID and watchdog-hostd.PID files with the command:
# rm vmware-hostd.PID watchdog-hostd.PID
7.Start the management service.
◦For ESX, run the command:
# service mgmt-vmware start
◦For ESXi, run the command:
# /sbin/services.sh restart
Note: This issue may also occur if the /etc/vmware/hostd/config.xml is blank or has invalid entries. To resolve the issue recreate the config.xml file using the backup file available in the same folder.
Symptoms
•The command service mgmt-vmware restart does not restart hostd.
•The script gets stuck when stopping the service.
•The SSH session to the ESX host becomes unresponsive.
•hostd fails to restart.
Resolution
You must manually stop the stuck service and restart it.
To stop the service and restart it:
1.Log in as root to the ESX host command-line via the physical console or via KVM connection.
2.Navigate to the /var/run/vmware directory with the command:
# cd /var/run/vmware
3.Run this command to list the files vmware-hostd.PID and watchdog-hostd.PID :
# ls -l vmware-hostd.PID watchdog-hostd.PID
4.Determine the Process ID (PID) management service. View the contents of the vmware-hostd.PID file with the command:
# cat vmware-hostd.PID
For example:
[root@vmware]# cat vmware-hostd.PID
1191[root@vmware]#
5.Use the resulting PID to kill the process.
Caution: Use the kill -9 command with care. It kills the process of the supplied PID without exception or confirmation.
# kill -9
In this example, you run kill -9 1191.
6.Delete the vmware-hostd.PID and watchdog-hostd.PID files with the command:
# rm vmware-hostd.PID watchdog-hostd.PID
7.Start the management service.
◦For ESX, run the command:
# service mgmt-vmware start
◦For ESXi, run the command:
# /sbin/services.sh restart
Note: This issue may also occur if the /etc/vmware/hostd/config.xml is blank or has invalid entries. To resolve the issue recreate the config.xml file using the backup file available in the same folder.
留言