Henrique de Moraes Holschuh <[EMAIL PROTECTED]> writes: > On Wed, 15 Nov 2006, Michael Welsh Duggan wrote: >> Since upgrading, I have experienced similar problems using cyrus21. In >> particular, all of my seen flags seem inaccessible. Part of mail.log: >> >> Nov 15 18:29:22 maru cyrus/master[29877]: about to exec >> /usr/lib/cyrus/bin/imapd >> Nov 15 18:29:22 maru cyrus/imap[29877]: executed >> Nov 15 18:29:22 maru cyrus/imapd[29877]: accepted connection >> Nov 15 18:29:23 maru cyrus/imapd[29877]: login: maru[127.0.0.1] md5i >> plaintext >> Nov 15 18:29:23 maru cyrus/imapd[29877]: DBERROR: skiplist recovery >> /var/lib/cyrus/user/m/md5i.seen: ADD at 8FD4 exists > > A skiplist database is corrupted. This is not supposed to have *anything* > to do with sasl, so if you really did get it because of sasl, we have a damn > big bad bug that corrupts the application's stack/data space/open files. > > And since skiplist has nothing to do with berkeley DB, it should not happen > because there are two versions of berkeley DB linked to cyrus imapd now, > either... Still, that's a possibility. > > Does downgrading fix the issue? You may have a corrupted skiplist database > for other reasons, after all...
Thank you for responding. It appears you had correct. I had made a procedural error when restoring the corrupted databases from backup. A subsequent proper restore works with the up-to-date sasl libraries installed. This corruption occured under the following circumstances: I was reading mail using an open imap connection. While reading mail, the sasl packages were updated. After closing and restarting the imap connection later, the skiplists were corrupted. I do not know if the conjunction of these events were coincidence or not. I think you should consider, at the very least, whether the cyrus daemon should be brought down during the installation of new sasl libraries. -- Michael Welsh Duggan ([EMAIL PROTECTED])
pgpNXieNT6qj5.pgp
Description: PGP signature
