You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@spamassassin.apache.org by bu...@bugzilla.spamassassin.org on 2007/05/25 15:23:26 UTC

[Bug 5482] New: cannot open bayes databases

http://issues.apache.org/SpamAssassin/show_bug.cgi?id=5482

           Summary: cannot open bayes databases
           Product: Spamassassin
           Version: 3.2.0
          Platform: PC
        OS/Version: FreeBSD
            Status: NEW
          Severity: critical
          Priority: P5
         Component: spamc/spamd
        AssignedTo: dev@spamassassin.apache.org
        ReportedBy: mfahey@enter.net


spamassassin server - 3gb ram, intel quad core 2.4 cpu,freebsd 6.2 

Every day the bayesian database gets corrupted. We see the following in the log
file. We only use sqlite for scores. 

bayes: cannot open bayes databases /usr/local/share/spamassassin/bayes_* R/W:
lock failed: Interrupted system call

When we see the following in the logfile memory is at 1gig +. However after
restarting spamassassin there are memory usage goes right back to 400mb.
Something is corrupting the database.
I have to stop spamassassin, rm bayes* and restart spamassassin. 

Thanks.



------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

[Bug 5482] cannot open bayes databases

Posted by bu...@bugzilla.spamassassin.org.

http://issues.apache.org/SpamAssassin/show_bug.cgi?id=5482


spamassassin@invoca.ch changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|cannot open bayes databases |cannot open bayes databases




------- Additional Comments From spamassassin@invoca.ch  2007-06-12 23:58 -------
I see the same problem since 3.2.0, now also with 3.2.1. We are using SA with
spampd with maxchildren set to 25. This has worked fine for years until 3.2.0.

The only real difference I see is that after wiping bayes_*, SA didn't start
using bayes_journal, which always was used before.

I have now set "bayes_learn_to_journal 1", let's see how it works.




------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

[Bug 5482] cannot open bayes databases

Posted by bu...@bugzilla.spamassassin.org.

http://issues.apache.org/SpamAssassin/show_bug.cgi?id=5482


spamassassin@invoca.ch changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |spamassassin@invoca.ch






------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

[Bug 5482] cannot open bayes databases

Posted by bu...@bugzilla.spamassassin.org.

http://issues.apache.org/SpamAssassin/show_bug.cgi?id=5482





------- Additional Comments From abins@tc.program.com.tw  2007-08-16 19:00 -------
I have the same problem on 3.2.2 on Linux platform (Fedora Core 3). The log 
file shows:

bayes: cannot open bayes databases /tmp/.spamassassin/bayes_* R/W:
lock failed: Interrupted system call

now I try the setting below and see how it works.

bayes_auto_expire 0
bayes_learn_to_journal 1
bayes_journal_max_size 0

http://rivviepop.wordpress.com/2006/09/09/spamassassin-bayes-and-berkeley-db/



------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

[Bug 5482] cannot open bayes databases

Posted by bu...@bugzilla.spamassassin.org.

http://issues.apache.org/SpamAssassin/show_bug.cgi?id=5482





------- Additional Comments From spamassassin@invoca.ch  2007-08-16 22:26 -------
Using "bayes_learn_to_journal 1" made it work for me. I guess using

bayes_auto_expire 0
bayes_journal_max_size 0

makes you end up in other problems with the size of you bayes.



------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.