[Dovecot] Time just moved backwards error even with ntpd

[Karsten Bräckelmann]

On Sat, 2008-01-19 at 12:46 +0100, Luigi Rosa wrote:
> Scenario: server PC abruptly switched off due to power cable problems 
> (an UPS cannot solve this issue), so during shutdown Linux was not 

This sounds like rather extreme, exceptional circumstances. And actually
an infrastructure problem, rather than software. ;)

> 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:

No. :)

> 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

Exactly one hour. Doesn't strike me as a coincidence...

  guenther


-- 
char *t="\10pse\0r\0dtu\0. at ghno\x4e\xc8\x79\xf4\xab\x51\x8a\x10\xf4\xf4\xc4";
main(){ char h,m=h=*t++,*x=t+2*h,c,i,l=*x,s=0; for (i=0;i<l;i++){ i%8? c<<=1:
(c=*++x); c&128 && (s+=h); if (!(h>>=1)||!t[s+h]){ putchar(t[s]);h=m;s=0; }}}