OL : Incorrect Server time Even After Syncing NTP server
(Doc ID 2686589.1)
Last updated on MAY 30, 2022
Applies to:
Oracle Compute Cloud Service - Version N/A and laterInformation in this document applies to any platform.
Symptoms
A time drift of more than 150 years noticed on the server. NTP sync is unable to fix it.
# ntpdate -ud a.b.c.d 5 Aug 18:58:12 ntpdate[151695]: ntpdate 4.2.6p5@1.2349-o Wed Dec 19 17:34:23 UTC 2018 (1) Looking for host a.b.c.d and service ntp host found : <hostname> transmit(a.b.c.d) receive(a.b.c.d) transmit(a.b.c.d) receive(a.b.c.d) transmit(a.b.c.d) receive(a.b.c.d) transmit(a.b.c.d) receive(a.b.c.d) server a.b.c.d, port 123 stratum 4, precision -19, leap 00, trust 000 refid [a.b.c.d], delay 0.02597, dispersion 0.00000 transmitted 4, in filter 4 reference time: e2a45d35.40bf12d5 Thu, Aug 5 2156 18:57:57.252 originate timestamp: e2a45d44.48fd5e44 Thu, Aug 5 2156 18:58:12.285 transmit timestamp: e2a45d44.48e4e26d Thu, Aug 5 2156 18:58:12.284 filter delay: 0.02621 0.02600 0.02599 0.02597 0.00000 0.00000 0.00000 0.00000 filter offset: 0.000135 0.000154 0.000146 0.000154 0.000000 0.000000 0.000000 0.000000 delay 0.02597, dispersion 0.00000 offset 0.000154 5 Aug 18:58:12 ntpdate[151695]: adjust time server a.b.c.d offset 0.000154 sec
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Cause |
| Solution |