OK, thanks. Ken Murchison wrote:
>I don't recall seeing this problem with the v2.0.15-HIERSEP-r2 release >and I'm not convinced that is is related to the altnamespace/unixhiersep >code. You could try grabbing the latest code from CVS which has updated >altnamespace/unixhiersep code and has a rearchitected deliver database. > >Ken > > >Jules Agee wrote: > >>I have been testing with v2.0.15-HIERSEP-r2 for the altnamespace >>functionality and have run into an intermittent problem with DB >>corruption. A single user's INBOX stops accepting new messages, and I >>start seeing this in the log: >> >>Oct 19 06:45:46 cronus lmtpd[21353]: duplicate_mark: closing >>/var/imap/deliverdb/deliver-t.db: DB_INCOMPLETE: Cache flush was unable >>to complete >>Oct 19 06:45:46 cronus lmtpd[21375]: lmtp connection preauth'd as postman >>Oct 19 06:45:46 cronus lmtpd[21378]: duplicate_mark: closing >>/var/imap/deliverdb/deliver-j.db: DB_INCOMPLETE: Cache flush was unable >>to complete >>Oct 19 06:45:46 cronus lmtpd[21407]: duplicate_mark: closing >>/var/imap/deliverdb/deliver-j.db: DB_INCOMPLETE: Cache flush was unable >>to complete >> >>Then to get those mailbox accepting messages again, I run recover -r >>user.username >>which works fine, but then when I run quota -f, this shows up in the log: >> >>Oct 19 10:52:34 cronus quota[3760]: DBERROR: unable to create cursor: >>DB_RUNRECOVERY: Fatal error, run database recovery >>Oct 19 10:52:34 cronus quota[3760]: DBERROR: error advancing: >>DB_RUNRECOVERY: Fatal error, run database recovery >>Oct 19 10:52:34 cronus quota[3760]: DBERROR: error closing: >>DB_RUNRECOVERY: Fatal error, run database recovery >>Oct 19 10:52:34 cronus quota[3760]: DBERROR: error closing mailboxes: >>cyrusdb error >>Oct 19 10:52:34 cronus quota[3760]: DBERROR: error exiting application: >>DB_RUNRECOVERY: Fatal error, run database recovery >>Oct 19 10:52:34 cronus quota[3760]: DBERROR: error exiting application: >>cyrusdb error >> >>I have run db_recover -h /var/imap/db >>and db_recover -h /var/imap/deliverdb, but the problem shows up again in >>a day or two on a different mailbox - am I fixing the right db files? >> >>I'm using RedHat 7.0 + some updates with version 3.1.17-5 of the db3 RPM >>installed. >> >>Any suggestions? >> >>-- >>Jules Agee >>System Administrator >>Pacific Coast Feather Co. >>[EMAIL PROTECTED] x284 >> >>Private communication between citizens is necessary to ensure the >>continued preservation of freedom. For more information, see: >>http://www.computerprivacy.org/archive/03171998-5.shtml >> >>My public encryption key is available here: >>http://keyserver.pgp.com/pks/lookup?op=get&exact=on&search=0x21662FE4 >> > -- Jules Agee System Administrator Pacific Coast Feather Co. [EMAIL PROTECTED] x284 Private communication between citizens is necessary to ensure the continued preservation of freedom. For more information, see: http://www.computerprivacy.org/archive/03171998-5.shtml My public encryption key is available here: http://keyserver.pgp.com/pks/lookup?op=get&exact=on&search=0x21662FE4
