This issue is resolved in vRealize Log Insight 8.1 and later.
To resolve this issue, update to vRealize Log Insight 8.1 or later, available at Broadcom Portal.
Workaround:
To workaround this issue, copy the trust store from the Primary node to the other nodes in the vRealize Log Insight cluster.
- Log into the vRealize Log Insight UI using the direct address of the Primary node.
Example: https://192.168.4.10/login
- Test the connection and accept the certificate for any SSL configured integrations such as vSphere, vRealize Operations, SMTP, Active Directory, and/or Forwarder nodes.
- Using an SCP Utility as the root user, copy the /usr/java/jre-vmware/lib/security/cacerts file from the vRealize Log Insight Primary node to the /usr/java/jre-vmware/lib/security/ directory of all other nodes in the vRealize Log Insight cluster.
Example: scp root@healthynode:/usr/java/jre-vmware/lib/security/cacerts /usr/java/jre-vmware/lib/security/
Note: Enter your healthy node's IP or Fully Qualified Domain name (FQDN) in place of healthynode above.