You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@spamassassin.apache.org by jds <jd...@losdos.dyndns.org> on 2005/04/29 06:09:50 UTC
razor returns error 202 after ~12 to 24 hours
hi,
recently i've noticed that razor returns "err 202" messages after
some period of time (~12 to 24 hrs) or some number of messages,
and correspondingly does not report spam results back to SA.
restarting SA fixes the problem.
first, a little about the environment...
# uname -a
SunOS taco 5.9 Generic_112233-08 sun4u sparc SUNW,Ultra-5_10
# spamassassin --version
SpamAssassin version 3.0.2
# grep razor /etc/mail/spamassassin/local.cf
use_razor2 1
razor_config /etc/razor/razor-agent.conf
# cat /etc/razor/razor-agent.conf
#
# Autogenerated by Razor-Agents v2.67
# Sun Apr 24 14:48:25 2005
# Created with all default values
#
logfile = /var/log/razor.log
debuglevel = 4
identity = identity
ignorelist = 0
listfile_catalogue = servers.catalogue.lst
listfile_discovery = servers.discovery.lst
listfile_nomination = servers.nomination.lst
logfile = razor-agent.log
logic_method = 4
min_cf = ac
razorzone = razor2.cloudmark.com
rediscovery_wait = 172800
report_headers = 1
sort_by_distance = 0
turn_off_discovery = 0
use_engines = 4,8
whitelist = razor-whitelist
so, i am running SA 3.0.2 and 2.67. SA is started as follows:
/usr/local/bin/spamd -d -c \
--max-children=3 --max-conn-per-child=20 \
--syslog-socket=inet --syslog=local2 \
--pidfile /var/run/spamd.pid --helper-home-dir=/etc/razor
so what's the problem??? read on...
for a limited duration after SA is started, razor returns valid
spam/nospam results and accordingly those results are used for SA
scoring. however, eventually razor will not do it's job, reporting
via the log "got err 202 for query" -- seems to be an authentication
error of some type. note that my setup *does not* report spam to
razor's servers; i am just acting as a razor client at this time.
based on some googling, i have set up a daily cron job to run discovery:
26 5 * * * /usr/local/bin/razor-admin -d --discover -home=/etc/razor
this does not rectify the problem, nor does manually running the discover.
HOWEVER, if i kill and restart SA, razor once again returns valid
spam/nospam results. and thus the cycle is started all over again.
within 24 hours, i will have to manually restart SA in order for
razor to perform nominally.
with the log debug level bumped up to 4, a typical "good" razor
session looks like this:
--------------------------
Apr 26 19:29:41.082365 check[26012]: [ 2] [bootup] Logging initiated
LogDebugLevel=4 to file:/etc/razor/razor-agent.log
Apr 26 19:29:41.278709 check[26012]: [ 4] shock.cloudmark.com >> 36 server
greeting: sn=C&srl=5074&a=l&a=cg&ep4=7542-10
Apr 26 19:29:41.282039 check[26012]: [ 4] shock.cloudmark.com << 25
Apr 26 19:29:41.285963 check[26012]: [ 4] shock.cloudmark.com << 80
Apr 26 19:29:44.035750 check[26012]: [ 4] shock.cloudmark.com >> 20
Apr 26 19:29:44.038273 check[26012]: [ 3] mail 1 is known spam.
Apr 26 19:29:44.039466 check[26012]: [ 4] shock.cloudmark.com << 5
--------------------------
and a bad one like this:
--------------------------
Apr 26 20:51:25.930097 check[22901]: [ 2] [bootup] Logging initiated
LogDebugLevel=4 to file:/etc/razor/razor-agent.log
Apr 26 20:51:26.157304 check[22901]: [ 4] shock.cloudmark.com >> 36 server
greeting: sn=C&srl=5076&a=l&a=cg&ep4=7542-10
Apr 26 20:51:26.159341 check[22901]: [ 4] shock.cloudmark.com << 25
Apr 26 20:51:26.160681 check[22901]: [ 4] shock.cloudmark.com << 14
Apr 26 20:51:26.310735 check[22901]: [ 4] shock.cloudmark.com >> 144
Apr 26 20:51:26.317887 check[22901]: [ 4] shock.cloudmark.com << 5
Apr 26 20:51:26.488409 check[22901]: [ 4] 66.151.150.12 >> 35 server
greeting: sn=D&srl=493&a=l&a=cg&ep4=7542-10
Apr 26 20:51:26.489841 check[22901]: [ 4] 66.151.150.12 << 12
Apr 26 20:51:26.572199 check[22901]: [ 4] 66.151.150.12 >> 32
Apr 26 20:51:26.574262 check[22901]: [ 4] 66.151.150.12 << 12
Apr 26 20:51:26.657019 check[22901]: [ 4] 66.151.150.12 >> 51
Apr 26 20:51:26.663241 check[22901]: [ 4] 66.151.150.12 << 132
Apr 26 20:51:26.745575 check[22901]: [ 4] 66.151.150.12 >> 31
Apr 26 20:51:26.748203 check[22901]: [ 4] mail 1.0 e=4
sig=8_6R7KVU43wOAl6ULgv31zXV2hkA: got err 202 for query:
HASH - HASH(0x15b4f68),4 keys
a => c
e => 4
ep4 => 7542-10
s => 8_6R7KVU43wOAl6ULgv31zXV2hkA
Apr 26 20:51:26.749452 check[22901]: [ 4] mail 1.1 e=4
sig=eh8Uzup9NTI30knTF8cNMtAD26IA: got err 202 for query:
HASH - HASH(0xd19054),4 keys
a => c
e => 4
ep4 => 7542-10
s => eh8Uzup9NTI30knTF8cNMtAD26IA
Apr 26 20:51:26.750554 check[22901]: [ 4] mail 1.1 e=8 sig=VaVxQdz2b8IA:
got err 202 for query:
HASH - HASH(0x15b5034),3 keys
a => c
e => 8
s => VaVxQdz2b8IA
Apr 26 20:51:26.751440 check[22901]: [ 3] mail 1 is not known spam.
Apr 26 20:51:26.752890 check[22901]: [ 4] 66.151.150.12 << 5
--------------------------
finally,
a few days worth of razor logging is here:
http://losdos.dyndns.org:8080/mail-razrlog.txt
once the 202 errors start, razor will not report a spam message until
SA is restarted. the razor log simply shows the 202 errors.
any clues as to why this happens? and what i need to do to fix it?
thanks for any insight,
jim