Exactly. Now that you mention it, its happening everytime I stop the cyrus server. After deleting the files under /var/imap it will work again.
>I discovered that I could shutdown the cyrus-imapd service, run > > ctl_cyrusdb, run cvt_cyrusdb_all and then restart cyrus-imapd service to > > solve the problem. But it's a pain. This doesn't happen every time we > > restart the system. What exactly are the commands you run for this to get it to work this way ? I tried ctl_cyrusdb -r and am so lost on the cvt_cyrusdb, i was afraid to get too adventrous with it. ----- Original Message ----- From: "Tracy Bost" <[EMAIL PROTECTED]> To: "Tracy Bost" <[EMAIL PROTECTED]> Sent: Tuesday, March 16, 2004 8:47 PM Subject: Fw: cyrus stopped working -- corrupted files ? > > ----- Original Message ----- > From: "Fred W. Bacon" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Sent: Tuesday, March 16, 2004 6:42 PM > Subject: Re: cyrus stopped working -- corrupted files ? > > > > On Tue, 2004-03-16 at 13:09, Tracy Bost wrote: > > > > > My question is what exactly would cause this problem or why would the > > > files under db become corrupt ? > > > We naturally want to try and prevent this from happening in the > > > future. > > > > > > Thanks ! > > > > > > Mar 16 08:26:06 AFMAIL1 ctl_cyrusdb[6976]: DBERROR db4: PANIC: > > > DB_RUNRECOVERY: Fatal error, run database recovery > > > Mar 16 09:04:30 AFMAIL1 ctl_cyrusdb[3660]: DBERROR: dbenv->open > > > '/var/imap/db' failed: DB_RUNRECOVERY: Fatal error, run database > > > recovery > > > Mar 16 09:04:30 AFMAIL1 ctl_cyrusdb[3660]: DBERROR: init /var/imap/db: > > > cyrusdb error > > > Mar 16 09:04:30 AFMAIL1 ctl_deliver[3659]: DBERROR db4: fatal region > > > error detected; run recovery > > > > I've been seeing this lately myself. In our case, it appears to happen > > anytime we shut the system down, such as rebooting after installing a > > new kernel package. We're running cyrus 2.1.16 on Fedora Core 1. In my > > case, I discovered that I could shutdown the cyrus-imapd service, run > > ctl_cyrusdb, run cvt_cyrusdb_all and then restart cyrus-imapd service to > > solve the problem. But it's a pain. This doesn't happen every time we > > restart the system. > > > > I should add that this is on an ext3 file system...which may or may not > > be important. > > > > -- > > Fred W. Bacon <[EMAIL PROTECTED]> > > Aerodyne Research, Inc. > > > > --- > > 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 > > > > --- 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