Re: vmware-hostd stopped

alefesta · ‎10-30-2008

Hi all,

I have an esx 3.5 , part of a Vi3 infrastracture, all of sudden the it was disconnected. I was able to ping and remotly administrer through SSH. All the services are running but if I do a "service mgmt-vmware status" said vmware-hostd stopped. If I try to restart the service or a sequence like vpxa than mgmt hostd run for 1 sec than stop. There were no changes of configuration on the server, apparently nothing changed...

In log messages I've found this "watchdog-hostd: '/usr/sbin/vmware-hostd -u -a' exited after 1 seconds (quick failure 6)" and in vpxa.log I've this:

Could not resolve namespace for authenticating to host agent

Last stats polling used ms

Creating temporary connect spec: localhost:443

Failed to discover namespace: Connection refused

Could not resolve namespace for authenticating to host agent

Last stats polling used ms

Creating temporary connect spec: localhost:443

Failed to discover namespace: Connection refused

Could not resolve namespace for authenticating to host agent

Last stats polling used ms

I may ping and reslove the virtual center and all other host and I may do the same from the other hosts and from the virtual center.

thanks for help me in this.

Alex

Karunakar · ‎10-30-2008

Hi,

This also could be the issue with the DNS.

Can you please check , if the hostname of the esx machine can be resolved from nslookup,

and also try to check if you can ping the esx machine with the hostname.

Also try to remove the esx machine from the vc inventory and try to restart mgmt-vmware service in esx, and then try to add the machine with the IP address.

This should resolve. BTW, check the network settings in the ESX, check for the dns. in /etc/resolve.conf .

-Karunakar

alefesta · ‎10-30-2008

thanks, yes that was my first idea, I've double checked all you said but nothing, apparently the machine is able to reslove everything and is able to connect...

I may add this I may telnet on port 902 (the client) but not able to telnet 443 and 80 or other ports..I've double checked the firewall and even if I put it down (allo access inbound and outbound) I am not able to access. Without the vmware-hostd I am not able to access from web or from the vi client... the host is already removed from the vc and is correctly registerd in the dns.

Alex

Karunakar · ‎10-30-2008

Can you please let me know if you are getting any error messages while trying to add the esx machine to the VC

or any error messages in /var/log/messages.

This could helpus to isolate the issue.

-Karunakara

alefesta · ‎10-30-2008

from the VC I've got a simple"unable to access the host" from the messages I've got this:

Oct 30 13:33:09 esx01srv watchdog-hostd: '/usr/sbin/vmware-hostd -u -a' exited after 0 seconds (quick failure 5)

Oct 30 13:33:09 esx01srv watchdog-hostd: Executing cleanup command '/usr/sbin/vmware-hostd-support'

Oct 30 13:33:10 esx01srv watchdog-hostd: Executing '/usr/sbin/vmware-hostd -u -a'

Oct 30 13:33:10 esx01srv watchdog-hostd: '/usr/sbin/vmware-hostd -u -a' exited after 0 seconds (quick failure 6)

Oct 30 13:33:10 esx01srv watchdog-hostd: Executing cleanup command '/usr/sbin/vmware-hostd-support'

Oct 30 13:33:11 esx01srv watchdog-hostd: End '/usr/sbin/vmware-hostd -u -a', failure limit reached

Oct 30 13:33:41 esx01srv watchdog-hostd: PID file /var/run/vmware/watchdog-hostd.PID not found

Oct 30 13:33:41 esx01srv watchdog-hostd: Unable to terminate watchdog: Can't find process

Oct 30 13:33:48 esx01srv watchdog-hostd: PID file /var/run/vmware/watchdog-hostd.PID not found

Oct 30 13:33:48 esx01srv watchdog-hostd: 4326 Begin '/usr/sbin/vmware-hostd -u -a', min-uptime = 60, max-quick-failures = 5, max-total-failures = 1000000

Oct 30 13:33:48 esx01srv watchdog-hostd: Executing '/usr/sbin/vmware-hostd -u -a'

