Bugs item #807217, was opened at 2003-09-17 03:59 Message generated for change (Comment added) made by anadelonbrin You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=498103&aid=807217&group_id=61702
Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None >Status: Closed >Resolution: Out of Date Priority: 9 Submitted By: Rick Adams (rick_adams) Assigned to: Nobody/Anonymous (nobody) Summary: fatal region error detected; run recovery Initial Comment: I am getting errors like: bsddb._db.DBRunRecoveryError: (- 30982, 'DB_RUNRECOVERY: Fatal error, run database recovery -- fatal region error detected; run recovery') in the log file. There does not seem to be a recovery program to run. SpamBayes is still mostly working even though gnerating this error a complete logfile is attached ---------------------------------------------------------------------- >Comment By: Tony Meyer (anadelonbrin) Date: 2005-12-05 21:45 Message: Logged In: YES user_id=552329 We haven't fixed the underlying problem (that we know of), but since the default is now ZODB, I figure we can close this. ---------------------------------------------------------------------- Comment By: Kenny Pitt (kpitt) Date: 2004-08-17 02:14 Message: Logged In: YES user_id=859086 Noting dupe in 1009077 ---------------------------------------------------------------------- Comment By: Gisli Ottarsson (gisli) Date: 2004-06-12 04:54 Message: Logged In: YES user_id=332630 This problem has been spotted on an up-to-date Debian Unstable system. The system has fetchmail sucking mail through a pop3proxy. Version: spambayes-1.0rc1 I am halting spambayes, removing spambayes.messageinfo.db and restarting. Should I have removed this file when I updated to 1.0rc1 recently? Gisli ---------------------------------------------------------------------- Comment By: Mark Hammond (mhammond) Date: 2003-10-27 12:30 Message: Logged In: YES user_id=14198 Noting another Outlook user saw this in [ 828669 ] pythoncom error ---------------------------------------------------------------------- Comment By: Mark Hammond (mhammond) Date: 2003-09-23 19:21 Message: Logged In: YES user_id=14198 Adjusting category, as there are 2 reports in this bug - Outlook and the proxy ---------------------------------------------------------------------- Comment By: Richie Hindle (richiehindle) Date: 2003-09-23 18:59 Message: Logged In: YES user_id=85414 Re-opening. This is *not* fixed - the underlying problem is still there, and is very nasty. ---------------------------------------------------------------------- Comment By: Wolfgang Strobl (strobl) Date: 2003-09-23 03:19 Message: Logged In: YES user_id=311771 Removing spambayes.messageinfo.db solved the problem for me. Thanks. ---------------------------------------------------------------------- Comment By: Tony Meyer (anadelonbrin) Date: 2003-09-22 21:19 Message: Logged In: YES user_id=552329 Presumably, if your (bayes) database is a pickle, then this means that the problem is in the messageinfo database. You should be able to just delete that file without any problems, as long as you aren't planning to correct training of any messages still in the caches. ---------------------------------------------------------------------- Comment By: Wolfgang Strobl (strobl) Date: 2003-09-22 20:07 Message: Logged In: YES user_id=311771 I' started getting these errors, too, after upgrading from a2 (or 3) to a5 and changing from a pickled db to a dbhash (i.e. bsdi) one. Replacing all the code by a fresh CVS download from Friday didn't help. Exporting the database and reimporting it to a pickle unfortunately didn't fix the problem, either. I'm still getting these tracebacks, see below. I don't understand the "c:\python23\lib\bsddb\__init__.py" part in the traceback - my hammie.db is a pickled db, and I'm calling sb_server with the -D flag I haven't seen a pattern in which messages trigger this behaviour and which do not. It seems that when after say five or ten successfully processed messages, a message throws such an exception, any other message throws that exception, too. One has to kill and restart the proxy in order to make it work again, for another five or ten messages. ------- X-Spambayes-Exception: Traceback (most recent call last): . File "sb_server.py", line 439, in onRetr . msg.setId(state.getNewMessageName()) . File "C:\archiv\cvshome\spambayes\spambayes\message.py", line 193, in setId . msginfoDB._getState(self) . File "C:\archiv\cvshome\spambayes\spambayes\message.py", line 131, in _getState . (msg.c, msg.t) = self.db[msg.getId()] . File "c:\python23\lib\shelve.py", line 118, in __getitem__ . f = StringIO(self.dict[key]) . File "c:\python23\lib\bsddb\__init__.py", line 86, in __getitem__ . return self.db[key] .DBRunRecoveryError: (-30982, 'DB_RUNRECOVERY: Fatal error, run database recovery -- fatal region error detected; run recovery') ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=498103&aid=807217&group_id=61702 _______________________________________________ Spambayes-bugs mailing list [email protected] http://mail.python.org/mailman/listinfo/spambayes-bugs
