Downgrading Berkley Problem - no sig

Jeff Wilde jeff.wilde at parkregion.com
Fri Feb 28 17:15:08 EST 2003


Resend didn't need digital signature sorry about that.

I have been having problems with 4.1.25 and I am wanting to downgrade to
3.3.x.  I was wondering what am I all missing.  I recompiled and
everything went well with that.  I then tried restarting cyrus and got
lots and lots of errors in the logfile and cyrus didn't really start.  I
ran the ctl_cyrusdb -r option which I figured would help with the
database recovery process, but it looks like it still wants v4.  What
are the steps I need to take to implement this successfully?  Here are
sniplets of log:

Feb 28 12:45:44 web master[28991]: setrlimit: Unable to set file
descriptors limit to 2147483647: Operation not permitted
Feb 28 12:45:44 web master[28991]: retrying with 1024 (current max)
Feb 28 12:45:44 web master[28991]: process started
Feb 28 12:45:44 web ctl_cyrusdb[28993]: recovering cyrus databases
Feb 28 12:45:44 web ctl_cyrusdb[28993]: DBERROR db3: Ignoring log file:
/usr/local/mail/db/log.0000000201: unsupported log version 7
Feb 28 12:45:44 web ctl_cyrusdb[28993]: DBERROR db3: Invalid log file:
log.0000000201: Invalid argument
Feb 28 12:45:44 web ctl_cyrusdb[28993]: DBERROR db3: PANIC: Invalid
argument
Feb 28 12:45:44 web ctl_cyrusdb[28993]: DBERROR: critical database
situation
Feb 28 12:45:44 web master[28991]: process 28993 exited, status 75
Feb 28 12:45:44 web master[28991]: no service 'sieve' in /etc/services,
disabling sieve
Feb 28 12:45:44 web master[28991]: ready for work
Feb 28 12:45:45 web ctl_cyrusdb[28994]: checkpointing cyrus databases
Feb 28 12:45:45 web ctl_cyrusdb[28994]: DBERROR db3: region error
detected; run recovery.
Feb 28 12:45:45 web ctl_cyrusdb[28994]: DBERROR: dbenv->open
'/usr/local/mail/db' failed: DB_RUNRECOVERY: Fatal error, run database
recovery
Feb 28 12:45:45 web ctl_cyrusdb[28994]: DBERROR: init
/usr/local/mail/db: cyrusdb error
Feb 28 12:45:45 web ctl_cyrusdb[28994]: done checkpointing cyrus
databases
Feb 28 12:45:45 web imapd[28995]: DBERROR db3: region error detected;
run recovery.
Feb 28 12:45:45 web pop3d[28996]: DBERROR db3: region error detected;
run recovery.
Feb 28 12:45:45 web lmtpd[28997]: DBERROR db3: region error detected;
run recovery.
Feb 28 12:45:45 web imapd[28995]: DBERROR: dbenv->open
'/usr/local/mail/db' failed: DB_RUNRECOVERY: Fatal error, run database
recovery
Feb 28 12:45:45 web pop3d[28996]: DBERROR: dbenv->open
'/usr/local/mail/db' failed: DB_RUNRECOVERY: Fatal error, run database
recovery
Feb 28 12:45:45 web lmtpd[28997]: DBERROR: dbenv->open
'/usr/local/mail/db' failed: DB_RUNRECOVERY: Fatal error, run database
recovery
Feb 28 12:45:45 web imapd[28995]: Fatal error: can't initialize mboxlist
environment
Feb 28 12:45:45 web lmtpd[28997]: DBERROR: init /usr/local/mail/db:
cyrusdb error
Feb 28 12:45:45 web lmtpd[28997]: lmtpd: unable to init duplicate
delivery database
Feb 28 12:45:45 web lmtpd[28997]: DBERROR db3: environment not yet
opened
Feb 28 12:45:45 web lmtpd[28997]: DBERROR: opening
/usr/local/mail/mailboxes.db: Invalid argument
Feb 28 12:45:45 web lmtpd[28997]: DBERROR: opening
/usr/local/mail/mailboxes.db: cyrusdb error
Feb 28 12:45:45 web lmtpd[28997]: FATAL: can't read mailboxes file
Feb 28 12:45:45 web imapd[28998]: DBERROR db3: region error detected;
run recovery.
Feb 28 12:45:45 web pop3d[28999]: DBERROR db3: region error detected;
run recovery.
Feb 28 12:45:45 web lmtpd[29000]: DBERROR db3: region error detected;
run recovery.


Tia






More information about the Info-cyrus mailing list