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).
** Package changed: upstart (Ubuntu) => dovecot (Ubuntu)
** Changed in: dovecot (Ubuntu)
Importance: Undecided => Low
** Changed in: dovecot (Ubuntu)
Status: New => Triaged
** Changed in: upstart
Status: New => Invalid
** Changed in: dovecot
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dovecot in ubuntu.
https://bugs.launchpad.net/bugs/718188
Title:
dovecot won't be restarted after failure
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
