Hi Justin,

If you can tell me what you want me to do when it is doing the problem, I'm
happy to. It's easily reproduced here, I just need to wait a little while!

At the moment I'm restarting spamd on a semi regular basis which is getting
to be a bit of a drama :)

Cheers

Gav



On 11/11/04 3:48 PM, "Justin Mason" <[EMAIL PROTECTED]> wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> 
> there's been a few reports of this, but we're really mystified.
> A test case would help, but it doesn't seem easily reproducable
> for anyone :(
> 
> - --j.
> 
> Gavin Cato writes:
>> Anyone? :(
>> 
>> On 10/11/04 8:56 AM, "Gavin Cato" <[EMAIL PROTECTED]> wrote:
>> 
>>> Hiya,
>>> 
>>> Got a bit of a problem.
>>> 
>>> Have this setup ;
>>> 
>>> Internet --> avmx01 server (Postfix + ClamAV + Amavisd) --> SA server
>>> (Sendmail + SA 3.0.1) --> Remote MTA
>>> 
>>> The avmx01 server was upgraded to a much more powerful machine 2 days ago. I
>>> don't think that should be causing this problem though.
>>> 
>>> The SA server is sometimes running out of memory (hitting swap) as the spamd
>>> process is sometimes not enforcing the maximum children setting.
>>> 
>>> Twice overnight the box was hitting swap so hard it wasn't really doing
>>> anything useful - each time a ;
>>> 
>>> ps ax | grep spamd | wc -l
>>> 
>>> Showed well over 200 processes.
>>> 
>>> It just did it again when I came into work, though this time I caught it
>>> when it was up to 189 processes.
>>> 
>>> I'm starting it via this ;
>>> 
>>> /usr/local/bin/spamd --max-children=25 --listen-ip=x.x.x.x
>>> --allowed-ips=y.y.y.y,z.z.z.z -d -u nobody
>>> 
>>> It is called via spamass-milter.
>>> 
>>> The server is running FreeBSD 4.9 with 2.5gb RAM with 2 x 1.1ghz P3's & 10k
>>> RPM SCSI.
>>> 
>>> Any ideas on what I can look for? After restarting spamd everything runs
>>> perfect, as I wrote this it is sticking to 26 spamd processes (normal) and
>>> it is holding it to that. But it won't stay that away forever based on last
>>> night.
>>> 
>>> At the moment I'll probably put something in cron to kill and restart spamd
>>> every couple of hours.
>>> 
>>> Gav
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>> 
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.2.4 (GNU/Linux)
> Comment: Exmh CVS
> 
> iD8DBQFBku8OMJF5cimLx9ARAguiAJ9NQkwIe1aZOYNSUe4quzcF/50uiACdHe2w
> DcRRhlL14UGW7hFm3e07Pm4=
> =mua/
> -----END PGP SIGNATURE-----
> 


Reply via email to