Bug#611546: /etc/init.d/cyrus2.2: You are missing a dpkg-statoverride on /var/run/cyrus. Add it.

Tue Feb 1 13:55:06 UTC 2011

On Monday, 2011-01-31 at 15:03:55 -0200, Henrique de Moraes Holschuh wrote:
> On Sun, 30 Jan 2011, Lupe Christoph wrote:
> > This message is probably cryptic enough to confuse the average Debian user. "Why
> > do I need that, and how do I do it?" is the most likely reaction.

> Yeah, it is less helpful than it could be as a punishment for the user who
> deletes the statoverrides, as in "since you messed with it, now you get to
> learn what it does the hard way".  It has been like that for many years.

Since I never tocuhed the overrides, I feel undervedly punished ;-)

> From that, you can correctly infer that it should NEVER happen normally.

Welllll...

> So, we do have some nasty bug in the packages, or something bad happened to
> your system that damaged the statoverrides.

Fortunately, I do a backup of this system with rsnapshot, so I can see
when /var/lib/dpkg/statoverride changed:

-rw-r--r-- 5 root root 675 2010-06-10 10:41 monthly.5/var/lib/dpkg/statoverride
-rw-r--r-- 5 root root 675 2010-06-10 10:41 monthly.4/var/lib/dpkg/statoverride
-rw-r--r-- 5 root root 675 2010-06-10 10:41 monthly.3/var/lib/dpkg/statoverride
-rw-r--r-- 5 root root 675 2010-06-10 10:41 monthly.2/var/lib/dpkg/statoverride
-rw-r--r-- 5 root root 675 2010-06-10 10:41 monthly.1/var/lib/dpkg/statoverride
-rw-r--r-- 9 root root 514 2010-12-27 11:54 weekly.2/var/lib/dpkg/statoverride
-rw-r--r-- 9 root root 514 2010-12-27 11:54 weekly.1/var/lib/dpkg/statoverride
-rw-r--r-- 9 root root 514 2010-12-27 11:54 weekly.0/var/lib/dpkg/statoverride
-rw-r--r-- 9 root root 514 2010-12-27 11:54 monthly.0/var/lib/dpkg/statoverride
-rw-r--r-- 9 root root 514 2010-12-27 11:54 daily.6/var/lib/dpkg/statoverride
-rw-r--r-- 9 root root 514 2010-12-27 11:54 daily.5/var/lib/dpkg/statoverride
-rw-r--r-- 9 root root 514 2010-12-27 11:54 daily.4/var/lib/dpkg/statoverride
-rw-r--r-- 9 root root 514 2010-12-27 11:54 daily.3/var/lib/dpkg/statoverride
-rw-r--r-- 9 root root 514 2010-12-27 11:54 daily.2/var/lib/dpkg/statoverride
-rw-r--r-- 2 root root 581 2011-01-30 17:02 daily.1/var/lib/dpkg/statoverride
-rw-r--r-- 2 root root 581 2011-01-30 17:02 daily.0/var/lib/dpkg/statoverride

The latest two are after I entered the overrides for /var/run/cyrus and
/var/run/cyrus/socket manually. So it happened between 2010-06-10 and
2010-12-27. Since I rarely reboot this server, I noticed the problem too
late for any better precision.

