On Sunday 06 November 2005 03:00, Synthetic Cartoonz wrote:
My home ntpd server refused to accept the time update from the *.us.pool.ntp.org server pool, reporting this nastygram in the ntp log: "time correction of -3599 seconds exceeds sanity limit (1000); set clock manually to the correct UTC time." The system's reported time was about an hour off due to the clock change last week and the fact that the server was down on that day (lack of electricity due to a recent hurricane), so the automatic change never occurred on the server.
The reason for this is that you have your CMOS clock set to local time. If you had it set to UTC there wouldn't have been a problem In general, the hardware clock should always be set to UTC, it just makes everything else so much easier.