vpxd-svcs service does not start in vCenter Server because the configured DNS server does not respond
search cancel

vpxd-svcs service does not start in vCenter Server because the configured DNS server does not respond

book

Article ID: 459714

calendar_today

Updated On:

Products

VMware vCenter Server

Issue/Introduction

After a restart of vCenter Server or all of its services, the vpxd-svcs service does not start.

  • In /var/log/vmware/lookupsvc/lookupserver-default.log, LDAP searches to vmdird are completed only at intervals of more than a minute, and the connection eventually fails during the SASL bind.
[YYYY-MM-DDTHH:MM:SS pool-2-thread-4 WARN com.vmware.sso.interop.ldap.LdapErrorChecker] Error received by LDAP client: com.vmware.sso.interop.ldap.OpenLdapClientLibrary, error code: -1
[YYYY-MM-DDTHH:MM:SS pool-2-thread-4 WARN com.vmware.vim.lookup.impl.LdapStorage] Failed to connect to LDAP server, will retry; attempt:1 of 15, delay:5 sec
com.vmware.sso.interop.ldap.ServerDownLdapException: Can't contact LDAP server
        at com.vmware.sso.interop.ldap.OpenLdapClientLibrary.ldap_sasl_srp_bind_s(OpenLdapClientLibrary.java:781)
  • /var/log/vmware/dnsmasq.log shows the reverse lookup of the vCenter Server IP address being forwarded to the DNS server repeatedly. No reply or NXDOMAIN is recorded for these queries.
YYYY-MM-DDTHH:MM:SS dnsmasq[####]: query[PTR] ##.#.###.##.in-addr.arpa from 127.0.0.1
YYYY-MM-DDTHH:MM:SS dnsmasq[####]: forwarded ##.#.###.##.in-addr.arpa to ##.###.#.#
YYYY-MM-DDTHH:MM:SS dnsmasq[####]: query[PTR] ##.#.###.##.in-addr.arpa from 127.0.0.1
YYYY-MM-DDTHH:MM:SS dnsmasq[####]: forwarded ##.#.###.##.in-addr.arpa to ##.###.#.#
  • The DNS server configured on vCenter Server is not reachable from vCenter Server.
# ping ##.###.#.#
From ##.###.#.## icmp_seq=1 Destination Host Unreachable
From ##.###.#.## icmp_seq=2 Destination Host Unreachable

# nslookup ##.###.#.## ##.###.#.#
;; connection timed out; no servers could be reached

 

Environment

VMware vCenter Server 8.x

Cause

The DNS server configured on vCenter Server does not respond. The reverse lookup of the vCenter Server IP address is forwarded to the DNS server, and no response is returned.

Resolution

  1. Restore connectivity to the DNS server configured on vCenter Server, or change the DNS server to a reachable one. To change the DNS server, see KB 423207.
  2. Restart all vCenter Server services.
service-control --stop --all && service-control --start --all

Additional Information

Japanese version: vCenter Server で設定されている DNS サーバーが応答しない場合に vpxd-svcs サービスが起動しない(459716)

The following commands can be used to check whether DNS queries from vCenter Server receive a response.

 
grep -c "forwarded" /var/log/vmware/dnsmasq.log
grep -E "reply |NXDOMAIN" /var/log/vmware/dnsmasq.log | tail

For similar issues caused by malformed /etc/hosts, see the following articles.