Problems with BerkeleyDB3 - corrupt Databases?

Anton Roeckseisen Anton_Roeckseisen at genua.de
Wed Jan 28 05:47:32 EST 2004


On Thu, Jan 08, 2004 at 07:37:12PM +0100, Anton Roeckseisen wrote:
> Hi All,
> 
> I get following errors in my logs:
> --
> Jan  8 19:03:33 aphrodite master[13180]: [ID 392559 local6.debug] about to exec /opt/Mailsystem/cyrus/bin/ctl_cyrusdb
> Jan  8 19:03:33 aphrodite ctl_cyrusdb[13180]: [ID 702911 local6.notice] checkpointing cyrus databases
> Jan  8 19:03:33 aphrodite ctl_cyrusdb[13180]: [ID 866726 local6.warning] DBERROR db3: log_flush: LSN past current end-of-log
> Jan  8 19:03:33 aphrodite ctl_cyrusdb[13180]: [ID 866726 local6.warning] DBERROR db3: txn_checkpoint: failure in memp_sync Invalid argument
> Jan  8 19:03:33 aphrodite ctl_cyrusdb[13180]: [ID 865331 local6.error] DBERROR: couldn't checkpoint: Invalid argument
> Jan  8 19:03:33 aphrodite ctl_cyrusdb[13180]: [ID 109027 local6.error] DBERROR: sync /var/imap/db: cyrusdb error
> Jan  8 19:03:36 aphrodite ctl_cyrusdb[13180]: [ID 578205 local6.debug] archiving database file: /var/imap/mailboxes.db
[...]
> Another problem is that I had to disable "ctl_deliver" and
> "tls_prune" because they kept complaining about problems with
> their DBs until the log-filesystem was full..... :-( Above
> problem might have the same roots....
> db_verify usually found errors in deliver.db and tls_sessions.de,
> but does not with mailboxes.db.

I fixed those problems with turning off "async" option for
deliver and tls cache databases. Now using the same as in
mailboxes.db. I had to rebuild cyrus
to modify this options.

\Anton





More information about the Info-cyrus mailing list