DannyBu
Contributor
Contributor

ESX-Host not responding to VC

Hi guys,

we had some issues, restarting and migrating vm's on one esx-host. So I tried starting the management agents, like described in KB1003490 (VMware Knowledge Base ).

/etc/init.d/hostd restart     seemed to work fine, but with

/etc/init.d/vpxa restart      I got following output (after a long time):

watchdog-vpxa: Terminating watchdog process with PID 35024

vpxa stopped.

So I thought the vpxa ist not running and tried to start with "/etc/init.d/vpxa start" , but esx says, that the service is running.

I tried to repeat the procedure, but the vpxa-restart hangs with following output:

/etc/init.d/vpxa restart

watchdog-vpxa: PID file /var/run/vmware/watchdog-vpxa.PID does not exist

watchdog-vpxa: Unable to terminate watchdog: No running watchdog process for vpxa

vpxa stopped.

It would be fine, if there would be a solution, without downtime, because there are still VMs running.

Tags (2)
Reply
0 Kudos
vXav
Expert
Expert

Have you tried this KB?

Reply
0 Kudos
aleex42
Enthusiast
Enthusiast

You could stop all mgmt agents and then restart them again:

services.sh stop

services.sh start

No VM downtime - only temporary disconnect from vCenter or vSphere Client.

-- Alex (VMware VCAP-DCV, NetApp NCIE, LPIC 2)

View solution in original post

Reply
0 Kudos
DannyBu
Contributor
Contributor

Thank you for your replys.

We restarted the mgmt-services via iLo (I assume this does the same as services.sh start/stop). This took about 20 minutes, but worked. Now after migrating the VMs to another host and reboot of the host, everything seems to work fine again.

Reply
0 Kudos
aleex42
Enthusiast
Enthusiast

Yes, thats the same :slightly_smiling_face:

-- Alex (VMware VCAP-DCV, NetApp NCIE, LPIC 2)