NTP time step too large: 13668 days

[pbabu6001]

Our ESA and SMA servers are receiving below Warning messages. Could you please let us know what does that mean? and how to resolve?

NTP time step too large: 13668 days (server 10.142.2.60 ip 10.142.2.60) [manual intervention required]

NTP time step too large: 13668 days (server 10.142.2.60 ip 10.142.2.60) [manual intervention required]

[marc.luescherFRE]

This error means that the system time and the actual time are not in synch.

Check NTP server IP and time zone applied and if you can access your timesource from the Ironports

If that all works then manual set the time on CLI with settime, enter the current time and date by hand and then enable via ntpconfig the ntp config again.

That should fix the issue

-Marc

[Libin Varghese]

Hi,

If the time on the system is off by six months or more, you will get this message in the logs:

Wed Nov 11 21:26:04 2009 Info: sntp query host 10.92.151.132 delay 510 offset 16158559567723
Wed Nov 11 21:26:04 2009 Warning: NTP time step too large: 187 days (server tock.example ip 10.92.151.132) [manual intervention required]

To fix this issue, manually set the time and date and then re-enable NTP:

example.local> settime

Once you've manually set the clock to a closer approximation, NTP will precisely adjust the clock.

Thank You!

Libin Varghese