Bug#766403: cyrus-common: Restarting Cyrus IMAPd: cyrmasterfind: `/run/cyrus/lock': No such file or directory

Ross Boylan ross at biostat.ucsf.edu
Wed Oct 22 20:58:23 UTC 2014


Package: cyrus-common
Version: 2.4.16-4+deb7u2
Severity: normal

Dear Maintainer,

   * What led up to the situation?
Before installation of cyrus I created a filesystem on a device, mkdir /var/spool/cyrus,
and then mounted the device on that mount point.
Installed cyrus.  Terminal shows:
Setting up db5.1-util (5.1.29-5) ...
Setting up libzephyr4 (3.0.2-2) ...
Setting up db-util (5.1.6) ...
Setting up db4.7-util (4.7.25-21) ...
Setting up db4.8-util (4.8.30-12) ...
Setting up cyrus-common (2.4.16-4+deb7u2) ...
Creating/updating cyrus user account...
dpkg-statoverride: warning: --update given but /var/run/cyrus does not exist
dpkg-statoverride: warning: --update given but /var/run/cyrus/socket does not exist
Adding user `cyrus' to group `sasl' ...
Adding user cyrus to group sasl
Done.
cyrus-common: Creating cyrus-imapd directories...Creating/updating cyrus control directories in /var/lib/cyrus...
Creating/updating partition spool /var/spool/cyrus/mail...
Creating/updating partition spool /var/spool/cyrus/news...
Trying to optimize Cyrus partitions, edit /etc/default/cyrus-imapd to disable...
Setting attributes to +S for  /var/spool/cyrus/mail...
Setting attributes to +S for  /var/spool/cyrus/news...
done.
cyrus-common: Creating empty user_deny database...done.
Setting up cyrus-common-2.4 (2.4.16-4+deb7u2) ...
find: `/run/cyrus/lock': No such file or directory
find: `/run/cyrus/proc': No such file or directory
Setting up cyrus-imapd-2.4 (2.4.16-4+deb7u2) ...
Setting up cyrus-imapd (2.4.16-4+deb7u2) ...

   * What exactly did you do (or not do) that was effective (or
     ineffective)?
I plan to look at the installation script and run the commands to create /var/run/cyrus and the 
socket subdirectory.

   * What was the outcome of this action?
Have not tried the fix.  After the cyrus installation I followed README.Debian.simpleinstall to step 6..
When I restarted cyrus:
# /etc/init.d/cyrus-imapd restart
Restarting Cyrus IMAPd: cyrmasterfind: `/run/cyrus/lock': No such file or directory
find: `/run/cyrus/proc': No such file or directory
.

   * What outcome did you expect instead?
That cyrus would restart.
I'm not entirely surprised there were problems given what I did.


Commentary:
It seems likely the installation script detected the existence of
/var/spool/cyrus and concluded there was an existing installation.
Note /var/spool/cyrus was not owned by cyrus, since that user didn't
exist when I created that directory.  It then tried to update
non-existent directories (see logs of the install) rather than create
them.

Wanting to put the cyrus spool on a separate partition doesn't seem
that unusual to me; it would be nice if the installer could handle
this case.  I guess people typically install and then fool around with
things.


-- System Information:
Debian Release: 7.7
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.2.0-4-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages cyrus-common depends on:
ii  adduser                3.113+nmu3
ii  db-util                5.1.6
ii  db4.7-util             4.7.25-21
ii  db4.8-util             4.8.30-12
ii  db5.1-util             5.1.29-5
ii  debconf [debconf-2.0]  1.5.49

cyrus-common recommends no packages.

cyrus-common suggests no packages.

-- Configuration Files:
/etc/logcheck/ignore.d.server/cyrus-imapd [Errno 13] Permission denied: u'/etc/logcheck/ignore.d.server/cyrus-imapd'
/etc/logcheck/violations.ignore.d/cyrus-imapd [Errno 13] Permission denied: u'/etc/logcheck/violations.ignore.d/cyrus-imapd'

-- debconf information:
* cyrus-common/removespools: false



More information about the Pkg-Cyrus-imapd-Debian-devel mailing list