Simon Matter wrote:
I finally got a window of scheduled downtime to test this, and I'm having problems. Here's what I did: # /etc/init.d/cyrus-imapd stop # db_checkpoint -v -1 -h /var/lib/imap/db # db_recover -v -h /var/lib/imap/db # rm db/* # /usr/lib/cyrus-imapd/cvt_cyrusdb /var/lib/imap/deliver.db berkeley /var/lib/imap/deliver.db.skip skiplist # /usr/lib/cyrus-imapd/cvt_cyrusdb /var/lib/imap/tls_sessions.db berkeley /var/lib/imap/tls_sessions.db.skip skiplist # mv deliver.db.skip deliver.db ; mv tls_sessions.db.skip tls_sessions.db # chown cyrus:mail tls_sessions.db deliver.db # /etc/init.d/cyrus-imapd start At this point, the log explodes with messages along the lines of: Dec 11 06:11:53 ajax imaps[1394]: DBERROR: critical database situation Dec 11 06:11:53 ajax master[32203]: service imaps pid 1394 in READY state: terminated abnormally Dec 11 06:11:53 ajax master[32203]: service lmtpunix pid 1397 in READY state: terminated abnormally Dec 11 06:11:53 ajax imap[1395]: DBERROR A : db4 Dec 11 06:11:53 ajax imap[1395]: DBERROR: critical database situation Dec 11 06:11:53 ajax master[32203]: service imap pid 1395 in READY state: terminated abnormally Dec 11 06:11:53 ajax imap[1399]: DBERROR A : db4 Dec 11 06:11:53 ajax imap[1399]: DBERROR: critical database situation Dec 11 06:11:53 ajax imaps[1400]: DBERROR A : db4 Dec 11 06:11:53 ajax imaps[1400]: DBERROR: critical database situation Any ideas on why this is going on? I did notice that /var/lib/imap/rpm/db.cfg.cache has entries along the lines of: CONFIG_DB_DUPLICATE=berkeley CONFIG_DB_MBOX=skiplist CONFIG_DB_SEEN=skiplist CONFIG_DB_SUBS=flat CONFIG_DB_TLS=berkeley CONFIG_DB_ANNOTATION=skiplist CONFIG_DB_SIEVE=2.2.3 Is there someplace I need to tell imapd that deliver and tls_sessions are now skiplist? I don't see anything in /etc/imapd.conf and /etc/cyrus.conf.Something is really broken here... First shutdown using 'service cyrus-imapd stop', then put this in /etc/imapd.conf: duplicate_db: skiplist tlscache_db: skiplist Now try to start it up using 'service cyrus-imapd start'. Unfortunately I think the cyrus-imapd package shipped with FC4 has some bugs in the init scripts. I recommend you use my rpms, which are newer and have less bugs. RedHat ships old versions of my rpms which don't include the latest bug fixes. Find the source rpm here: http://www.invoca.ch/pub/packages/cyrus-imapd/
I tried what you suggested regarding just the /etc/imapd.conf changes, but without using your RPMs. There was no change: DBERROR messages everywhere until the imapd service was stopped, etc. I will try using your RPMs during the next period of scheduled maintenance, later this week. Thanks again.
---- Cyrus Home Page: http://cyrusimap.web.cmu.edu/ Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
