Sieve failure on deliverdb corruption...

From: Rob Mueller (no email)
Date: Wed Jun 18 2003 - 21:07:05 EDT


Over night our delivery DB (DB3 - db3-3.3.11-6) croaked. This is the first
time I've seen something like this. I've included the first error and some
subsequent information from the log below.

Now I presume this is a DB3 problem and not a cyrus issue, but what really
annoyed me is that all subsequent sieve filtering failed. This annoyed quite
a few people who have forwarding to their SMS provider setup for important
messages.

Does sieve REALLY require access to the duplicate delivery DB to be
successful? Is there any chance it can be turned into a non-fatal error?

Rob

-----

Jun 18 14:36:36 www lmtpd[23791]: DBERROR db3: PANIC: Invalid argument
Jun 18 14:36:36 www lmtpd[23791]: DBERROR: critical database situation
Jun 18 14:36:36 www lmtpd[23718]: DBERROR: error fetching <xyz1>:
DB_RUNRECOVERY: Fatal error, run database recovery
Jun 18 14:36:36 www lmtpd[23718]: duplicate_check: error looking up
<xyz1>/user.abc1: cyrusdb error
Jun 18 14:36:37 www lmtpd[23718]: DBERROR: mystore: error beginning txn:
DB_RUNRECOVERY: Fatal error, run database recovery
Jun 18 14:36:37 www lmtpd[827]: DBERROR: error closing: DB_RUNRECOVERY:
Fatal error, run database recovery
Jun 18 14:36:37 www lmtpd[827]: DBERROR: error closing deliverdb: cyrusdb
error
Jun 18 14:36:37 www lmtpd[827]: DBERROR: error exiting application:
DB_RUNRECOVERY: Fatal error, run database recovery
Jun 18 14:36:37 www lmtpd[16460]: DBERROR: error fetching <xyz2>:
DB_RUNRECOVERY: Fatal error, run database recovery
Jun 18 14:36:37 www lmtpd[16460]: duplicate_check: error looking up
<xyz2>/user.abc2: cyrusdb error
Jun 18 14:36:37 www lmtpd[5568]: DBERROR: mystore: error beginning txn:
DB_RUNRECOVERY: Fatal error, run database recovery
Jun 18 14:36:37 www lmtpd[5568]: DBERROR: mystore: error beginning txn:
DB_RUNRECOVERY: Fatal error, run database recovery
Jun 18 14:36:37 www lmtpd[23645]: DBERROR: mystore: error beginning txn:
DB_RUNRECOVERY: Fatal error, run database recovery
Jun 18 14:36:37 www lmtpd[23645]: DBERROR: mystore: error beginning txn:
DB_RUNRECOVERY: Fatal error, run database recovery
Jun 18 14:36:37 www lmtpd[23928]: DBERROR: mystore: error beginning txn:
DB_RUNRECOVERY: Fatal error, run database recovery
Jun 18 14:36:37 www lmtpd[16460]: DBERROR: mystore: error beginning txn:
DB_RUNRECOVERY: Fatal error, run database recovery
Jun 18 14:36:37 www lmtpd[3496]: DBERROR: error closing: DB_RUNRECOVERY:
Fatal error, run database recovery
Jun 18 14:36:37 www lmtpd[3496]: DBERROR: error closing deliverdb: cyrusdb
error
Jun 18 14:36:37 www lmtpd[3496]: DBERROR: error exiting application:
DB_RUNRECOVERY: Fatal error, run database recovery

...

Jun 18 14:37:46 www lmtpd[32203]: DBERROR db3: region error detected; run
recovery.
Jun 18 14:37:46 www lmtpd[32203]: DBERROR: dbenv->open '/var/imap/db'
failed: DB_RUNRECOVERY: Fatal error, run database recovery
Jun 18 14:37:46 www lmtpd[32203]: DBERROR: init /var/imap/db: cyrusdb error
Jun 18 14:37:46 www lmtpd[32203]: lmtpd: unable to init duplicate delivery
database
Jun 18 14:37:46 www lmtpd[24483]: DBERROR: mystore: error beginning txn:
DB_RUNRECOVERY: Fatal error, run database recovery








Hosted Email Solutions

Invaluement Anti-Spam DNSBLs



Powered By FreeBSD   Powered By FreeBSD