On Fri, 13 Mar 2009, Savoy, Jim wrote:
On Fri, 13 Mar 2009, Savoy, Jim wrote:
[23409] dbg: locker: safe_lock: trying to get lock on
/var/spool/spamassassin/bayes with 300 timeout
[23409] dbg: locker: safe_lock: timed out after 300 seconds
(it sat for 3 minutes at each of the two "300 timeout"
On Fri, 13 Mar 2009, Savoy, Jim wrote:
>> [23409] dbg: locker: safe_lock: trying to get lock on
>> /var/spool/spamassassin/bayes with 300 timeout
>> [23409] dbg: locker: safe_lock: timed out after 300 seconds
>>
>> (it sat for 3 minutes at each of the two "300 timeout" warnings).
>John Hardin wro
On Fri, 13 Mar 2009, Savoy, Jim wrote:
[23409] dbg: locker: safe_lock: trying to get lock on
/var/spool/spamassassin/bayes with 300 timeout
[23409] dbg: locker: safe_lock: timed out after 300 seconds
(it sat for 3 minutes at each of the two "300 timeout" warnings).
Disable auto-expiry in your
upted system call"
errors. I checked the /var/spool/spamassassin directory and saw that it
had over 300 large (10-to-20 meg)
bayes_toks.expire files in it. I google-searched this and found that
several others had this problem, so I
attempted to resolve it the same way they did. Only it didn&
, unexpected
> result, calculating optimal atime delta (first pass)
> [3990] dbg: bayes: expiry max exponent: 9
> OK, It finally started giving me more output after about 45 minutes.
> Now I am seeing the following lines repeating over and over again in
> the debug info. The bay
Derek Catanzaro wrote:
Matt Kettler wrote:
Derek Catanzaro wrote:
Matt Kettler wrote:
Derek Catanzaro wrote:
I have a ton of bayes_toks.expire files listed in
/root/.spamassassin. Is it safe to delete these files?
Yes, provided no expire process is currently
Matt Kettler wrote:
Derek Catanzaro wrote:
Matt Kettler wrote:
Derek Catanzaro wrote:
I have a ton of bayes_toks.expire files listed in
/root/.spamassassin. Is it safe to delete these files?
Yes, provided no expire process is currently running and using one
Matt Kettler wrote:
That's *enormous* for bayes_toks. It should be something on the order of
10-20 megs with the default bayes_expiry_max_db_size settings.
Since your bayes DB has so many excess tokens, it may take sa-learn
--force-expire a VERY long time to actually do the expire. Bayes Expiry
Derek Catanzaro wrote:
> Matt Kettler wrote:
>> Derek Catanzaro wrote:
>>
>>> I have a ton of bayes_toks.expire files listed in
>>> /root/.spamassassin. Is it safe to delete these files?
>> Yes, provided no expire process is currently running and us
Matt Kettler wrote:
Derek Catanzaro wrote:
I have a ton of bayes_toks.expire files listed in
/root/.spamassassin. Is it safe to delete these files?
Yes, provided no expire process is currently running and using one.
I did wind up deleting all of the bayes_toks.expire files, there
Derek Catanzaro wrote:
> I have a ton of bayes_toks.expire files listed in
> /root/.spamassassin. Is it safe to delete these files?
Yes, provided no expire process is currently running and using one.
> I did check the FAQ regarding "manybayestoksexpirefiles" but from wh
I have a ton of bayes_toks.expire files listed in /root/.spamassassin.
Is it safe to delete these files? I did check the FAQ regarding
"manybayestoksexpirefiles" but from what I can tell the directory is not
set to use sticky bit. Here is my ls -la results on the directory
.spamassassin/bayes_* R/W:
lock failed: Interrupted system call" in the logs.
I've been reading the FAQ and googling around but I can't figure out the best
configuration. As I could understand, it is convenient when you have a heavy
site to tell
spamassassin in local.cf "baye
On Tuesday 11 October 2005 08:34 pm, Justin Mason wrote:
> Chris writes:
> > I've got two files that have appeared in my $.Spamassassin folder, one
> > is bayes_toks.expire14973 and the other has .expire15267. Both are
> > dated yesterday, 10 Oct at 8:00pm and 8:01pm. Are these supposed to be
> >
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Chris writes:
> I've got two files that have appeared in my $.Spamassassin folder, one is
> bayes_toks.expire14973 and the other has .expire15267. Both are dated
> yesterday, 10 Oct at 8:00pm and 8:01pm. Are these supposed to be there?
> I've not
I've got two files that have appeared in my $.Spamassassin folder, one is
bayes_toks.expire14973 and the other has .expire15267. Both are dated
yesterday, 10 Oct at 8:00pm and 8:01pm. Are these supposed to be there?
I've not noticed them before. SA 3.1 is running.
--
Chris
Registered Linux U
16 matches
Mail list logo
