Running (Embedded PSC) vCenter Server Appliance 6.5.0b | 14 MARCH 2017 | ISO Build 5178943
Upgrade to vCenter Server Appliance 6.5 Update 1 | 27 JULY 2017 | Build 5973321 using VMware-vCenter-Server-Appliance-220.127.116.1100-5973321-patch-FP.iso
After the reboot an alarm for vapi-endpoint status changed from green to yellow appears. The vAPI Endpoint service is Running and the Health is good.
Restarting the service or the VSCSA again does not clear the alarm.
- Shut down the VCSA
- Take a snapshot while powered off, power on.
- Putty in (this would be run on an external PSC; untested since I have an Embedded deployment)
tail -20 endpoint.log | grep “HEALTH Failed to connect to”
2017-09-02T17:03:20.536-07:00 | INFO | state-manager1 | HealthConfigurationEventListener | HEALTH Failed to connect to 7e00fc36-7353-4d79-8387-4349ea5d7414com.vmware.cis.cls.vapi vAPI provider.
- Replace the ID with the one above from your system. I could not find a way to prompt for a password so “history -c” will be run later. Be careful of copy/paste has — maybe copied as one line, but it is dash-dash.
/usr/lib/vmidentity/tools/scripts/lstool.py unregister –url http://localhost:7080/lookupservice/sdk –id 7e00fc36-7353-4d79-8387-4349ea5d7414 –user ‘email@example.com’ –password ‘VMware1!’ –no-check-cert
- Restart the vAPI Endpoint service