ESXi hosts are disconnected from vCenter and failed to reconnect

Products

• VMware vCenter Server
• VMware vSphere ESXi

Issue/Introduction

Symptoms:

• ESXi hosts are disconnected from vCenter server
• HA alerts that the host is not in sync with vCenter server

 

Environment

• VMware vCenter Server Appliance 7.0.x
• VMware vSphere ESXi 7.x
• VMware vCenter Server 8.x
• VMware vSphere ESXi 8.x
  
  

 

Cause

• vCenter Server fails to resolve ESXi host names, either due to an unreachable DNS server or missing DNS entries for the ESXi host(s).
• In the vpxd.log file, you see entries similar to:

YYYY-MM-DDTHH:MM:SS info vpxd[7F4EA0D31700] [Originator@6876 sub=vpxLro opID=1b###3ce] [VpxLRO] -- FINISH task-internal-8993588

YYYY-MM-DDTHH:MM:SS warning vpxd[7F4EA0D31700] [Originator@6876 sub=Default] Failed to resolve address; <resolver p:0x00007f4df4cd0770, 'exampleESXi.vsphere.local:443'>, e: asio.netdb:1(Host not found (authoritative))

YYYY-MM-DDTHH:MM:SS error vpxd[7F4EA0D31700] [Originator@6876 sub=HttpConnectionPool-000000] [ConnectComplete] Connect failed to <cs p:00007f4e18969a40, TCP:exampleESXi.vsphere.local:443>; cnx: (null), error: N7Vmacore15SystemExceptionE(Host not found (authoritative))

YYYY-MM-DDTHH:MM:SS error vpxd[7F4EA1037700] [Originator@6876 sub=Vmomi opID=HB-host-##@10590-75c56e63-TaskLoop-201f###f] [VpxdClientAdapter] Got vmacore exception: Host not found (authoritative)

YYYY-MM-DDTHH:MM:SS error vpxd[7F4EA1037700] [Originator@6876 sub=Vmomi opID=HB-host-##@10590-75c56e63-TaskLoop-201f###f] [VpxdClientAdapter] Backtrace:

-->

--> [backtrace begin] product: VMware VirtualCenter, version: X.Y.Z, build: build-#######, tag: vpxd

--> backtrace[00] libvmacore.so[0x003C6234]: Vmacore::System::Stacktrace::CaptureWork(unsigned int)

--> backtrace[01] libvmacore.so[0x001F01C3]: Vmacore::System::SystemFactoryImpl::CreateQuickBacktrace(Vmacore::Ref<Vmacore::System::Backtrace>&)

--> backtrace[02] libvmacore.so[0x0019A11D]: Vmacore::Throwable::Throwable(std::string const&)

--> backtrace[03] libvmacore.so[0x003BE26B]: Vmacore::SystemException::SystemException(int, std::string const&)

--> backtrace[04] libvmacore.so[0x002F7CB0]

--> backtrace[05] libvmacore.so[0x0034624A]

--> backtrace[06] libvmacore.so[0x00346703]

--> backtrace[07] libvmacore.so[0x00348CAB]

--> backtrace[08] libvmacore.so[0x0035B433]

--> backtrace[09] libvmacore.so[0x003550E6]

--> backtrace[10] libvmacore.so[0x00301E51]

--> backtrace[11] libvmacore.so[0x002FA672]

--> backtrace[12] libvmacore.so[0x002FE0D2]

--> backtrace[13] libvmacore.so[0x002FE2F0]

--> backtrace[14] libvmacore.so[0x00307ECA]

--> backtrace[15] libvmacore.so[0x003080E4]

--> backtrace[16] libvmacore.so[0x0035F7AE]

--> backtrace[17] libvmacore.so[0x0035FFEA]

--> backtrace[18] libvmacore.so[0x002F9E0B]

--> backtrace[19] libvmacore.so[0x003D0102]

--> backtrace[20] libpthread.so.0[0x00007806]

--> backtrace[21] libc.so.6[0x000DE9BD]

--> [backtrace end]

-->

YYYY-MM-DDTHH:MM:SS warning vpxd[7F4EA1037700] [Originator@6876 sub=VpxProfiler opID=HB-host-67@10590-75c56e63-TaskLoop-201f###f] TaskLoop [TotalTime] took 20022 ms

-> nslookup exampleESXi.vsphere.local

;; connection timed out; no servers could be reached

 

Resolution

To resolve this:

• Ensure the DNS servers are reachable from the environment.
• Verify that the ESXi hostnames and IP addresses are correctly registered in DNS.
• Test name resolution using nslookup or dig to confirm proper DNS functionality.