Launching soon: The world's first vendor agnostic bug scrubLearn more & join waitlist
OPERATIONAL DEFECT DATABASE
...
...
The command service mgmt-vmware restart does not restart hostd.The script gets stuck when stopping the service. The SSH session to the ESX/ESXi host becomes unresponsive. hostd fails to restart. Neither of these commands restart hostd successfully on an ESXi/ESX host: ./sbin/services.sh ./etc/init.d/hostd restart
This issue occurs if the config.xml file, located at /etc/vmware/hostd/ and the proxy.xml file, located at /etc/vmware/hostd/ is empty or has invalid entries. This issue may also occur if there are IPv6 entries in the /etc/hosts file that are associated with the localhost.
To resolve this issue, manually stop and restart the stuck service. To stop and restart the stuck service: Log in as root to the ESXi/ESX host command-line via the physical console or via KVM connection.Navigate to the /var/run/vmware directory with the command: # cd /var/run/vmware Run this command to list the files vmware-hostd.PID and watchdog-hostd.PID: # ls -l vmware-hostd.PID watchdog-hostd.PID Determine theProcess 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]# 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 PID For example: kill -9 1191 Delete the vmware-hostd.PID and watchdog-hostd.PID files with the command: # rm vmware-hostd.PID watchdog-hostd.PID Start the management service: For ESX, run the command: # service mgmt-vmware start For ESXi, run the command: # /etc/init.d/hostd start Notes: This issue may also occur if the /etc/vmware/hostd/config.xml is blank or has invalid entries. If a backup of the config.xml file exists in the same directory, the issue may be resolved by replacing the config.xml file with this backup file.This issue also occurs if the /etc/vmware/hostd/proxy.xml file is empty or has invalid entries. This issue may be resolved by copying the proxy.xml file from a working host and then restarting the hostd service.
Note: In the hostd.log file, when the proxy.xml file is empty, you see the messages similar to:[2012-07-30 04:13:26.764 FFFCAE80 verbose 'App'] Plugin 9 statically linked[2012-07-30 04:13:26.764 FFFCAE80 info 'Proxysvc'] Proxy config filepath is /etc/vmware/hostd/proxy.xml[2012-07-30 04:13:26.765 FFFCAE80 panic 'App'] error: no element found[2012-07-30 04:13:26.765 FFFCAE80 panic 'App'] backtrace:[00] rip 16d00c33[01] rip 16b9303e[02] rip 16b327a2 Restarting the Management agents in ESXiService mgmt-vmware restart no reinicia el hostdService mgmt-vm ware restart pode não reiniciar o hostd在 ESX/ESXi 中重新启动 mgmt-vmware 服务可能无法重新启动 hostdサービス mgmt-vmware を再起動しても ESX/ESXi の hostd が再起動しない場合がある