After more investigation it seems that the issue is triggered by
managesieve: when managesieve is enabled dovecot forks multiple times
which leads upstart to loose track of it. If managesieve is disabled
upstart is correctly tracking dovecot.

The posted debdiff fixes the problem. Please upload to Maverick.

** Changed in: dovecot (Ubuntu Maverick)
       Status: Confirmed => In Progress

** Summary changed:

- dovecot-postfix and upstart incompatibility
+ upstart unable to correctly track dovecot daemon when managesieve plugin is 
enabled

** Description changed:

+ 
+ When the managesieve plugin is enabled it seems that dovecot forks once more 
than what upstart expects. Upstart tracks the wrong pid with "expect fork" set.
+ 
+ ============
+ Original description
+ 
  Binary package hint: dovecot-postfix
  
  Dovecot on Maverick is now using upstart to launch dovecot. When
  dovecot-postfix is installed, the dovecot must have some component as
  root (for SASL authentification purpose, in order to write to postfix
  chroot). Problem is, the system can start dovecot on boot, but any
  attempt into using restart dovecot will result in a hang of upstart.
  CTRL+C can cancel it, but then dovecot is in a strange state, with half
  the processus presents in memory. This is not the correct behavior, as
  we except a smooth restart of such an important service of the mail
  (especially if SASL authentification of postfix is involved).
  
- As a workaround, I replace the symlink to upstart by the old init.d original 
script from ubuntu 10.04.1. 
+ As a workaround, I replace the symlink to upstart by the old init.d original 
script from ubuntu 10.04.1.
  I try to figure out a clean solution, but apparently this is inherent to 
upstart and explains why some package, such as apache, did not go on the 
upstart train already.

** Also affects: upstart (Ubuntu)
   Importance: Undecided
       Status: New

-- 
upstart unable to correctly track dovecot daemon when managesieve plugin is 
enabled
https://bugs.launchpad.net/bugs/646858
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to