Twitter Updates
| Restarting vmware-hostd |
 |
 |
 |
|
Today I had an issue here an ESX host became unresponsive in vCenter, yet the VMs that were running on the host were fine. The normal remedy for this issue would be to restart the management agent on the ESX host via the Service Console:
However, this did not work. The mgmt-vmware restart command hung while stopping the "VMware ESX Server Host Agent". Ten minites after executing mgmt-vmware restart, I decided to break out of the process by pressing Ctrl+z. Clearly, there was a problem with the existing running instance of the management agent, vmware-hostd. The only way to get this working without a host reboot, is to find the PID for vmware-hostd and kill it: To locate the PID for the running vmware-hostd process execute:
Once vmware-hostd is no longer running, you can restart the management agent by running:
|
Share This Page
Certifications
Popular
- Building an iSCSI Openfiler SAN on a USB Stick
- Simple VMware vSphere 4 & 5 License Calculator
- Replace SSL Certificates: Replace vCenter Server SSL Certificates
- Patching ESX 3.5 Using esxupdate
- My experiences with Installing vCenter on Windows Server 2008 R2
- ESX 3i: Host in HA Cluster must have userworld swap enabled
- ESX 3.5 on HP Proliant ML115 G5
- Replacing vSphere SSL Certificates
- Clearing a GUID Partition Table (GPT) in Linux
- VMware ESXi 3.5 on HP Proliant ML110 G5
Support VirtualVCP!
Information and Resources on this site are 100% free, however it costs money to run this site. Please help support this site by giving a donation.
RSS Feeds
Hosted By:
I've seen posts the same of this thousands of times with this error; am I the only one in the world that doesn't have the above working for them?
The service restart never works so I don't try no more, I find the running process, kill the PID then restart the service and the host agent still hangs.
I end up having to do a restart "shutdown -r now" command then after stopping all the processes etc it sits at restarting the system until I manually power off the machine (left it 30~ hours once).
Not sure if this is beyond the scope of this subject but any help will be apreicated as it's every week this happens; only thing that's changed is I've added a new OpenFiler iSCSI storage share...