Classification: PUBLIC

OK. Here's the resolution.

The problem was that Razor kept doing a discovery each pass.  When I did a
razor-admin -d -discover it did not write to the catalogue and nominated
files.  It turns out that two .lock files were in there (for whatever
reason) as stopped these from being updated.

The other problem was the Razor zone was incorrect for Razor2.  It should
be: razor2.cloudmark.com.  My config file had the old Razor1 domain.   This
is now fixed.

Now my average is under 1 second for the Razor test.

FWIW:
How I troubleshot this problem

In the ~/.razor/razor-agent.conf file I set:
   logfile = razor-agent.log
   debuglevel = 15

In the /etc/mail/spamassassin/local.cf file I set:
   timelog_path /tmp/satiming
   razor_config ~/.razor/razor-agent.conf

By looking at the timing logs written to /tmp/satiming, I saw that razor2
was the delay point.
By setting razor debug level to 15, verbose debug is written by razor to
razor-agent.log.
By looking at the razor-agent.log, I saw that the two files weren't being
written to.

Be sure to set debuglevel back to 5 for transactions or 1 for startup and
errors only

<<Dan>>
|-----Original Message-----
|From: Smart, Dan 
|Sent: Monday, November 04, 2002 11:49 AM
|To: Theo Van Dinter; Smart, Dan
|Cc: [EMAIL PROTECTED]
|Subject: RE: [SAtalk] Public Razor2 is slow as Christmas
|
|
|Classification: PUBLIC
|
|I'm located on a T-1 into the AT&T Atlanta hub.  No "barbed 
|wire" here.  
|
|Thanks for the info.
|
|<<Dan>>
|
||-----Original Message-----
||From: Theo Van Dinter [mailto:[EMAIL PROTECTED]]
||Sent: Monday, November 04, 2002 10:31 AM
||To: Smart, Dan
||Cc: [EMAIL PROTECTED]
||Subject: Re: [SAtalk] Public Razor2 is slow as Christmas
||
||
||On Mon, Nov 04, 2002 at 09:14:19AM -0600, Smart, Dan wrote:
||> In my timings, I have found that the public Razor2 takes a
||minimum of
||> 8 seconds, and an average of 10 seconds.  It often goes much longer:
||> 15-18 seconds.
||
||I guess it depends where you are, I usually have a response in
||< 2 seconds.
||
||> Question #1: Has the timeout parameter for Razor been fixed?
||
||It's "fixed" in CVS.  There is no way to completely fix it in
||SA (the problem comes from Net::Ping called by razor 2.20), so 
||I put in a kluge to try working around the problem.
||
||> Question #2: Does anyone get better performance than this?
||
||yes, it generally works pretty well for me.
||
||> Question #3: Can you create a local replica of the public Razor
||> database to speed things up (<OT> a little)
||
||Since the server is proprietary, even if you had a copy you
||couldn't do anything with it.  I think someone wrote a proxy 
||for razor 1 that would cache results locally, but I don't 
||think they've done it up for razor 2 yet.
||
||--
||Randomly Generated Tagline:
||"... until this thing blows up, or yells 'stop', or says Uncle or 
|| something..."                  - Prof. Demetry
||
|


-------------------------------------------------------
This sf.net email is sponsored by: See the NEW Palm 
Tungsten T handheld. Power & Color in a compact size!
http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0001en
_______________________________________________
Spamassassin-talk mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/spamassassin-talk

Reply via email to