SpamAssassin timed out and was killed... box too slow?

[Julian Field]

At 17:28 04/06/2003, you wrote:
>At 04:37 PM 6/4/2003 +0100, you wrote:
>>Try setting
>>skip_rbl_checks 1
>
>
>I've already set skip_rbl_checks 1 in the spam.assassin.prefs.conf
>file.  In the debug mode, it said  that Razor2 and Pyzor were not
>availabe.  So I also made the following entries in spam.assassin.prefs.conf
>so that I can eliminate any of the below to be the cause of the problem:
>use_dcc 0
>use_pyzor 0
>use_razor1 0
>use_razor2 0
>use_bayes 0
>
>In debug mode, a couple of lines seem bothersome -
>
>unix passed to setlogsock, but path not available at
>/opt/MailScanner/lib/MailSc
>anner/Log.pm line 62
>
>and
>
>debug: Failed to parse line in SpamAssassin configuration, skipping:
>defang_mime 0
>
>Could they be the cause of the timeout problem?

Shouldn't be, no. Try reducing to 1 child process (Max Children = 1 in
MailScanner.conf) then see how it behaves.


>Thanks.
>
>Vasantha
>
>
>>in spam.assassin.prefs.conf and see if that helps. You will need to restart
>>MailScanner after setting this.
>>
>>At 16:22 04/06/2003, you wrote:
>>>We've a SunBlade 100 (500 Mhz) with 500 Mem running Solaris 2.8.  The
>>>machine does nothing other than MailScanning.  It is not even a MailServer.
>>>
>>>The MailScanner itself works perfectly.  It is only when I turn on
>>>SpamAssassin that the load on the machine gets really high.  A lot of mail
>>>gets accumulated in the incoming queue waiting to be scanned.  I'm running
>>>15 mailscanner processes and it forks and gets doubled whenever I turn on
>>>SpamAssassin.  Pretty soon the following error shows up in the log:
>>>Jun  3 15:57:07 nisc4 MailScanner[5766]: SpamAssassin timed out and was
>>>killed, consecutive failure 1 of 20
>>>Jun  3 15:57:41 nisc4 MailScanner[5758]: SpamAssassin timed out and was
>>>killed, consecutive failure 1 of 20
>>>Jun  3 15:58:14 nisc4 MailScanner[5750]: SpamAssassin timed out and was
>>>killed, consecutive failure 1 of 20
>>>Jun  3 16:00:08 nisc4 MailScanner[5774]: SpamAssassin timed out and was
>>>killed, consecutive failure 1 of 20
>>>
>>>Have others seen this problem?  How have you fixed the problem?  We've
>>>MailScanner-4.20-3 with SpamAssassin-2.50.  The SpamAssassin Timeout is set
>>>to 40 and Scanner timeout is set to 10 (that is the default in that version
>>>of MailScanner)
>>>
>>>I'd really appreciate some suggestions.
>>>
>>>Thanks.
>>>
>>>Vasantha
>>>
>>>
>>>
>>>
>>>At 05:37 PM 6/3/2003 -0500, you wrote:
>>>>What kind of horsepower does your box have?  OS?
>>>>
>>>>Mike
>>>>
>>>>
>>>>-----Original Message-----
>>>>From: MailScanner mailing list [mailto:MAILSCANNER at JISCMAIL.AC.UK] On
>>>>Behalf
>>>>Of Chris W. Parker
>>>>Sent: Tuesday, June 03, 2003 5:28 PM
>>>>To: MAILSCANNER at JISCMAIL.AC.UK
>>>>Subject: Re: SpamAssassin timed out and was killed... box too slow?
>>>>
>>>>
>>>>Vasantha Narayanan <mailto:vnarayan at HAVERFORD.EDU> wrote:
>>>>
>>>> > Did you find a solution yet?
>>>>
>>>>No I did not.
>>>>
>>>> > I'm having the same problem.
>>>>
>>>>I feel your pain. :(
>>>>
>>>>
>>>>
>>>>Chris.
>>>
>>>VVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVV
>>>Vasantha Narayanan
>>>Networking and Systems                  email: vnarayan at haverford.edu
>>>Haverford College, PA                   Phone:
>>>610-896-1110
>>
>>--
>>Julian Field
>>www.MailScanner.info
>>MailScanner thanks transtec Computers for their support
>
>VVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVV
>Vasantha Narayanan
>Networking and Systems                  email: vnarayan at haverford.edu
>Haverford College, PA                   Phone:
>610-896-1110

--
Julian Field
www.MailScanner.info
Professional Support Services at www.MailScanner.biz
MailScanner thanks transtec Computers for their support