Restoring Mailboxes

Dr. Harry Knitter harry at knitter-edv-beratung.de
Wed Apr 19 07:50:42 EDT 2006


Hello,

we have a problem to restore Cyrus mailboxes from an installation of SuSE 9.2 
which we want to transfer do a SuSE 10.0 installation.
We have backuped the directories /var/lib/imap and /var/spool/imap and copied 
them to the new installation.
after restarting Cyrus syslog was flooded with messages 

<snip>

Apr 19 01:00:15 tux saslauthd[15007]: detach_tty      : master pid is: 15007
Apr 19 01:00:15 tux saslauthd[15007]: ipc_init        : listening on 
socket: /var/run/sasl2//mux
Apr 19 01:00:22 tux master[15022]: setrlimit: Unable to set file descriptors 
limit to -1: Operation not permitted
Apr 19 01:00:22 tux master[15022]: retrying with 1024 (current max)
Apr 19 01:00:22 tux master[15022]: process started
Apr 19 01:00:22 tux master[15023]: about to 
exec /usr/lib/cyrus/bin/ctl_cyrusdb
Apr 19 01:00:22 tux ctl_cyrusdb[15023]: DBERROR � : db4
Apr 19 01:00:22 tux ctl_cyrusdb[15023]: DBERROR � : db4
Apr 19 01:00:22 tux ctl_cyrusdb[15023]: recovering cyrus databases
Apr 19 01:00:22 tux ctl_cyrusdb[15023]: skiplist: 
recovered /var/lib/imap/mailboxes.db (112 records, 13252 bytes) in 0 seconds
Apr 19 01:00:22 tux ctl_cyrusdb[15023]: skiplist: 
recovered /var/lib/imap/annotations.db (0 records, 144 bytes) in 0 seconds
Apr 19 01:00:22 tux ctl_cyrusdb[15023]: DBERROR � : db4
Apr 19 01:00:22 tux ctl_cyrusdb[15023]: DBERROR � : db4
Apr 19 01:00:22 tux ctl_cyrusdb[15023]: DBERROR: critical database situation
Apr 19 01:00:22 tux master[15022]: process 15023 exited, status 75
Apr 19 01:00:22 tux master[15024]: about to exec /usr/lib/cyrus/bin/idled
Apr 19 01:00:22 tux idled[15024]: DBERROR � : db4
Apr 19 01:00:22 tux idled[15024]: DBERROR: critical database situation
Apr 19 01:00:22 tux master[15022]: process 15024 exited, status 75
Apr 19 01:00:22 tux master[15022]: SLPRegister [service:imap://tux.:143]
Apr 19 01:00:22 tux master[15022]: Error registering service with slp -20
Apr 19 01:00:22 tux master[15022]: SLPRegister [service:pop3://tux.:110]
Apr 19 01:00:22 tux master[15022]: Error registering service with slp -20
Apr 19 01:00:22 tux master[15022]: SLPRegister [service:sieve://tux.:2000]
Apr 19 01:00:22 tux master[15022]: Error registering service with slp -20
Apr 19 01:00:22 tux master[15022]: ready for work
Apr 19 01:00:22 tux master[15025]: about to 
exec /usr/lib/cyrus/bin/ctl_cyrusdb
Apr 19 01:00:22 tux ctl_cyrusdb[15025]: DBERROR � : db4
Apr 19 01:00:22 tux ctl_cyrusdb[15025]: DBERROR: critical database situation
Apr 19 01:00:22 tux master[15026]: about to exec /usr/lib/cyrus/bin/lmtpd
Apr 19 01:00:22 tux master[15022]: process 15025 exited, status 75
Apr 19 01:00:22 tux lmtpunix[15026]: DBERROR � : db4
Apr 19 01:00:22 tux lmtpunix[15026]: DBERROR: critical database situation
Apr 19 01:00:22 tux master[15022]: process 15026 exited, status 75
Apr 19 01:00:22 tux master[15022]: service lmtpunix pid 15026 in READY state: 
terminated abnormally
Apr 19 01:00:22 tux master[15027]: about to exec /usr/lib/cyrus/bin/lmtpd
Apr 19 01:00:22 tux lmtpunix[15027]: DBERROR � : db4
Apr 19 01:00:22 tux lmtpunix[15027]: DBERROR: critical database situation
Apr 19 01:00:24 tux master[15022]: process 15027 exited, status 75
Apr 19 01:00:24 tux master[15022]: service lmtpunix pid 15027 in READY state: 
terminated abnormally
Apr 19 01:00:24 tux master[15028]: about to exec /usr/lib/cyrus/bin/lmtpd
Apr 19 01:00:24 tux lmtpunix[15028]: DBERROR � : db4
Apr 19 01:00:24 tux lmtpunix[15028]: DBERROR: critical database situation
Apr 19 01:00:34 tux master[15022]: process 15028 exited, status 75
Apr 19 01:00:34 tux master[15022]: service lmtpunix pid 15028 in READY state: 
terminated abnormally
Apr 19 01:00:34 tux master[15029]: about to exec /usr/lib/cyrus/bin/lmtpd
Apr 19 01:00:34 tux lmtpunix[15029]: DBERROR � : db4
Apr 19 01:00:34 tux lmtpunix[15029]: DBERROR: critical database situation
Apr 19 01:00:44 tux master[15022]: process 15029 exited, status 75
Apr 19 01:00:44 tux master[15022]: service lmtpunix pid 15029 in READY state: 
terminated abnormally
Apr 19 01:00:44 tux master[15031]: about to exec /usr/lib/cyrus/bin/lmtpd
Apr 19 01:00:44 tux lmtpunix[15031]: DBERROR � : db4
Apr 19 01:00:44 tux lmtpunix[15031]: DBERROR: critical database situation
Apr 19 01:00:44 tux master[15022]: process 15031 exited, status 75
Apr 19 01:00:44 tux master[15022]: service lmtpunix pid 15031 in READY state: 
terminated abnormally
Apr 19 01:00:44 tux master[15032]: about to exec /usr/lib/cyrus/bin/lmtpd
Apr 19 01:00:44 tux lmtpunix[15032]: DBERROR � : db4
Apr 19 01:00:44 tux lmtpunix[15032]: DBERROR: critical database situation
Apr 19 01:00:54 tux master[15022]: process 15032 exited, status 75
Apr 19 01:00:54 tux master[15022]: service lmtpunix pid 15032 in READY state: 
terminated abnormally
Apr 19 01:00:54 tux master[15033]: about to exec /usr/lib/cyrus/bin/lmtpd
Apr 19 01:00:54 tux lmtpunix[15033]: DBERROR � : db4
Apr 19 01:00:54 tux lmtpunix[15033]: DBERROR: critical database situation
Apr 19 01:01:04 tux master[15022]: process 15033 exited, status 75
Apr 19 01:01:04 tux master[15022]: service lmtpunix pid 15033 in READY state: 
terminated abnormally
Apr 19 01:01:04 tux master[15034]: about to exec /usr/lib/cyrus/bin/lmtpd
Apr 19 01:01:04 tux lmtpunix[15034]: DBERROR � : db4
Apr 19 01:01:04 tux lmtpunix[15034]: DBERROR: critical database situation
Apr 19 01:01:14 tux master[15022]: process 15034 exited, status 75
Apr 19 01:01:14 tux master[15022]: service lmtpunix pid 15034 in READY state: 
terminated abnormally
Apr 19 01:01:14 tux master[15035]: about to exec /usr/lib/cyrus/bin/lmtpd
Apr 19 01:01:14 tux lmtpunix[15035]: DBERROR � : db4
Apr 19 01:01:14 tux lmtpunix[15035]: DBERROR: critical database situation
Apr 19 01:01:24 tux master[15022]: process 15035 exited, status 75
Apr 19 01:01:24 tux master[15022]: service lmtpunix pid 15035 in READY state: 
terminated abnormally
Apr 19 01:01:24 tux master[15036]: about to exec /usr/lib/cyrus/bin/lmtpd
Apr 19 01:01:24 tux lmtpunix[15036]: DBERROR � : db4
Apr 19 01:01:24 tux lmtpunix[15036]: DBERROR: critical database situation
Apr 19 01:01:28 tux master[15022]: SLPderegister [service:imap://tux.:143]
Apr 19 01:01:28 tux master[15022]: SLPderegister [service:pop3://tux.:110]
Apr 19 01:01:28 tux master[15022]: SLPderegister [service:sieve://tux.:2000]
Apr 19 01:01:28 tux master[15022]: exiting on SIGTERM/SIGINT
</snip>


is there any possibility to retrieve the data from the old mailboxes and 
restore them to the new ones?

The versions of cysrus are 2.2.12 for the new one

and

2.2.8 for the old one

Thanks in advance


Harry



More information about the Info-cyrus mailing list