Migration

Andrew Morgan morgan at orst.edu
Mon Mar 13 10:56:54 EST 2006


On Mon, 13 Mar 2006, Jeremy Leonard wrote:

> I'm having trouble migrating.
> I'm trying to migrate from:
>
> Suse 9.0/Cyrus 2.1.15/bdb 4.1.25
>
> to:
>
> Suse 10.0/Cyrus 2.2.12/dbd 4.3.27
>
> On the new server I have everything working.
> I tried to move the existing data from the old server by:
>
> On the new server I stopped the cyrus service.
> removed /var/lib/imap and /var/spool/imap
> On the old server I tar.gz'd /var/spool/imap and /var/lib/imap
> copied them to the new server and untar.gz'd them
> Into their appropriate directories.
> Restarted the service and I get and try to access the message store vi imap I 
> get:
>
> Mar 13 07:00:46 elite master[7213]: about to exec /usr/lib/cyrus/bin/imapd
> Mar 13 07:00:46 elite imap[7213]: DBERROR ä: db4
> Mar 13 07:00:46 elite imap[7213]: DBERROR: critical database situation
> Mar 13 07:00:46 elite master[3918]: process 7213 exited, status 75
> Mar 13 07:00:46 elite master[3918]: service imap pid 7213 in READY state: 
> terminated abnormally
>
> Mar 13 07:02:00 elite ctl_cyrusdb[14286]: DBERROR ÐÖ: db4
> Mar 13 07:02:00 elite ctl_cyrusdb[14286]: recovering cyrus databases
> Mar 13 07:02:00 elite ctl_cyrusdb[14286]: skiplist: recovered 
> /var/lib/imap/mailboxes.db (98 records, 9752 bytes) in 0 seconds
> Mar 13 07:02:00 elite ctl_cyrusdb[14286]: skiplist: recovered 
> /var/lib/imap/annotations.db (0 records, 144 bytes) in 0 seconds
> Mar 13 07:02:00 elite ctl_cyrusdb[14286]: DBERROR ÐÖ: db4
> Mar 13 07:02:00 elite ctl_cyrusdb[14286]: DBERROR ÐÖ: db4
> Mar 13 07:02:00 elite ctl_cyrusdb[14286]: DBERROR: critical database 
> situation
> Mar 13 07:02:00 elite master[14283]: process 14286 exited, status 75
> Mar 13 07:02:00 elite master[14287]: about to exec /usr/lib/cyrus/bin/idled
> Mar 13 07:02:00 elite idled[14287]: DBERROR ðØ: db4
> Mar 13 07:02:00 elite idled[14287]: DBERROR: critical database situation
> Mar 13 07:02:00 elite master[14283]: process 14287 exited, status 75

You don't say which backends you are using berkeley db with, but you'll 
probably have to dump them to plaintext and import them on the new box. 
Or, if it is backends that don't matter (tls_sessions, duplicate), just 
delete them and have Cyrus create them fresh.

 	Andy


More information about the Info-cyrus mailing list