1

Topic: Dovecot 1.2.16 problem with time

I use latest stable iRedMail release on CentOS 5.8 64-bit.

When I reboot my server I get the following:

Mar 08 22:15:54 dovecot: Fatal: Time just moved backwards by 12 seconds. This might cause a lot of problems, so I'll just kill myself now. http://wiki.dovecot.org/TimeMovedBackwards
Mar 09 00:31:24 dovecot: Info: Dovecot v1.2.16 starting up (core dumps disabled)
Mar 09 00:31:55 dict: Info: mysql: Connected to 127.0.0.1 (iredadmin)
Mar 09 00:33:49 dovecot: Fatal: Time just moved backwards by 13 seconds. This might cause a lot of problems, so I'll just kill myself now. http://wiki.dovecot.org/TimeMovedBackwards

My servers are in Switzerland and I use ntpd on ch.pool.ntp.org, so the time should be synched ok. According to the dovecot wiki version 2.0 of dovecot should do a better job, regarding the handling of moving back the systemtime.

Does iRedmail support dovecot 2.x? Or do I really write a script as suggested in the wiki vor dovecot version < 2.x??

2

Re: Dovecot 1.2.16 problem with time

Please refer to this link as suggested: http://wiki.dovecot.org/TimeMovedBackwards

iRedMail will install Dovecot-2.x by default on CentOS/RHEL 6.x, but Dovecot-1.2.x on CentOS/RHEL 5.x.