bug: Lock table is out of available locks

JUANVAQUEROPONC JUANVAQUEROPONC at terra.es
Mon Nov 29 01:22:30 CET 2004


David Relson wrote:
> On Sun, 28 Nov 2004 23:05:55 GMT JUANVAQUEROPONC wrote:
> > I did:
> > bogofilter -s < spam.mbox
> > for i in ~/Mail/*; do bogofilter -n < "$i"; done
> > 
> > I'm getting with some of the last ham mboxes:
> > Lock table is out of available locks
> > bogofilter: (db) db_set_dbvalue( 'shoul'd' ), err: 12, Cannot allocate
> > memory bogofilter: db_close called with transaction still open,
> > program fault! Lock table is out of available object entries
> > 
> > I'm using Debian unstable bogofilter_0.93.1-1 on x86
> 
> This is a normal occurrence with a large database.  There's information
> on it in the README.db file and in new versions of the FAQ,
> http://www.bogofilter.org/faq.php.  You need to configure your
> Berkeley DB environment, specifically create a DB_CONFIG file with a
> larger lock count and then run 'bogoutil -f /path/to/your/wordlist.db'

Why isn't this lock count incremented automaticaly?
It's not a good idea to have the user read many documents before
starting to use a program and having error messages that can be
programatically resolved is not a good idea either.
Is anyone working on a proper fix for this problem?

> Instead of the for loop, you can probably use bogofilter's "-B" option
> for what you want.

Thanks for the hint.





More information about the Bogofilter mailing list