Hi gang. Just ran into a weird problem. My qmail server suddenly refused SMTP traffic from any source. When I would try to send mail from my workstation via KMail, I would get a message indicating the following:
qq temporary problem (#4.3.0) Further digging in the logs (/var/log/qmail/qmail-smtpd/current) revealed a few lines like so (on one line): @4000000040cfeb401fd44ecc X-Qmail-Scanner-1.16:[snow10873679884267417] clam_scanner: corrupt or unknown ClamAV scanner error or memory/resource/ perms problem - exit status 50 So, the problem appeared to be ClamAV, so I checked into it, and sure enough, clamd wasn't running. Started it and restarted qmail, and tried to send again. The same error occurred. So I did a freshclam and was on the verge of reinstalling ClamAV when I decided to do a google search for the longer error message. Gotta luv Google for troubleshooting - sure enough, I found a number of hits. The very first entry suggested this might be a process limit (SOFTLIMIT_OPTS). So I checked my setting in /var/qmail/control/conf-common. I had previously changed this from the default (as suggested in the Life With qmail guide), but set to "-m 15000000" and all was good. I decided to bump this and see what happened - so the line was changed to: SOFTLIMIT_OPTS="-m 30000000" then restarted qmail, and tested sending my mail via KMail - it worked as it should have, and my mail was (hopefully) delivered, with no visible errors. I'm posting this here with detail in hopes I might save someone else some grief. This is a case of the reported error not indicating the actual problem, but indicating a symptom of the problem. These are sometimes tough to find (speaking from a coding perspective). So I guess the only real question left is why did my box suddenly exceed this setting, even though nothing had changed? No new software was added, no new updates (though there were a few unrelated updates last week). I'm not sure I totally understand the SOFTLIMIT_OPTS setting (which I think is used to set a ulimit for the qmail process?), so maybe the answer is very clear with that background knowledge. Anyone have any suggestions? Shawn _______________________________________________ clug-talk mailing list [EMAIL PROTECTED] http://clug.ca/mailman/listinfo/clug-talk_clug.ca