In that time range I upgraded the server, and it retained
cyrus21-common. (Dunno why it didn't upgrade to 2.2.) And I believe this
shows a good hint at what happened:

-rw-r--r--  2 root root 3279 2008-03-15 14:06 monthly.5/var/lib/dpkg/info/cyrus21-common.list
-rw-r--r--  2 root root 3279 2008-03-15 14:06 monthly.4/var/lib/dpkg/info/cyrus21-common.list
-rw-r--r-- 14 root root 3547 2010-09-22 13:23 weekly.2/var/lib/dpkg/info/cyrus-common-2.2.list
-rw-r--r-- 14 root root 3547 2010-09-22 13:23 weekly.1/var/lib/dpkg/info/cyrus-common-2.2.list
-rw-r--r-- 14 root root 3547 2010-09-22 13:23 weekly.0/var/lib/dpkg/info/cyrus-common-2.2.list
-rw-r--r-- 14 root root 3547 2010-09-22 13:23 monthly.3/var/lib/dpkg/info/cyrus-common-2.2.list
-rw-r--r--  3 root root  388 2010-09-22 13:23 monthly.3/var/lib/dpkg/info/cyrus21-common.list
-rw-r--r-- 14 root root 3547 2010-09-22 13:23 monthly.2/var/lib/dpkg/info/cyrus-common-2.2.list
-rw-r--r--  3 root root  388 2010-09-22 13:23 monthly.2/var/lib/dpkg/info/cyrus21-common.list
-rw-r--r-- 14 root root 3547 2010-09-22 13:23 monthly.1/var/lib/dpkg/info/cyrus-common-2.2.list
-rw-r--r--  3 root root  388 2010-09-22 13:23 monthly.1/var/lib/dpkg/info/cyrus21-common.list
-rw-r--r-- 14 root root 3547 2010-09-22 13:23 monthly.0/var/lib/dpkg/info/cyrus-common-2.2.list
-rw-r--r-- 14 root root 3547 2010-09-22 13:23 daily.6/var/lib/dpkg/info/cyrus-common-2.2.list
-rw-r--r-- 14 root root 3547 2010-09-22 13:23 daily.5/var/lib/dpkg/info/cyrus-common-2.2.list
-rw-r--r-- 14 root root 3547 2010-09-22 13:23 daily.4/var/lib/dpkg/info/cyrus-common-2.2.list
-rw-r--r-- 14 root root 3547 2010-09-22 13:23 daily.3/var/lib/dpkg/info/cyrus-common-2.2.list
-rw-r--r-- 14 root root 3547 2010-09-22 13:23 daily.2/var/lib/dpkg/info/cyrus-common-2.2.list
-rw-r--r-- 14 root root 3547 2010-09-22 13:23 daily.1/var/lib/dpkg/info/cyrus-common-2.2.list
-rw-r--r-- 14 root root 3547 2010-09-22 13:23 daily.0/var/lib/dpkg/info/cyrus-common-2.2.list

cyrus21-common and cyrus-common-2.2 coexisted for a while until I
removed cyrus21-common (and the other 2.1 packages). That probably
removed the overrides.

This is what I did:
# upgrade packages that are essential for the Lenny upgrade
apt-get install apt aptitude perl perl-base dpkg amavisd-new libcompress-zlib-perl libarchive-zip-perl
# do the main portion of the upgrade
aptitude safe-upgrade
# do the rest
aptitude dist-upgrade

Nothing there upgraded the cyrus packages from 2.1 to 2.2, which is
probably as intended. When I later upgraded, I must have managed to
leave the 2.1 packages on the system. Though I wonder how, since the
cyrus-common-22 packages says:

Replaces: cyrus21-common, cyrus22-common

The Bash history for root shows that I installed the packages with

apt-get install cyrus-imapd-2.2 cyrus-pop3d-2.2 cyrus-sasl2-doc cyrus-doc-2.2 cyrus-admin-2.2

> The postinst script should create them if they don't exist already.  In
> fact, the cyrus-comon-2.2 postinst script, from package version
> 2.2.13-14+lenn3 has this:

As You can see from above, that postinst ran before the postrm from
cyrus21-common.

> We need more data to find out what could be wrong.

Something that should have prevented cyrus21-common and cyrus-common-2.2
from coexisting. Any idea hiow that might have happened?

> Does "dpkg --pending --configure" says it is trying to configure any cyrus
> packages?

Nothing as you will probably have guessed from the above.

Verrry interesting...
Lupe Christoph
-- 
Octogon Gesellschaft für Computer-Dienstleistungen mbH
Sitz: Schiffbauerweg 9 / 82319 Starnberg / Deutschland
Telefon: 08151/4449640 / Telefax: 08151/4449644 / HRB 112724 Amtsgericht München
Geschäftsführer: Lutz Christoph