vRealize Operations Cluster fails to start with the status Waiting for Analytics
book
Article ID: 315903
calendar_today
Updated On:
Products
VMware Aria Suite
Issue/Introduction
Symptoms:
After performing a disaster recovery operations or a cluster-wide reboot of vRealize Operations, you see these symptoms:
vRealize Operations Administrator interface (https://<vRealize_Operations_FQDN>/admin) may report the status message:
Waiting for Analytics
vRealize Operations Administrator interface (https://<vRealize_Operations_FQDN>/admin) display the that nodes are not coming online:
In the vRealize Operations Primary or Primary Replica node's ntp logs (located at: /var/log/), you may observe:
ntpd[9764]: no reply; clock not set ntpd[9798]: ntpd exiting on signal 15
In the vRealize Operations Primary or Primary Replica node's analytics-wrapper.log (located at: /storage/log/vcops/logs/), you may observe:
INFO | jvm 1 | YYYY/MM/DD <time> | >>> AnalyticsMain.run failed with error: IllegalStateException: time difference between servers is 37110 ms. It is greater than 30000 ms. Unable to operate, terminating...
</time>
Note: The time difference between servers will be unique to the time drift between the vRealize Operation nodes.
This issue occurs due to NTP time drift between the vRealize Operations nodes.
Resolution
To resolve this issue:
Ensure all NTP servers configured for use with the vRealize Operations nodes (Analytics and Remote Collector Clusters) are accessible
Update the ntp.conf file (located in /etc/) with new NTP server(s) in each vRealize Operations node if the original NTP servers are no longer available.
For more information, consult Configure NTP on VMware Appliances in the vRealize Operations Help Guide.