'service cyrus-imapd stop' fails to stop cyrus-imapd, silently

[Marius Gedminas]

$ pgrep -u cyrus
11769
11804

$ sudo service cyrus-imapd stop

$ pgrep -u cyrus
11769
11804
---
ApportVersion: 2.14.1-0ubuntu3.10
Architecture: amd64
DistroRelease: Ubuntu 14.04
Package: cyrus-imapd-2.4 2.4.17+caldav~beta9-3
PackageArchitecture: amd64
ProcVersionSignature: Ubuntu 3.13.0-51.84-generic 3.13.11-ckt18
Tags: trusty
Uname: Linux 3.13.0-51-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

_MarkForUpload: True

[Marius Gedminas (mgedmin)]

sudo service cyrus-imapd stop at least says it didn't work

$ pgrep -u cyrus
11769
11804

$ sudo service cyrus-imapd restart
 * Restarting Cyrus IMAPd cyrmaster
   ...fail!

$ pgrep -u cyrus
11769
11804

[Marius Gedminas (mgedmin)]

apport information

[Marius Gedminas (mgedmin)]

apport information

[Marius Gedminas (mgedmin)]

The init script is looking for /var/run/cyrmaster.pid, which doesn't exist. The actual pid file is /var/run/cyrus-master.pid

[Marius Gedminas (mgedmin)]

There was a similar upstream bug about PIDFILE mismatch: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=778781

Curiously it was just the reverse in Debian: the init script was looking for /var/run/cyrus-master.pid, but the software actually used /var/run/cyrus-master.pid.

[Frank Agerholm (8-frank-b)]

Workaround:

Set the PIDFILE-variable in /etc/default/cyrus-imapd:

PIDFILE=/var/run/cyrus-master.pid

Now the init script does not use its default any more an "stop" works for me...

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.