vc-ws1a-broker service cannot be started with the accesscontrol-service.log logs showing "Name or service not known"

Products

• VMware vCenter Server

Issue/Introduction

vc-ws1-broker service fails to start.

The /var/log/vmware/vc-ws1a-broker/accesscontrol-service.log shows the following error. 

2026-01-14T19:41:29,259 ERROR 10.252.129.146:accesscontrol (main) [-;-;-;-;-;-;-] org.springframework.boot.SpringApplication - Application run failed org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'OTARemovalJob' defined in URL [jar:file:/opt/vmware/idm/accesscontrol/BOOT-INF/lib/access-control-business-0.0.1-SNAPSHOT.jar!/com/vmware/vidm/accesscontrol/OTARemovalJob.class]: Bean instantiation via constructor failed; nested exception is org.springframework.beans.BeanInstantiationException: Failed to instantiate [com.vmware.vidm.accesscontrol.OTARemovalJob]: Constructor threw exception; nested exception is java.net.UnknownHostException: <VC_FQDN>: <VC_FQDN>: Name or service not known

 

Environment

vCenter 7.x/8.x/9.x

vCenter is deployed with its PNID as its IP Address.

The vCenter's Network was configured in the VAMI with a hostname. 

Cause

Issue is due to the DNS failure of vCenter to connect to its own hostname. 

Resolution

Validate that the /etc/hosts file is correct. 

If it is not, then update it via the VAMI(https://vCenter_fqdn:5480) under its networking configuration. 

Afterwards, reboot the vCenter and then validate that the /etc/hosts file has changed to the correct value.