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:
tpdNTPDeamonNotSynchronizedWarning
Alarm ID:
TKSPLATMI10
Recovery:
Verify NTP settings and that NTP sources can be
reached.
Ensure ntpd service is running.
Verify the content of the /etc/ntp.conf file is
correct for the server.
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.
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.
If ntp peer is reachable, restart the ntpd service.
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 and, subsequent to the ntp reset, the application
restarted.
To reset date:
sudo service ntpd stop
sudo ntpdate <ntp server
IP>
sudo service ntpd start
If the problem persists, it is recommended to
contact
My Oracle Support.