vAPI Endpoint Failed to connect warning message for multiple services on vCenter Server VAMI page
Article ID: 399481
Updated On:
Products
Issue/Introduction
- Services section in VC VAMI Page shows vAPI Endpoint Failed to Connect warning messages for multiple services.
- vAPI Endpoint logs shows Health Yellow errors while trying to connect to the respective services :
/var/log/vmware/vapi/endpoint/endpoint.log- below sample entries shows connectivity failure to Content Library, Topology and HVC services.YYYY-MM-DDTHH:MM:SS | INFO | state-manager1 | StatusInfoFactory | HEALTH YELLOW Failed to connect to <Service ID>\com.vmware.vcenter.hvc.vapi vAPI provider.YYYY-MM-DDTHH:MM:SS | INFO | state-manager1 | StatusInfoFactory | HEALTH YELLOW Failed to connect to <Service ID>\com.vmware.cis.cls.vapi vAPI provider.YYYY-MM-DDTHH:MM:SS | INFO | state-manager1 | StatusInfoFactory | HEALTH YELLOW Failed to connect to <Service ID>\com.vmware.topology.vapi vAPI provider.
Environment
vCenter Server 7.0.x
vCenter Server 8.0.x
Cause
This issue is observed when the respective services are in stopped state on the vCenter Server. If services are not running, vAPI endpoint will show "Connection refused" in the error stack when it is trying to check the health of the service.
/var/log/vmware/vapi/endpoint/endpoint.logYYYY-MM-DDTHH:MM:SS | WARN | state-manager1 | ApiInterfacesFactory | Retrieving interfaces for service <Service ID>\com.vmware.topology.vapi has failed.com.vmware.vapi.client.exception.ConnectionException: http://localhost:10098/topologysvc invocation failed with "java.net.ConnectException: Connection refused"
Resolution
- SSH to the vCenter Server
- Check the service status using "
service-control --status" command. - Start all the automatic services using command "
service-control --start --all".
Note: Respective service logs needs to be reviewed if the services are failing to start after executing start all command mentioned above.
Feedback
