|
I'm using SA 2.11 with Razor 1.20, Postfix and
spamproxy. My spamproxy processes kept dying. I tracked the problem
down to them receiving an ALRM signal from somewhere. As far as I can
tell, that alarm is initiated from SA.
The two places I see an alarm set in SA are DNS.pm
and Reporter.pm. Both of these deal with killing the Razor check if it
times out. I reported a problem yesterday with my Razor check not
completing if the ~/.razor.lst file exists. This causes the following
error:
razor check skipped: No such file or
directory undefined Razor::Client
(A plain razor-check test works fine at that
point, but I have to remove ~/.razor.lst for SA to not complain. Of
course, the first time SA does a Razor check, the ~/.razor.lst file gets created
even if I put turn_off_discovery in the razor.conf file.)
My assumption is that the alarm does not get
shut off due to the failed Razor test and then that alarm somehow gets sent to
spamproxy which then dies.
For the time being, I configured spamproxy to
ignore the ALRM signal and that seems to have fixed my problem. Any ideas
on how to fix Razor, or if there may be some other issue at
work?
Thanks,
Karyl
|
