On Sat, 05 Feb 2005, Karl Schmidt wrote: > Micah Anderson wrote: > >The original bug report said that you were running: > > > >Version: 0.93.1-1 > >ii libdb4.2 4.2.52-17 Berkeley v4.2 Database > >Libraries > > > >and your problem occurs with both: > >bogofilter_0.93.3.1-1_i386.deb > >bogofilter_0.93.5-1_i386.deb > > > >You say that bogofilter_0.93.1-1_i386.deb works and then go on to say: > > > >"At least bogofilter_0.93.1-1_i386.deb or the one before works without > >crashing the db file." > > > > The version number was wrong because I had already rolled it back to > 93.1-1 The bug refers to 93.5-1 (and 93.3.1-1)
Your report is very confusing because of this. Let me see if I understand: 1. You upgraded bogofilter to 0.93.5-1 from 0.93.0-1 2. you followed the NEWS.Debian instructions to convert your wordlist db log format to the new version using db4.2_recover and db4.2_archive (NOTE! 4.2, not 4.3, or db_recover, db_archive or db3_recover, db3_archive) 3. About 48 hours later you get the error "datastore_db.c:1056: DB_ENV->open, err: DB_RUNRECOVERY: Fatal error, run database recovery" somewhere in an exim logfile and bogofilter ceases to work properly. 4. You remove 0.93.5-1 5. You install 0.93.0-1 and recreate your DB files with a db4.2 environment 6. Things work again. 7. Same problem with 0.93.1-1 following same procedures > I had and still have installed: > ii libdb1-compat 2.1.3-7 The Berkeley database routines [glibc > 2.0/2. > ii libdb3 3.2.9-20 Berkeley v3 Database Libraries [runtime] > ii libdb3-dev 3.2.9-20 Berkeley v3 Database Libraries > [development] > ii libdb4.2 4.2.52-17 Berkeley v4.2 Database Libraries [runtime] > ii libdb4.3 4.3.27-1 Berkeley v4.3 Database Libraries [runtime] > > My understanding is that these do not conflict (if so this is a > dependency issue). This is fine, I've got all these installed and I don't have the problem you are having. > The problem exists after recreating all new db and log files via > bogofilter. (I archive all ham AND spam). It only appeared after about > 48 hours of operation (the wrong version fails right away). "It only appeared" means the error: "datastore_db.c:1056: DB_ENV->open, err: DB_RUNRECOVERY: Fatal error, run database recovery" appears somewhere in a logfile? "the wrong version fails right away" -- what is the wrong version? and how do you determine that it has failed right away? > I don't see how this problem can be related to a change in db files when > they were created after the upgrade. It shouldn't... Micah -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]