On Oct 12, 2004, at 10:56, [EMAIL PROTECTED] wrote:
On Tue, 12 Oct 2004, Scott Rothgaber wrote:Doug Hardie wrote:
have encountered quite a few situations in the last month where clamav
just stopped working properly and had to be manually restarted.
I had the same problem with spamass-milter a while back. What you need is a "watchdog" script, something like this...
We had a problem similar to this this week, however, the problem wasn't
due to a dead/core'd process. clamdscan actually hung for one reason or
another and clamd had to be shot down with a -9. This took place just
after the upgrade to .80rc4 and I attributed it to (possibly) having a rc3
clamd running with a rc4 clamdscan. Perhaps I did not adequately shut
down rc3 before the update. Either way, I assume that clamdscan shouldn't
hang if clamd is dead. I noticed that mail was backed up because the
amavis delivery agent (ADA?) hung when it relayed to amavisd. Eventually
the problem was found to be clamdscan hanging and restarting clamd (after
a -9) seemed to work.
Is anyone else experiencing similar problems?
The problems I had were all with version .75 and earlier. The .80rcs have worked very well for me. I had a timeout problem every morning at about 6 am for about 5 minutes until I increased the clamd timeout value. No timeouts this morning.
_______________________________________________ http://lists.clamav.net/cgi-bin/mailman/listinfo/clamav-users
