3.16.173 32509 - Server Chrony Daemon Not Synchronized

Alarm Group:

PLAT

Description:

This alarm indicates the NTP daemon (background process) has been unable to locate a server to provide an acceptable time reference for synchronization.

Severity:

Minor

Instance:

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

HA Score:

Normal

Auto Clear Seconds:

0 (zero)

OID:

eagleXgDsrTpdChronyDaemonNotSynchronizedWarningNotify

Alarm ID:

TKSPLATMI10

Recovery:

1. Verify the NTP settings and ensure that the NTP servers are reachable.
   1. Ensure ntpd service is running.
   2. Verify the content of the /etc/ntp.conf file is correct 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 ntp peer is reachable, restart the ntpd service.
3. If 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. Run 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.