VMware Aria Operations UI Fails to Load and Nodes Stuck on Waiting for Analytics

Products

• VMware Aria Operations (formerly vRealize Operations) 8.x

Issue/Introduction

VMware Aria Operations UI fails to load following a cluster restart. In the Admin UI, nodes remain stuck on the "Waiting for Analytics" status.

The analytics.log file contains errors similar to the following: /storage/log/vcops/log/analytics-xxxxxx.log

INFO [Analytics Main Thread] com.vmware.statsplatform.persistence.sqldb.SQLHAInfoCache.printPublishedMasterInfo - node role: MASTER,  master connection:  jdbc:postgresql://IP:5433/vcopsdb?ssl=true&  sslfactory=org.postgresql.ssl.LibPQvROpsFactory&  sslmode=verify-ca,  master connection timestamp: 
INFO [Analytics Main Thread] com.vmware.statsplatform.persistence.sqldb.SQLDBHAManagerImpl.waitForOtherNodesToPublishMasterDB - sleep for 10 seconds and check again.
INFO [Analytics Main Thread] com.vmware.statsplatform.persistence.sqldb.SQLDBHAManagerImpl.waitForOtherNodesToPublishMasterDB - 1 out of 2 have published its master db knowledge
ERROR [Thread-8] com.integrien.alive.controller.ControllerStartupMonitorThread.run - Controller did not start within 60 minutes. - Restarting analytics.
INFO [Thread-8] com.vmware.vcops.platform.common.PlatformEnvironment.exitSystem - Terminating process with exit code -1 ...

Environment

Aria Operations 8.17
Aria Operations 8.18

Cause

This issue occurs due to a time skew (NTP synchronization mismatch) between the nodes in the Aria Operations cluster.

Resolution

• Log in to all Aria Operations cluster nodes as the root user via SSH or the virtual machine console.
• Verify the current system time and NTP configuration on each node to identify the drift.
• Correct the time synchronization settings so that all cluster nodes share the exact same time.
• Once the time skew is resolved, restart the service using the command: systemctl restart analytics.service