3.16.154 32341 - Server Chrony Daemon Never Synchronized

Alarm Group:

PLAT

Description:

This alarm indicates that the server is not synchronized with any NTP source and has not been synchronized since the last configuration change.

Severity:

Major

Instance:

May include AlarmLocation, AlarmId, AlarmState, AlarmSeverity, and bindVarNamesValueStr.

HA Score:

Normal

Auto Clear Seconds:

0 (zero)

OID:

eagleXgDsrTpdChronyDaemonNeverSynchronizedNotify

Alarm ID:

TKSPLATMA42

Recovery:

1. Verify NTP settings and that NTP sources can be reached.
   1. Ensure ntpd service is running.
   2. Verify that the /etc/ntp.conf file consists the correct configuration for the server.
   3. Verify the ntp peer configuration; execute ntpq -p and analyze the output. Verify peer data, such as tally code (first column before remote), remote, refid, stratum (st), and jitter, are valid for server.
   4. Execute ntpstat to determine the ntp time synchronization status. If not synchronized or the stratum is not correct for server, then ping the ntp peer to determine if peer can be reached.
2. If the ntp peer is reachable, restart the ntpd service.
3. If the problem persists, then resetting the NTP date may resolve the issue.

   Note:

   Before resetting the NTP date, the applications may need to be stopped. After the NTP reset, the applications must be restarted.
   1. Perform the following commands to reset date:
   • sudo service ntpd stop
   • sudo ntpdate <ntp server IP>
   • sudo service ntpd start
4. For any assistance, contact My Oracle Support.