On Fri, 21 Jan 2005, Jukka Salmi wrote:
Hi,
I is probably a FAQ, but I couldn't find an answer to it...
On a NetBSD 2.0 system running Cyrus IMAPd 2.2.10 and Berkeley DB 4.2.52 (both installed from pkgsrc) I updated BDB to 4.3.27. After starting master the following was logged:
Jan 21 15:47:18 bart master[16978]: process started Jan 21 15:47:18 bart master[10723]: about to exec /usr/pkg/cyrus/bin/ctl_cyrusdb Jan 21 15:47:18 bart ctl_cyrusdb[10723]: DBERROR p*^F^H: db4 Jan 21 15:47:18 bart ctl_cyrusdb[10723]: DBERROR p*^F^H: db4 Jan 21 15:47:18 bart ctl_cyrusdb[10723]: recovering cyrus databases Jan 21 15:47:18 bart ctl_cyrusdb[10723]: skiplist: recovered /var/imap/mailboxes.db (22 records, 3596 bytes) in 0 seconds Jan 21 15:47:18 bart ctl_cyrusdb[10723]: skiplist: recovered /var/imap/annotations.db (13 records, 1392 bytes) in 0 seconds Jan 21 15:47:18 bart ctl_cyrusdb[10723]: DBERROR p*^F^H: db4 Jan 21 15:47:18 bart ctl_cyrusdb[10723]: DBERROR p*^F^H: db4 Jan 21 15:47:18 bart ctl_cyrusdb[10723]: DBERROR: critical database situation Jan 21 15:47:18 bart master[16978]: process 10723 exited, status 75 Jan 21 15:47:18 bart master[16978]: ready for work Jan 21 15:47:18 bart master[29388]: about to exec /usr/pkg/cyrus/bin/ctl_cyrusdb Jan 21 15:47:18 bart ctl_cyrusdb[29388]: DBERROR p*^F^H: db4 Jan 21 15:47:18 bart ctl_cyrusdb[29388]: DBERROR: critical database situation Jan 21 15:47:18 bart master[16978]: process 29388 exited, status 75
The only BDBs I use are duplicate_db and tlscache_db, so I could simply delete $configdirectory/{deliver.db,tls_sessions.db,db/*} and start Cyrus again.
yes.
But how is it possible to upgrade without deleting the DBs?
Reset the bdb environment with the old db_recover binary prior to upgrade. I do not think that the database format changed between the two BDB versions.
-- Igor --- Cyrus Home Page: http://asg.web.cmu.edu/cyrus Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
