Menu
▾
▴
#234 database corruption (bsddb)
when the pop3proxy.py is run for some longish time (2
hours) the database file (DBM) gets corrupted and each
mail then contains:
X-Spambayes-Exception:
bsddb._db.DBRunRecoveryError((-30989,
'DB_RUNRECOVERY: Fatal error,
run database recovery')) in __getitem__() at
/usr/lib/python2.3/bsddb/__init__.py line 86:
return
self.db[key]
Logged In: YES
user_id=31435
Which operating system, and which version of Sleepycat's
Berkeley code (spambayes shouldn't be able to corrupt a
Berkeley DB, so the problem is probably specific to the bsddb
version in use)?
Logged In: YES
user_id=698198
the operating system is RH 7.2 with those versions of the
Berkeley DB:
db1-1.85-7
db2-2.4.14-7
db3-3.2.9-4
sorry i didn't include this in right away with the bug report.
Logged In: YES
user_id=85414
We still don't know what causes this, but as a workaround
you can delete your spambayes.messageinfo.db file - that
file doesn't (yet) do anything important for pop3proxy, and
it's that file that's becoming corrupt. A new one will be
created, which may eventually become corrupt as well -
again, just delete it. You'll need to stop pop3proxy while
you delete it.
Logged In: YES
user_id=698198
i did some experimenting with various bsddb3 versions:
- with db-3.3.11 the python segfaults and core is dumped
- with db-3.2.9 the database is corrupted
- with db-4.1.25 everything works as it should (no db
corruption)
hth,
Logged In: YES
user_id=44345
Just a point of reference. I use bsddb with Berkeley DB 3.3.11
on Mac OS X via the hammie and hammiefilter programs
with no problem.
Logged In: YES
user_id=552329
From the last comment by the OP, this sounds like it is a bug
with bsddb that is fixed in db-4.1.25, so I'm closing this.
Reopen if that's not right. (What to do with the messageinfo
db still needs to be resolved, but that's a separate issue).