Bret Miller wrote:
I used to have problems with bayes locking and journaling. When it
finally corrupted the database, I decided it was time to put it into a
real SQL database instead of using DB_File. Haven't had a single problem
with bayes CPU or locking since.
Maybe it's time you consider
Ok, I may say something dumb, but have you tried to clear the bayes db
with :
sa-learn --clear --dbpath
-- Fab
Bret Miller wrote:
I used to have problems with bayes locking and journaling. When it
finally corrupted the database, I decided it was time to put
it into a
real SQL database instead of using DB_File. Haven't had a
single problem
with bayes CPU or locking since.
Me again. Since I'm not getting any responses I better keep posting more
information as I've made some more investigating today.
Sometimes when I run sa-learn --force-expire I get this response almost
immediately:
Bus error (core dumped)
When I run again the process just hogs until I break it
Here's an interesting observation.
I set bayes_auto_expire to 0 as a temporary solution, I thought, and
restarted spamd. The hogging occurs at least as often as before. Am I
looking in the wrong direction or wouldn't this have helped something?
Another observation:
# sa-learn --dump magic:
Me again. Since I'm not getting any responses I better keep
posting more
information as I've made some more investigating today.
Sometimes when I run sa-learn --force-expire I get this
response almost immediately:
Bus error (core dumped)
When I run again the process just hogs until I break
Bret Miller wrote:
I used to have problems with bayes locking and journaling. When it
finally corrupted the database, I decided it was time to put it into a
real SQL database instead of using DB_File. Haven't had a single problem
with bayes CPU or locking since.
Maybe it's time you consider
Andreas Pettersson wrote:
Bus error (core dumped)
This *can* be the symnptom of a hardware problem, such as bad memory or a bad
disk.
If you have a disk thats going bad, the symptoms often are corrupt files and
extremeley slow writes (because the disk controller retries the write operation
Jonas Eckerman wrote:
Andreas Pettersson wrote:
Bus error (core dumped)
This *can* be the symnptom of a hardware problem, such as bad memory
or a bad disk.
If you have a disk thats going bad, the symptoms often are corrupt
files and extremeley slow writes (because the disk controller
On Mon, 25 Sep 2006, Andreas Pettersson wrote:
Bret Miller wrote:
I used to have problems with bayes locking and journaling. When it
finally corrupted the database, I decided it was time to put it into a
real SQL database instead of using DB_File. Haven't had a single problem
with bayes CPU
I used to have problems with bayes locking and journaling. When it
finally corrupted the database, I decided it was time to put
it into a
real SQL database instead of using DB_File. Haven't had a
single problem
with bayes CPU or locking since.
Maybe it's time you consider using MySQL?
Bret Miller wrote:
Are you sure you have enough RAM to handle the number of threads you are
running?
Yes, I'm pretty sure 512MB is enough.
No swapping going on, and I only scan msgs smaller than 500 KB.
Avg scan time is about 3-4 sec and I scan less than 1 a day.
Regards,
Andreas
On Mon, 25 Sep 2006, Andreas Pettersson wrote:
Same Bus error (core dumped) as before when running manual expire.
When I make another try it hogs, and is still doing so after 5 minutes. But
this time I'll wait at least 30 minutes, just to make sure.
And just to make it clear; the spamd daemon
Logan Shaw wrote:
One thing you could try is running db4_recover (or db_recover,
depending on how it's installed) on the Bayes database.
Seems like something to try. But I don't understand the utility:
usage: db_recover [-ceVv] [-h home] [-P password] [-t [[CC]YY]MMDDhhmm[.SS]]
How can I
Ok, more information here.
I found in spamd.log this line when the problem started:
Fri Sep 22 19:55:22 2006 [74581] warn: bayes: expire_old_tokens: child
processing timeout at /usr/local/bin/spamd line 1082
which was followed by lots of these:
Fri Sep 22 19:55:52 2006 [74581] warn: bayes:
Hi, me again ;)
I'm pretty confident that the hogging occurs when SA is trying to sync
the bayes. The bayes_journal is cleared exactly when the hogging begins.
And when I run sa-learn --sync I get the very same hogging effect.
The permissions seems ok, doesn't it?
-rw--- 1 spamd wheel
16 matches
Mail list logo
