[Dovecot] Time just moved backwards error even with ntpd

Ralf Hildebrandt Ralf.Hildebrandt at charite.de
Sat Jan 19 14:16:29 EET 2008


* Luigi Rosa <lrosa at hypertrek.info>:
> Scenario: server PC abruptly switched off due to power cable problems (an 
> UPS cannot solve this issue), so during shutdown Linux was not able to 
> resinchronize the system clock. After a few hours the server come back on, 
> Linux booted and the services (ntpd, dovecot and many others) started
>
> But the system clock was 45 minutes ahead, so:
>
> Jan 19 11:13:39 gw ntpd[2112]: synchronized to LOCAL(0), stratum 10
> Jan 19 11:13:39 gw ntpd[2112]: kernel time sync disabled 0041
> Jan 19 11:14:43 gw ntpd[2112]: synchronized to 62.48.35.100, stratum 2
> Jan 19 10:31:55 gw ntpd[2112]: time reset -3600.221385 s
> Jan 19 10:31:55 gw ntpd[2112]: kernel time sync enabled 0001
> Jan 19 10:31:55 gw dovecot: Time just moved backwards by 3600 seconds. This 
> might cause a lot of problems, so I'll just kill myself now. 
> http://wiki.dovecot.org/TimeMovedBackwards

Solution: Start ntpdate/ntpd FIRST.

-- 
Ralf Hildebrandt (Ralf.Hildebrandt at charite.de)             plonk at charite.de
Postfix - Einrichtung, Betrieb und Wartung       Tel. +49 (0)30-450 570-155
http://www.arschkrebs.de
I realise computers suck. The only reason why they are a hobby of mine
is because I enjoy pain! 


More information about the dovecot mailing list