Authd error: 514 Error connecting to hostd-vmdb service instance.
Failed to connect to host :902. Check that authd is running correctly (lib/connect error 11)
.Unable to access the specified host. It either does not exist, the server software is not responding, or there is a network problem.
VMware Infrastructure Client could not establish the initial connection with server your server. Details: A connection failure occurred.
Unable to access the specified host. It does not exist, the server software is not responding, or there is a network problem.
The vmware-hostd
management service is the main communication channel between ESX/ESXi hosts and VMkernel. If vmware-hostd
fails, ESX/ESXi hosts disconnects from vCenter Server/VirtualCenter and cannot be managed, even if you try to connect to the ESX/ESXi host directly. When this happens, you see these errors.
To resolve this issue, validate that each troubleshooting step below is true for your environment. The steps provide instructions or a link to a document, for validating the step and taking corrective action as necessary. The steps are ordered in the most appropriate sequence to isolate the issue and identify the proper resolution. After each step, attempt to restart the management agents. Do not skip a step.
Note: For information on restarting mgmt-vmware
, see Restarting the Management agents on an ESX or ESXi Server (1003490).
vmware-hostd
is running. For more information, see Verifying that the Management Service is running on an ESX host (1003494) and Verifying if management services are running on an ESXi host (2030663)./etc/hosts
file is written correctly and has entries similar to:# Do not remove the following line, or various programs
# that require network functionality will fail.
127.0.0.1 <localhost>.<localdomain> <localhost>
10.0.0.1 <server>.<domain> <server>
/
or /var/log
is full, then vmware-hostd
cannot start because it is trying to write information to a full disk. For more information on disk space usage on the ESX host, see Investigating disk space on an ESX or ESXi host (1003564).ls /vmfs/volumes
vdf -h
/etc/vmware/esx.conf
is not missing or corrupt. If the file is missing or corrupt, replace it with a backup copy from/var/log/oldconf/
. For more information, see Troubleshooting an ESX host that does not boot (10065)./etc/vmware/firewall/services.xml
file:/var/log/vmware/hostd.log
for these errors:['ServiceSystem' 3076444288 verbose] Command finished with status 0
['FirewallSystem' 3076444288 verbose] Loading firewall configuration file '/etc/vmware/firewall/services.xml'
['App' 3076444288 panic] Application error: no element found
esxcfg-firewall -q
No element found at line 480, column 0, byte 11664 at /usr/lib/perl5/vendor_perl/5.8.0/i386-linux-thread-multi/XML/Parser.pm line 185
esxtop
vmware-hostd
is using more than 90% CPU, increase the amount of memory that is assigned to the ESX service console (valid for ESX only). For more information, see Increasing the amount of RAM assigned to the ESX Server service console (1003501).cmahostd
is consuming CPU. If this process is running, upgrade HP Insight Manager.If additional assistance is required for any of the above steps, file a support request with VMware Support and note this KB Article ID (1002849) in the problem description. For more information, see How to Submit a Support Request.
vmware-hostd
service fails to start, perform these troubleshooting steps:mgmt-vmware
./etc/vmware/firewall
directory for any files other than service.xml
. If there are any extraneous files in the directory, move them to an alternate location./etc/vmware/hostd/config.xml
by looking for blank hostd
logs. If the config.xml
file is corrupt, reinstall it:\VMware\RPMS\VMware-hostd-xxxxx.i386.rpm
.hostd
for the version ESX that you are using. To find the exact version of hostd
you are using, run this command:rpm -qa | grep hostd
rpm -ivh --replacepkgs VMware-hostd-xxxxx.i386.rpm
['App' 3076436096 panic] Backtrace generated
If the issue continues to exist after trying the steps in this article: