Desperate

[Colin Bruce]

Dear All,

We have been running cyrus for roughly 8 hours in a production environment and it
has failed. It will not start at all. It just sits their doing nothing. The following
errors are in the log file although these are follow by hundreds of lines similar
to this.

It is the latest stable version of cyrus that we are trying to run.

Apr  6 13:02:37 imap2 ctl_cyrusdb[2264]: archiving log file: /usr/local/packages/cyrus/var/db/log.0000000001
Apr  6 13:02:37 imap2 ctl_cyrusdb[2264]: archiving database file: /usr/local/packages/cyrus/var/mailboxes.db
Apr  6 13:02:37 imap2 ctl_cyrusdb[2264]: archiving log file: /usr/local/packages/cyrus/var/db/log.0000000001
Apr  6 13:02:37 imap2 ctl_cyrusdb[2264]: done checkpointing cyrus databases
Apr  6 13:02:37 imap2 master[2256]: process 2264 exited, status 0
Apr  6 13:03:23 imap2 imap[642]: DBERROR db4: PANIC: fatal region error detected; run recovery
Apr  6 13:03:23 imap2 imap[642]: DBERROR: critical database situation
Apr  6 13:03:56 imap2 imap[2255]: unable to tell master 1: Broken pipe
Apr  6 13:03:56 imap2 imap[2255]: unable to tell master 2: Broken pipe


We have run recovery as instructed but that does nothing.

Does anyone know how to fix this? If not does anyone know how difficult it would
be to to convert back to UW imap. It seems to be much more stable than cyrus.

As a matter of interest how are we supposed to stop cyrus if the machine it is
running on is being shutdown. I can't find any mention of how to do that in the
documentation.

Best wishes.....
Colin


---
Home Page: http://asg.web.cmu.edu/cyrus
Wiki/FAQ: http://cyruswiki.andrew.cmu.edu
List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html