Oct 30 13:33:48 esx01srv VMware[init|http://communities.vmware.com/community-document-picker.jspa?communityID=&subject=init]: 4326 Begin '/usr/sbin/vmware-hostd -u -a', min-uptime = 60, max-quick-failures = 5, max-total-failures = 1000000

Oct 30 13:33:48 esx01srv watchdog-hostd: '/usr/sbin/vmware-hostd -u -a' exited after 0 seconds (quick failure 1)

Oct 30 13:33:48 esx01srv watchdog-hostd: Executing cleanup command '/usr/sbin/vmware-hostd-support'

Oct 30 13:33:49 esx01srv watchdog-hostd: Executing '/usr/sbin/vmware-hostd -u -a'

Oct 30 13:33:49 esx01srv watchdog-hostd: '/usr/sbin/vmware-hostd -u -a' exited after 0 seconds (quick failure 2)

Oct 30 13:33:49 esx01srv watchdog-hostd: Executing cleanup command '/usr/sbin/vmware-hostd-support'

Oct 30 13:33:50 esx01srv watchdog-hostd: Executing '/usr/sbin/vmware-hostd -u -a'

Oct 30 13:33:50 esx01srv watchdog-hostd: '/usr/sbin/vmware-hostd -u -a' exited after 0 seconds (quick failure 3)

Oct 30 13:33:50 esx01srv watchdog-hostd: Executing cleanup command '/usr/sbin/vmware-hostd-support'

Oct 30 13:33:51 esx01srv watchdog-hostd: Executing '/usr/sbin/vmware-hostd -u -a'

Oct 30 13:33:51 esx01srv watchdog-hostd: '/usr/sbin/vmware-hostd -u -a' exited after 0 seconds (quick failure 4)

Oct 30 13:33:51 esx01srv watchdog-hostd: Executing cleanup command '/usr/sbin/vmware-hostd-support'

Oct 30 13:33:52 esx01srv watchdog-hostd: Executing '/usr/sbin/vmware-hostd -u -a'

Oct 30 13:33:52 esx01srv watchdog-hostd: '/usr/sbin/vmware-hostd -u -a' exited after 0 seconds (quick failure 5)

Oct 30 13:33:52 esx01srv watchdog-hostd: Executing cleanup command '/usr/sbin/vmware-hostd-support'

Oct 30 13:33:53 esx01srv watchdog-hostd: Executing '/usr/sbin/vmware-hostd -u -a'

Oct 30 13:33:53 esx01srv watchdog-hostd: '/usr/sbin/vmware-hostd -u -a' exited after 0 seconds (quick failure 6)

Oct 30 13:33:53 esx01srv watchdog-hostd: Executing cleanup command '/usr/sbin/vmware-hostd-support'

Oct 30 13:33:54 esx01srv watchdog-hostd: End '/usr/sbin/vmware-hostd -u -a', failure limit reached

AS you may see seems that the vmware-hostd doesnt' exist or (for sure) it is not able to run...

Alex

I'v found this in the hostd.log :

Current value 204800 exceeds soft limit 122880.

Hw info file: /etc/vmware/hostd/hwInfo.xml

Config target info loaded

Current value 204828 exceeds hard limit 204800. Shutting down process.

END SERVICES

[

Karunakar · ‎11-02-2008

hi alex,

lets try a different option this time.

Looks like hostd rpm is not installed properly.

try to search for hostd rpm installed in the machine using the below command.

rpm -qa | grep hostd

this will display the rpm of hostd, try to remove the same using the below command.

rpm -e <hostd rpm>

Now try to install the same rpm from the esx cd.

after that restart mgmt-vmware service, this should work.

-Karunakar

alefesta · ‎11-04-2008

Hi K,

so I did as you suggested but I was unable to remove completly the hostd since it says that I had dependencies on other services, so I tried a more simple rpm -Uvh from the vmware CDROM and upgraded the hostd rpm...than restarted the service and everything came back online...

thanks again for your help.

alex

Karunakar · ‎11-04-2008

Hi Alex,

You are welcome.

Can you award points if this was helpfull.

-Karunakar

ESX3 · ‎02-13-2009

Hi, there , i am unable to login to VI client, it says connection failed and when i checked the service mgmt-vmware status its says " vmware-hostd stopped"

Mean while i would like to add, i have installed esx 3.0 on vmware workstation 6.0 .Today i installed esx 3.0 and was able to open the web page by the ip address, after i restarted my system in the evening, i am aunable to connect. Also, we have DHCP network. and i forgot to assign teh DNS ip address when installing the ESX server, and now when i check the network settings in service console, it has differnt DNS ip address than mine. example. it says 192.168.1.11, and my system DNS IP address is 192.168.254.222 and 213.43.10.10.. and nslookup command for my host name and ipdress in service console does not resolve .