[ntp:questions] ntpd: time reset problem

David Mills mills at udel.edu
Fri Sep 11 19:15:07 UTC 2009


Frank,

The message

Sep 10 21:21:02 seymour dovecot: dovecot: Fatal: Time just moved backwards by 434 seconds. [ ... ]

Is not in the software distribution from here. Apparently, your version of ntpd has been modified. Even so, the probably cause is a defective server your protostats file should have more detailed information.

Dave

Frank Elsner wrote:

>Hello *,
>
>strange happening yesterday. See this logfile lines:
>
>Sep 10 20:45:52 seymour ntpd[9104]: synchronized to 192.53.103.108, stratum 1
>Sep 10 20:58:07 seymour ntpd[9104]: synchronized to 134.34.3.18, stratum 1
>Sep 10 21:21:02 seymour dovecot: dovecot: Fatal: Time just moved backwards by 434 seconds. [ ... ]
>Sep 10 21:26:36 seymour ntpd[9104]: no servers reachable
>Sep 10 21:42:56 seymour ntpd[9104]: synchronized to 192.53.103.104, stratum 1
>Sep 10 21:50:55 seymour ntpd[9104]: time reset +434.824810 s
>Sep 10 21:54:09 seymour ntpd[9104]: synchronized to 130.149.7.71, stratum 2
>Sep 10 21:55:07 seymour ntpd[9104]: synchronized to 129.69.1.153, stratum 1
>
>
>What happened to the clock between 20:58:07 and 21:42:56?
>I guess ntpd should never set the time the hard way.
>The software is ntp-4.2.4p2-1.fc6. Yes, I know it's old.
>
>The dovecot issue is not a topic, it just triggered my attention :-)
>
>
>
>--Frank Elsner
>
>_______________________________________________
>questions mailing list
>questions at lists.ntp.org
>https://lists.ntp.org/mailman/listinfo/questions
>  
>




More information about the questions mailing list