dovecot won't be restarted after failure
Bug #718188 reported by
Zrin Ziborski
This bug affects 3 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Dovecot |
Invalid
|
Undecided
|
Unassigned | ||
upstart |
Invalid
|
Undecided
|
Unassigned | ||
dovecot (Ubuntu) |
Fix Released
|
Low
|
Unassigned |
Bug Description
Binary package hint: upstart
Due to ntpdate (installed with ubuntu-minimal), the time was corrected backwards during boot, obviously after starting dovecot, causing
dovecot: Fatal: Time just moved backwards by 90 seconds. This might cause a lot of problems, so I'll just kill myself now. http://
after which dovecot was not restarted.
System: ubuntu 10.10 - maverick
Dovecot version: 1:1.2.12-1ubuntu8.1
installed packages: dovecot-common, dovecot-imapd, dovecot-pop3d (as daemons)
Related branches
description: | updated |
description: | updated |
To post a comment you must log in.
Hello Zrin, thank you for taking the time to file this bug report and help us make Ubuntu better!
This is actually a bug in the dovecot upstart job file. There is no 'respawn' keyword, so upstart will not restart the job when it exits with a non-normal exit, which it most certainly does when this error is displayed.
Redirecting to the dovecot package, Marking as Triaged, setting Importance to Low for now. Also closing the upstart and dovecot tasks as this does not actually concern them.
There may be another issue here though. Zrin, what runs ntpdate for you after normal services are started? Seems like giant deltas in time could cause some instability if done very late in the boot, and I want to make sure its not part of any default configuration we're shipping (though I think that would be a different bug).