Noel Jones wrote: >Richard J. Kieran wrote: >> I can't believe I got not a single response to this, so I'm trying again: >> >> I'm running clamd with MIMEDefang on a CentOS machine. Once in a while there >> will be a day when there are many "Problem running virus scanner: code=999" >> errors, anywhere from 1 or 2 (who cares?) to 4486 (now I'm concerned...), >> like yesterday. The next >> day, all will be back to normal until it happens again. Here is a maillog >> entry: >> >> Dec 1 00:03:15 fdr mimedefang.pl[4798]: mB153Ere005745: Could not connect >> to clamd daemon at /var/spool/MIMEDefang/clamd.sock > >This is the real problem, mimedefang can't connect to clamd. >Maybe clamd isn't running, or maybe there are too many >connections. If clamd is running, check the settings of >MaxConnectionQueueLength and MaxThreads in clamd.conf. Thanks. I tried bumping these settings up from the defaults. We'll see what happens. > > >The clamd "clamd.sock is in use" error will only occur when >you start clamd when it's already running. I have a script that shuts down then restarts all of the spam-filter related programs. I sometimes see this error when I run it manually. I also invoke this script when too many virus scanner errors are seen in the log file by a script that runs under cron hourly. I'll build in a delay between killing and restarting clamd and see if that helps with this one. Richard > > >-- >Noel Jones
_______________________________________________ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://www.clamav.net/support/ml
