Martti Kuparinen --> tech-pkg (2004-12-29 10:25:53 +0200):
> ROOT inside:~> lintpkgsrc -i
> Scanning Makefiles: 5262 packages
> Version mismatch: 'db4' 4.2.52nb7 vs 4.3.21
> ROOT inside:~>
> 
> I then updated db4 and cyrus stopped working. Here's a fragment from
> /var/log/messages:
> 
> Dec 29 10:11:01 inside lmtpunix[25171]: DBERROR d^^H^H: db4
> Dec 29 10:11:01 inside lmtpunix[25171]: DBERROR: critical database situation
> Dec 29 10:11:01 inside master[15334]: service lmtpunix pid 25171 in 
> READY state: terminated abnormally
> Dec 29 10:11:01 inside master[15334]: exiting on SIGTERM/SIGINT
> 
> 
> I went back to 4.2.52nb7 and everything is okay.

After updating BDB from db4-4.2.52nb7 to db4-4.3.27nb1 I saw the same
problem here (with cyrus-imapd-2.2.10nb2). I solved it as follows:

- stop Cyrus master
- run db_checkpoint and db_recover (using the old 4.2.52 binaries & libs)
- remove /var/imap/db/__db.* and /var/imap/db/log.*
- install new db4
- start Cyrus

I'm using default DB types, i.e. I did not change any *_db option
in imapd.conf. This means the only BDBs here are duplicate_db and
tlscache_db.


HTH, Jukka

-- 
bashian roulette:
$ ((RANDOM%6)) || rm -rf ~