Re: [SAtalk] System goes down

2003-09-04 Thread Nick Leverton
Kandji Développeur [EMAIL PROTECTED] wrote: The story : linux RedHat 7.3 - kernel 2.4.18#3 on smp system (2xPII) perl 5.6.1 spamassassin version 2.55 postfix 1.1.12-0.7 1) The system had been running for 90 days. 2) I installed spamassassin AND pop-before-smtp the same day 3) The system

Re: [SAtalk] System goes down - Reply to Nick Leverton

2003-09-04 Thread kandjidev
Thanks for the info, I've just upgraded my development server to 2.4.22.. It seems to work like a charm... Any further advice about this kernel too ?? Thanks On 4 Sep 2003 at 14:18, Nick Leverton wrote: Kandji Développeur [EMAIL PROTECTED] wrote: The story : linux RedHat 7.3 - kernel

RE: [SAtalk] System goes down

2003-09-03 Thread Martin, Jeffrey
described here. -Original Message- From: Kandji Développeur [mailto:[EMAIL PROTECTED] Sent: Tuesday, September 02, 2003 10:05 AM To: [EMAIL PROTECTED] Subject: [SAtalk] System goes down Hello, I've been using spamassassin for 2 weeks and it (*seems*) that it caused my system to go down

Re: [SAtalk] System goes down

2003-09-03 Thread Simon Byrnand
At 15:18 2/09/2003 -0400, [EMAIL PROTECTED] wrote: FWIW, Sendmail 8.12.9 (and possibly prior versions) supports a limit: define(`confMAX_DAEMON_CHILDREN', `24')dnl All that does is limits the number of simultanous children the main sendmail process will launch in response to incomming

Re: [SAtalk] System goes down

2003-09-03 Thread Simon Byrnand
At 19:26 2/09/2003 +0100, Justin Mason wrote: Folks -- are you using the -m switch to limit how many spamds can run? If you don't use that, and you're using an MTA that also does not limit concurrent local delivery commands, like sendmail, this will be an issue. Try the -m switch. On some setups

[SAtalk] System goes down

2003-09-02 Thread Kandji Développeur
Hello, I've been using spamassassin for 2 weeks and it (*seems*) that it caused my system to go down... The story : linux RedHat 7.3 - kernel 2.4.18#3 on smp system (2xPII) perl 5.6.1 spamassassin version 2.55 postfix 1.1.12-0.7 1) The system had been running for 90 days. 2) I installed

RE: [SAtalk] System goes down

2003-09-02 Thread Gary Funck
You might be experiencing hardware problems that only occur under load. SA/spamd uses a lot of cpu and memory cycles. If it runs long enough, on large messages, it might push the cpu past its operating range temperature, if for example, the system cooling is marginal. Likewise, marginal memory

Re: [SAtalk] System goes down

2003-09-02 Thread Carlo Wood
On Tue, Sep 02, 2003 at 04:04:45PM +0200, Kandji Développeur wrote: Hello, I've been using spamassassin for 2 weeks and it (*seems*) that it caused my system to go down... The story : linux RedHat 7.3 - kernel 2.4.18#3 on smp system (2xPII) perl 5.6.1 spamassassin version 2.55

Re: [SAtalk] System goes down

2003-09-02 Thread Carlo Wood
Here is the output of 'ps auxw' at the moment the machine did hang. What immedeately catches the eye is the large number of /usr/bin/perl /usr/bin/spamd -d -u nobody processes. I thought that there should only ONE spamd be running? USER PID %CPU %MEM VSZ RSS TTY STAT START TIME

Re: [SAtalk] System goes down

2003-09-02 Thread Justin Mason
Folks -- are you using the -m switch to limit how many spamds can run? If you don't use that, and you're using an MTA that also does not limit concurrent local delivery commands, like sendmail, this will be an issue. Try the -m switch. --j.

Re: [SAtalk] System goes down

2003-09-02 Thread Karl Larsen
On Tue, 2 Sep 2003, Carlo Wood wrote: Here is the output of 'ps auxw' at the moment the machine did hang. What immedeately catches the eye is the large number of /usr/bin/perl /usr/bin/spamd -d -u nobody processes. I think you should have a single spamd listed and the many perl

Re: [SAtalk] System goes down

2003-09-02 Thread tnelson
] [EMAIL PROTECTED]cc: ceforge.net Subject: Re: [SAtalk] System goes down

Re: [SAtalk] System goes down

2003-09-02 Thread Brian Godette
Your system is being killed by Linux's OOM killer. The OOM killer in 2.4 series doesn't appear to be all that bright and I have had it kill init in the past which results in what you describe (pings but services down). You basically have two options, either add more memory or limit the number

Re: [SAtalk] System goes down

2003-09-02 Thread Carlo Wood
On Tue, Sep 02, 2003 at 07:26:02PM +0100, Justin Mason wrote: Folks -- are you using the -m switch to limit how many spamds can run? If you don't use that, and you're using an MTA that also does not limit concurrent local delivery commands, like sendmail, this will be an issue. Try the -m

Re: [SAtalk] System goes down

2003-09-02 Thread Carlo Wood
On Tue, Sep 02, 2003 at 01:47:02PM -0600, Brian Godette wrote: Your system is being killed by Linux's OOM killer. The OOM killer in 2.4 series doesn't appear to be all that bright and I have had it kill init in the past which results in what you describe (pings but services down). You

Re: [SAtalk] System goes down

2003-09-02 Thread Jack L. Stone
At 03:18 PM 9.2.2003 -0400, [EMAIL PROTECTED] wrote: FWIW, Sendmail 8.12.9 (and possibly prior versions) supports a limit: define(`confMAX_DAEMON_CHILDREN', `24')dnl Tony Nelson Tony, how does one arrive at the limit '24'.? Best regards, Jack L. Stone, Administrator Sage American