imap db not readable after upgradr to 9.10

Bug #461364 reported by Joern Muehlencord
26
This bug affects 5 people
Affects Status Importance Assigned to Milestone
cyrus-imapd-2.2 (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: cyrus-imapd-2.2

After upgrade von 9.04 to 9.10 mail.info and mail.err showed the following error
Oct 26 19:18:46 moonworld cyrus/imap[15183]: DBERROR: critical database situation
Oct 26 19:18:46 moonworld cyrus/notify[15184]: DBERROR: critical database situation
Oct 26 19:18:46 moonworld cyrus/notify[15186]: DBERROR: critical database situation
Oct 26 19:18:46 moonworld cyrus/notify[15187]: DBERROR: critical database situation
Oct 26 19:18:46 moonworld cyrus/imap[15185]: DBERROR: critical database situation
(repeating several times a second)

Occured errors
The email clients configured could not connect.
/etc/init.d/cyrus22 stop did not work - error occurred while stopping

Workaround solution:
After stopping (killing) cyrmaster I did the following
su - cyrus
cd /var/lib/cyrus
rm db/*
rm db.backup1/*
rm db.backup2/*
rm deliver.db
rm tls_sessions.db
exit

And started cyrus again. Email server / all clients seem to work ok again.

ProblemType: Bug
Architecture: i386
Date: Mon Oct 26 19:56:02 2009
DistroRelease: Ubuntu 9.10
NonfreeKernelModules: nvidia
Package: cyrus-common-2.2 2.2.13-16ubuntu1
ProcEnviron:
 LANGUAGE=
 PATH=(custom, user)
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
SourcePackage: cyrus-imapd-2.2
Uname: Linux 2.6.31-14-generic i686

Revision history for this message
Joern Muehlencord (joern-muehlencord) wrote :
Revision history for this message
Marc Schumann (elmanso) wrote :

This problem also exits at my update from jaunty to karmic.

Solution works too.

Revision history for this message
Mark Ellis (mark-mpellis) wrote :

It would seem that jaunty cyrus (version 2.2.13-14ubuntu3) is linked against libdb4.6, whereas the karmic version (2.2.13-16ubuntu1) is linked against libdb4.2, not good.

I can confirm that downgrading to the previous cyrus versions works perfectly.

Revision history for this message
Charles (slivkoff) wrote :

Can someone post some steps to rebuild cyrus from the source with a patch to link against libdb4.6?

Revision history for this message
Mark Ellis (mark-mpellis) wrote :

Apply the attached patch, make sure you have libdb4.6-dev installed, and rebuild. I haven't tried to make this patch perfect, it's just enough to allow you to use db4.6

Revision history for this message
Ondřej Surý (ondrej) wrote :

This will go away with newer cyrus-imapd-2.2, once it gets pulled from Debian. Berkeley DB upgrades are now automatic.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.