-----Original Message----- From: doktour1 [mailto:[EMAIL PROTECTED] Sent: Wednesday, 11 June 2008 08:02 a.m. To: users@spamassassin.apache.org Subject: HELP!! spamasssin killing my server
If I disable spamassassin in my procmail file. The server load goes down to 85 or less processes in a matter of mintues, but then tons of spam get through to my users. I am running freebsd 5.1 using sendmail and procmail running spamc (spamd loading at startup). The only thing that keeps the server from crashing is to throttle sendmail at 50 connections. But this is unworkable because it delays deliver of mail for several hours. PLEASE HELP IF YOU CAN, ANY ADVICE WOULD HELP SAVE MY SANITY --AS MY HAIR IS ALREADY GONE! Below is the spamd debug log, followed by all of the configuration files for spamassassin. Thank you! Here is a spamd debug log. <SNIP> ----------------------------------------------------------------------- I saw the message from Kevin, not only do you have fix the INET socket problem but there are other config issues too. Tue Jun 10 14:55:37 2008 [72096] dbg: spf: cannot load Mail::SPF module or create Mail::SPF::Server object: Can't locate Mail/SPF.pm in @INC (@INC contains: ...<SNIP> The problem above could be caused by a Perl upgrade, or Perl CPAN module installation, or outright hasn't worked since you set things up. Interestingly it falls back on a legacy module that works. But it is interesting, because what caused this could have caused other problems too. Tue Jun 10 14:55:40 2008 [72216] dbg: config: read_scoreonly_config: cannot open "/usr/home/orkids/.spamassassin/user_prefs": No such file or directory Hmmm. Tue Jun 10 14:55:40 2008 [72218] dbg: config: read_scoreonly_config: cannot open "/home/britt/.spamassassin/user_prefs": No such file or directory Hmmm. Tue Jun 10 14:55:40 2008 [72216] dbg: conf: trusted_networks are not configured; it is recommended that you configure trusted_networks manually Do what it says ^ I suggest you : - make sure your Black/Block Lists are working, test them manually if you have to. Make sure they don't take too much time to look up, if they do disable for now until you've got performance back. - Check for any Perl upgrade that may have happened recently and assess if you need to go back a version. - Check for any Perl Modules that might have been installed lately - this might seem silly but it could save SA. I have a file that Spamassassin doesn't require, that is a perl module. If it is copied into SA's search path, my scan times go from 7 seconds to 60 seconds plus. So Beware Be Warned. - Verify that DCC is working OK, do this manually. - Do you use CPAN ? Have you used it recently? I had to hose my SA install thanks to a few modules being installed via CPAN. This was on Debian however, and if you don't apt-get these things, you can expect these problems. So there's a bit of work to tidy up, but the main one is the one Kevin was talking about with the "Could not create INET socket". Make sure you've set a good allowable amount of child processes. I use 10 on an HP DL380 2x3Ghz 2Gb RAM with no worries. HTH Cheers, Mike
