This bug was fixed in the package dovecot - 1:1.2.9-1ubuntu4
---
dovecot (1:1.2.9-1ubuntu4) lucid; urgency=low
* debian/contorl: Recommend ntpdate. (LP: #347881)
-- Chuck ShortTue, 09 Mar 2010 14:30:15 -0500
** Changed in: dovecot (Ubuntu)
Status: Confirmed => Fix Rele
I would personally think this is an issue with ntpdate, specifically
with its hook in if-up.d. time shouldn't really run backwards.
I'm looking at karmic, that script (/etc/network/if-up.d/ntpdate) says:
| # This is a heuristic: The idea is that if a static interface is brought
| # up, that is
I get the same error.
ntp is installed - default configuration
ntpdate is installed
--
dovecot-imapd incompatible with ntpdate use
https://bugs.launchpad.net/bugs/347881
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dovecot in ubuntu.
I just reproduced this exact issue in Jaunty (dovecot
1:1.1.11-0ubuntu2). That is; I set my clock to run ahead, restarted my
network which triggered a ntpdate. Hence my clock was set back to the
correct time, leading to dovecot shutting itself down.
"dovecot: Fatal: Time just moved backwards by 42
