[KLUG Members] Cyrus IMAP problems!

[Bruce Smith]

This just happened to me for the 2nd time since migrating to cyrus imapd.
The whole system quits accepting email (no lmtp) and imap/pop3 won't work.
This is a _small_ excerpt from /var/log/messages:

Jul 26 12:58:02 mail master[16556]: process 27747 exited, status 75
Jul 26 12:58:02 mail master[16556]: service imaps pid 27747 in READY state: terminated abnormally
Jul 26 12:58:02 mail master[16556]: process 27750 exited, status 75
Jul 26 12:58:02 mail master[16556]: service imap pid 27750 in READY state: terminated abnormally
Jul 26 12:58:02 mail pop3[27748]: DBERROR db4: PANIC: fatal region error detected; run recovery
Jul 26 12:58:02 mail pop3[27748]: DBERROR: critical database situation
Jul 26 12:58:02 mail pop3s[27751]: DBERROR db4: PANIC: fatal region error detected; run recovery
Jul 26 12:58:02 mail pop3s[27751]: DBERROR: critical database situation
Jul 26 12:58:02 mail master[27756]: about to exec /usr/lib/cyrus/bin/imapd
Jul 26 12:58:02 mail imap[27756]: DBERROR db4: PANIC: fatal region error detected; run recovery
Jul 26 12:58:02 mail imap[27756]: DBERROR: critical database situation
Jul 26 12:58:02 mail deliver[27760]: DBERROR db4: PANIC: fatal region error detected; run recovery
Jul 26 12:58:02 mail deliver[27760]: DBERROR: critical database situation

It seems to happen about a week apart right after a new log.00000x file
appears in /var/lib/imap/db/

To recover, I have to stop cyrus, remove all files: /var/lib/imap/db/*
then run:  

  su - cyrus -c "/usr/lib/cyrus/bin/ctl_cyrusdb -r"

and restart the cyrus service.  
If I don't remove the db files, the above command aborts also.

I'm running SuSE 9.1 and it's RPM's for Cyrus (everything up to date)
cyrus-imapd-2.2.3-79.   Any clues?  This is getting really annoying!

 - BS