cyr_expire: deliver.db inconsistent pre-checkpoint bailing out

Patrick Boutilier boutilpj at ednet.ns.ca
Sat Dec 6 12:44:01 EST 2014


Been a while but we just used to delete deliver.db when it went bad and just let Cyrus recreate it.

On December 6, 2014 1:07:06 PM AST, Vincent Fox <vbfox at ucdavis.edu> wrote:
>Hi,
>
>We are running quite old Cyrus 2.3.8 (near retirement) and last couple
>of nights it started kicking up this error during nightly expire run.
>
>  cyr_expire[3409]: [ID 386572 local6.error] db 
>/var/cyrus/imap/deliver.db, inconsistent pre-checkpoint, bailing out
>
>Any guidance on best course of action?  We do have nightly snapshots of
>the
>entire filesystem, so I could roll back to deliver.db from 3 or 4 days
>ago.
>Or would that create consistency issues with other databases only
>making
>things worse.  Or could I stop Cyrus and only reconstruct deliver.db?
>
>The server has thousands of users and 500gig+ of files so I don't
>relish
>the idea of long downtime for full reconstruct.
>
>Thanks!
>
>----
>Cyrus Home Page: http://www.cyrusimap.org/
>List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
>To Unsubscribe:
>https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.andrew.cmu.edu/pipermail/info-cyrus/attachments/20141206/1c7e2f23/attachment.html 


More information about the Info-cyrus mailing list