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 cl...@ubuntu.com Thu, 09 Aug 2012 12:22:52
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.
--
You received this bug notification because you are a
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 cl...@ubuntu.com Thu, 09 Aug 2012 12:22:52
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.
--
You received this bug notification because you are a
ping - this still hurts on natty. Please fix!
--
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
To manage notifications about
ping - this still hurts on natty. Please fix!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/718188
Title:
dovecot won't be restarted after failure
To manage notifications about this bug go to:
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
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
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
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
** Description changed:
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,
** Also affects: upstart
Importance: Undecided
Status: New
** Also affects: dovecot
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/718188
Title:
12 matches
Mail list logo
