vCenter Collection Status = Unknown and not seeing vCenter logs

Products

• VMware Aria Suite

Issue/Introduction

Integrations / vSphere Page shows VC Collection Status = Unknown

 

Environment

VMware Aria Operations for Logs 8.18

Cause

This is a known issue supported by a log message in /storage/core/loginsight/var/runtime.log similar to the below:

["ScheduledPluginServiceScheduledTask-thread-2"/10.xx.xx.xx ERROR] [com.vmware.loginsight.scheduled.ScheduledPluginService] [Could not get the connected cluster nodes to reassign vSphere integrations to them]

Resolution

Workaround: Edit the reference to the standalone (primary) node in the /internal/config page to use the IP address of the node instead of the existing FQDN. 

Changing internal configuration options in VMware Aria Operations for Logs describes how to perform edits on the /internal/config page.

ORIGINAL:

 <distributed overwrite-children="true">
    <daemon host="ariaoperationsforlogs.example.com" port="16520" token="c2c3015c-ad6c-472d-b7f3-dcac7d70020d">
      <service-group name="standalone" />
    </daemon>
    <daemon host="10.xx.xx.xx" port="16520" token="c7da646f-c7e4-4359-8bbf-64c8ef7be011">
      <service-group name="workernode" />
    </daemon>
    <daemon host="10.xx.xx.xx" port="16520" token="341ce09c-5ef1-4c73-a597-b7761d71c193">
      <service-group name="workernode" />
    </daemon>
  </distributed>

EDITED:

<distributed overwrite-children="true">
    <daemon host="10.xx.xx.xx" port="16520" token="c2c3015c-ad6c-472d-b7f3-dcac7d70020d">
      <service-group name="standalone" />
    </daemon>
    <daemon host="10.xx.xx.xx" port="16520" token="c7da646f-c7e4-4359-8bbf-64c8ef7be011">
      <service-group name="workernode" />
    </daemon>
    <daemon host="10.xx.xx.xx" port="16520" token="341ce09c-5ef1-4c73-a597-b7761d71c193">
      <service-group name="workernode" />
    </daemon>
</distributed>