At 09:21 AM 1/24/2007, Aleksander wrote:
Hi,
Got a little problem.
I've noticed that sometimes clamd is restarted by monit (monitoring software).
monit is configured like this:
check process clamd with pidfile /var/lib/clamav/clamd.pid
start program = "/etc/init.d/clamd start"
stop program = "/etc/init.d/clamd stop"
if failed host 127.0.0.1 port 3310 type tcp proto clamav then restart
I've been using monit on clamd for several months, and haven't had a
failure like this. Maybe I'm just really lucky and monit never tried
a PING during an update, or maybe using the timeout parameter is what
helps. I'm using a local socket rather than a TCP port, don't know
how that affects it either.
Mine looks like:
check process clamd with pidfile /var/run/clamav/clamd.pid
start program = "/usr/local/etc/rc.d/clamav-clamd.sh start"
stop program = "/usr/local/etc/rc.d/clamav-clamd.sh stop"
if failed unix /var/run/clamav/clamd protocol clamav
timeout 30 seconds then restart
To make yours less sensitive to transient failures, you can change it to:
if failed host 127.0.0.1 port 3310 type tcp protocol clamav
timeout 30 seconds 2 times then restart
--
Noel Jones
_______________________________________________
Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net
http://lurker.clamav.net/list/clamav-users.html
