a customer had the problem that, due to outdated DNS Server settings, vCenter didn’t start all services. Connecting with a browser just show “No healthy upstreams” and the login to the VCSA GUI takes a long time.
Login by ssh, and checking the services, showed that the lookupsvc hangs during start:
root@myvCenter [ /var/log ]# service-control --status Running: applmgmt lwsmd observability vmafdd vmcad vmdird vmware-eam vmware-envoy vmware-pod vmware-postgres-archiver vmware-rhttpproxy vmware-statsmonitor vmware-vdtc vmware-vmon vmware-vpostgres vtsdb StartPending: lookupsvc
The attempt to change the DNS server with the VCSA GUI at port 5480 had also failed. So the only way was to change the network configuration is the command line.
root@myvCenter [ ~ ]# /opt/vmware/share/vami/vami_config_net 0) Show Current Configuration (scroll with Shift-PgUp/PgDown) 1) Exit this program 2) Default Gateway 3) Hostname 4) DNS 5) Proxy Server 6) IP Address Allocation for eth0
To change the DNS Server use option 4
root@myvCenter [ ~ ]# /opt/vmware/share/vami/vami_config_net 4 overwritten by information from the DHCP server. Type Ctrl-C to go back to the Main Menu DNS Server 1 [127.0.0.1]: DNS Server 2 (optional) : 10.200.10.20 Domain Name (optional) : myDomain.org Search Path (space separated) (optional) : myDomain.org
After changing to a valid DNS server, it was possible to add a second DNS bei VCSA GUI.