http://bugzilla.spamassassin.org/show_bug.cgi?id=2991





------- Additional Comments From [EMAIL PROTECTED]  2004-05-04 12:16 -------
Experiencing the same behaviour. The problem appears to be related to the 
bayes_toks file. In my case it grew to as much as 42 MB after some days of 
heavy 
spam processing on a busy mail relay server. The issue perhaps is that DB files 
don't usually shrink, but at some stage they grow too large to make DB cope 
with 
them properly. Then processes get stuck. Apparently it's those processes who 
are 
actually updating the database, not just reading it.

I tried to "sa-learn" --import to rebuild the files, but that took some 30 
minutes (which is outrageous even for a 42 MB file) and then dumped core.

Here's the debug output from that run:

debug: Score set 0 chosen.
debug: running in taint mode? no
debug: using "/usr/local/share/spamassassin" for default rules dir
debug: using "/usr/local/etc/mail/spamassassin" for site rules dir
debug: using "/home/hmo/.spamassassin/user_prefs" for user prefs file
debug: bayes: 97217 tie-ing to DB file R/O /home/hmo/.spamassassin/bayes_toks
debug: bayes: 97217 tie-ing to DB file R/O /home/hmo/.spamassassin/bayes_seen
debug: bayes: found bayes db version 2
debug: Score set 2 chosen.
debug: Initialising learner
debug: lock: 97217 created /home/hmo/.spamassassin/bayes.lock.mizar.origin-it.
net.97217
debug: lock: 97217 trying to get lock on /home/hmo/.spamassassin/bayes with 0 
retries
debug: lock: 97217 link to /home/hmo/.spamassassin/bayes.lock: link ok
debug: bayes: 97217 tie-ing to DB file R/W /home/hmo/.spamassassin/bayes_toks
debug: bayes: 97217 tie-ing to DB file R/W /home/hmo/.spamassassin/bayes_seen
debug: bayes: found bayes db version 0
debug: bayes: new db, set db version 2 and 0 tokens
upgrading to DB_File, please be patient: /home/hmo/.spamassassin/old_bayes_seen
DB_File: copied 44520 entries.
upgrading to DB_File, please be patient: /home/hmo/.spamassassin/old_bayes_toks
Segmentation fault (core dumped)




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

Reply via email to