dovecot won't be restarted after failure

Bug #718188 reported by Zrin Ziborski on 2011-02-13
18
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Dovecot
Invalid
Undecided
Unassigned
upstart
Undecided
Unassigned
dovecot (Ubuntu)
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://wiki.dovecot.org/TimeMovedBackwards

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
Clint Byrum (clint-fewbar) wrote :

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).

affects: upstart (Ubuntu) → dovecot (Ubuntu)
Changed in dovecot (Ubuntu):
importance: Undecided → Low
status: New → Triaged
Changed in upstart:
status: New → Invalid
Changed in dovecot:
status: New → Invalid
Zrin Ziborski (zrin+launchpad) wrote :

Hiello Clint,
thank you for responding and corrections.

I've just installed the packages using aptitude -
it happens on the (first) run of ntpdate, while starting services.
I've noticed there is some code trying to address this
problem, it seems logical at first sight
I do not see why it is not working.

ping - this still hurts on natty. Please fix!

Launchpad Janitor (janitor) wrote :

This bug was fixed in the package dovecot - 1:2.1.7-1ubuntu2

---------------
dovecot (1:2.1.7-1ubuntu2) quantal; urgency=low

  * d/dovecot-core.dovecot.upstart: Respawn to handle unexpected but
    recoverable problems. (LP: #718188)
 -- Clint Byrum <email address hidden> Thu, 09 Aug 2012 12:22:52 -0700

Changed in dovecot (Ubuntu):
status: Triaged → Fix Released
Clint Byrum (clint-fewbar) wrote :

Hi Matthias. We generally reserve stable release updats for high/critical importance bugs. There is an easy workaround for this one. If you edit /etc/init/dovecot.conf and add (on its own line) this:

respawn

That should do the trick.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers