I've had a problem since adding rulesets to SpamAssassin. I've started to get these errors in my logs (some of the numbers vary):
Apr 11 00:21:26 gloop mimedefang-multiplexor[24463]: Slave 15 stderr: Out of memory during request for 1028 bytes, total sbrk() is 98183168 bytes! Apr 11 00:21:54 gloop mimedefang-multiplexor[24463]: Slave 12 stderr: Out of memory during "large" request for 135168 bytes, total sbrk() is 98207744 bytes at /usr/local/lib/perl5/site_perl/5.8.6/Mail/SpamAssassin/PerMsgStatus.pm line 2222. Failed to compile body SpamAssassin tests, skipping: (Out of memory during "large" request for 69632 bytes, total sbrk() is 98230272 bytes at (no file), rule VIRUS_WARNING235, line 822. ) top(1) says I have anywhere from as low as 200MB to as high as 400MB+ of RAM available, so I'm really confused as to where the problem is. I use rulesets via RDJ, so unless the author really dorked something up (which I believe unlikely), then I'm reduced to removing rules? Does sbrk(2) require contiguous memory and I'm dealing with a memory fragmentation issue? Did I go overboard with the rulesets SA is using? Am I being stupid? :) TRUSTED_RULESETS="TRIPWIRE ANTIDRUG RANDOMVAL BOGUSVIRUS SARE_EVILNUMBERS0 SARE_EVILNUMBERS1 SARE_EVILNUMBERS2 SARE_REDIRECT_POST300 SARE_BAYES_POISON_NXM SARE_HTML SARE_HEADER SARE_SPECIFIC SARE_ADULT SARE_BML SARE_FRAUD SARE_SPOOF SARE_RANDOM SARE_SPAMCOP_TOP200 SARE_OEM SARE_GENLSUBJ SARE_HIGHRISK SARE_UNSUB SARE_URI0 SARE_URI1 SARE_URI_ENG SARE_OBFU0 SARE_OBFU1 SARE_OBFU2 SARE_STOCKS FVGT_meta FVGT_body FVGT_headers FVGT_rawbody FVGT_subject FVGT_uri" Thanks! -- Dave _______________________________________________ NOTE: If there is a disclaimer or other legal boilerplate in the above message, it is NULL AND VOID. You may ignore it. Visit http://www.mimedefang.org and http://www.roaringpenguin.com MIMEDefang mailing list [email protected] http://lists.roaringpenguin.com/mailman/listinfo/mimedefang
