ntpd

NTPD exceeds sanity limit

Output /var/log/messages

Sep 13 09:10:27 friedrich ntpd[18024]: ntpd 4.2.4p5-a (1)
Sep 13 09:10:35 friedrich ntpd[18024]: time correction of 7202 seconds exceeds
sanity limit (1000); set clock manually to the correct UTC time.

run:

ntpd -qg

-q
Exit the ntpd just after the first time the clock is set.
This behavior mimics that of the ntpdate program, which is
to be retired. The -g and -x options can be used with this
option.

-g
Normally, ntpd exits if the offset exceeds the sanity limit,
which is 1000 s by default. If the sanity limit is set to
zero, no sanity checking is performed and any offset is
acceptable. This option overrides the limit and allows the
time to be set to any value without restriction; however,
this can happen only once. After that, ntpd will exit if the
limit is exceeded. This option can be used with the -q option.

Output /var/log/messages:

Sep 13 09:12:51 friedrich ntpd[18173]: ntpd 4.2.4p5-a (1)
Sep 13 11:13:01 friedrich ntpd[18173]: time reset +7201.890437 s