Loading...
Loading...
After upgrading VMware Aria Operations: There is a time difference across nodes in the VMware Aria Operations cluster.The ntpd service is down on one or mode nodes. Note: Run the systemctl status ntpd command on a node to get the status of the NTPD service.Example:#systemctl status ntpdntpd.service - Network Time ServiceLoaded: loaded (/usr/lib/systemd/system/ntpd.service; enabled; vendor preset: disabled)Active: inactive (dead) since Tue 2023-08-01 11:33:24 UTC; 1s agoDocs: man:ntpdProcess: 862 ExecStart=/usr/bin/ntpd -g -u ntp:ntp (code=exited, status=0/SUCCESS)Main PID: 874 (code=exited, status=0/SUCCESS)
Failure to resolve this issue can lead to time drift between cluster nodes, which can cause failures in product upgrader and bringing the cluster online, among other issues.
To resolve the issue, disable the systemd-timesyncd service and start the ntpd service.Complete the following on all Analytics nodes (Primary, Replica (if present), and Data nodes) simultaneously. Log into the Analytics node as root via SSH or Console.Run the following command to stop and disable the systemd-timesyncd service: systemctl stop systemd-timesyncd && systemctl disable systemd-timesyncd Run the following command to start the ntpd service: systemctl start ntpd Run the following command and cross reference between nodes to verify that the times are now synced across nodes: date
Click on a version to see all relevant bugs
VMware Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.