VMware Cloud Community
balazsgati
Contributor
Contributor
Jump to solution

Host is not responding

Hi All,

Today morning four host went to not responding state of the eight node Cluster. I see this error message in the VC

Events: "Host is not responding". All Service Console are unaccessable. When i try to connect to host by VI Client i get this error messge: "The server took too long to respond."

I tried to restart VC service. After the service restart, the four host went to disconnent state.

It is not possible to migrate the VMs to another host, but all the VMs are still running.

I tried to restart vmware-vpxa and mgmt-vmware in Console session. The mgmt-vmware didn't stopped. The vmware-vpxa restarted fine.

From the Console i could ping the VC server(FQDN), and from the VC server i could ping the HOST (FQDN). I enter the

DNS, and checked the Forward and Reverse Zones.

What can i do to solve this problem, without restart the hosts, 34 VMs are running at this time on this four hosts.

Thanks

Tags (3)
Reply
0 Kudos
1 Solution

Accepted Solutions
Pmarsha1
Enthusiast
Enthusiast
Jump to solution

Steps in order to progress

1) Login in the affected ESX server using Putty

2) service mgmt-vmware restart

If this doesn't work then the vmware-hostd daemon has to be killed.

3) ps -e | grep vmware-hostd

Look for the process_id associated with vmware-hostd

4) kill process_id

i.e. if 3) returned:

32470 ? 00:01:12 vmware-hostd

the command would be:

kill 32470

5) service mgmt-vmware status

if the service is started use

service mgmt-vmware restart

if it's stopped use:

service mgmt-vmware start

HTH

View solution in original post

Reply
0 Kudos
3 Replies
Pmarsha1
Enthusiast
Enthusiast
Jump to solution

Steps in order to progress

1) Login in the affected ESX server using Putty

2) service mgmt-vmware restart

If this doesn't work then the vmware-hostd daemon has to be killed.

3) ps -e | grep vmware-hostd

Look for the process_id associated with vmware-hostd

4) kill process_id

i.e. if 3) returned:

32470 ? 00:01:12 vmware-hostd

the command would be:

kill 32470

5) service mgmt-vmware status

if the service is started use

service mgmt-vmware restart

if it's stopped use:

service mgmt-vmware start

HTH

Reply
0 Kudos
balazsgati
Contributor
Contributor
Jump to solution

Thank You, it worked fine.

GB

Reply
0 Kudos
blong
Contributor
Contributor
Jump to solution

Just wanted to say I used those instructions for my same issue and they worked great too. Thank you so much for giving such an easy to follow procedure list to correct this problem. I really appreciate it. If I could award points, I would. Thanks again!

Reply
0 Kudos