[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Monit tries once and stops monitoring?
From: |
Matthew Trent |
Subject: |
Monit tries once and stops monitoring? |
Date: |
Thu, 29 Jul 2004 09:23:09 -0700 |
User-agent: |
KMail/1.6.2 |
I'm monitoring clamav with monit and it seems to constantly stop monitoring,
which
kind of defeats the purpose. clamd has some big memory management issues and
also seems to just die frequently, so I'm trying to hold things together with
monit
until they fix clamd.
I saw an old thread kind of on this subject (among other things), but there
didn't
seem to be an answer to my question there, so I'm resurrecting it.
Please CC me as I'm not on the list.
Logs show thus:
Jul 28 10:17:30 mail2 monit[24027]: 'clamd' zombie check passed
[status_flag=0000
]
Jul 28 10:17:30 mail2 monit[24027]: 'clamd' loadavg(1min) check passed
[current l
oadavg(1min)=1.5]
Jul 28 10:17:30 mail2 monit[24027]: mem usage of 40.1Successatches resource
limit
[mem usage>40.0%]
Jul 28 10:17:30 mail2 monit[24027]: Resource limit matched notification is
sent t
o address@hidden
Jul 28 10:17:30 mail2 monit[24027]: Trying to restart 'clamd'
Jul 28 10:17:30 mail2 monit[24027]: Monitoring disabled -- service clamd
Jul 28 10:17:30 mail2 monit[24027]: stop: (clamd) /usr/bin/killall
Jul 28 10:17:46 mail2 monit[24027]: failed to stop 'clamd'
Jul 28 10:17:51 mail2 monit[24027]: 'clamd' succeeded connecting to
INET[127.0.0.
1:3310]
Jul 28 10:17:51 mail2 monit[24027]: 'clamd' succeeded testing protocol
[DEFAULT]
at INET[127.0.0.1:3310]
(By the way, notice the third line, where the 'm' in 'matches' seems to be
replaced by
'Success'. This also happens in alert emails.)
After that, there is no further mention of clamd in the logs.
Seems like the key line is "Monitoring disabled -- service clamd". Shouldn't
monitoring be re-enabled at some point? Shouldn't it try again if something
goes wrong? My point in running monit is to make sure that process is running
all of the time, no matter what. Is there some option I'm missing that will
enable that kind of behavior?
My config looks like this:
check process clamd with pidfile /var/run/clamd.pid
start program = "/etc/init.d/clamav start"
stop program = "/etc/init.d/clamav stop"
if failed host 127.0.0.1 port 3310 then restart
if memory is greater than 40% then restart
if loadavg(1min) is greater than 15.0 then restart
alert address@hidden
Thanks in advance.
--
Matt
Systems Administrator
Local Access Communications
360.330.5535
pgpCS2ygSIop1.pgp
Description: signature
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- Monit tries once and stops monitoring?,
Matthew Trent <=