VMware vAPI Endpoint Service Health Alarm vCenter 6.7

 

  1. Shut down the VCSA
  2. Take a snapshot while powered off, power on.
  3. Putty in  (this would be run on an external PSC; untested since I have an Embedded deployment)
    cd /var/log/vmware/vapi/endpoint
    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.
  4. 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 ‘administrator@vsphere.local’ –password ‘VMware1!’ –no-check-cert

Comments

Popular posts from this blog

Extracting and using a modified VMWare Player BIOS or UEFI firmware

Activate Synology Active Backup for Business for DSM 6

Windows 11 internet/account bypass