Re: clamav-milter always detected not running

[Jan-Henrik Haukeland]

1) I know you said you tested the pid but please do this, ps -p $ 
(cat /var/run/clamav/clamav-milter.pid) to make sure the process is  
running. For good measure, also do netstat -alpn to check that the  
clamav unix-socket is there and up.

2) Make sure that the user running monit can read the content of the  
pid file /var/run/clamav/clamav-milter.pid

3) Stop monit and try to run once in debug mode, using: 'monit -Iv  
validate' Do this when you are certain that clamav-milter is running  
(see 1) and monit can read the pid file. You should see debug info  
output to the console. Maybe this will throw some light on the  
problem? Post the output to this list if monit is really trying to  
start clamav again even if 1) show that it is running.


On 18. nov. 2005, at 16.48, afraz wrote:

> Hi,
>
> I subscribed to the list just to ask this question, I hope that's okay
> (neither Google nor the archives could help).
>
> I'm running clamav-milter and want to monitor it with monit. Here  
> is what I'm
> using;
>
> -- BEGIN CONFIG --
> check process clamav-milter with pidfile /var/run/clamav/clamav- 
> milter.pid
>     start program = "/etc/init.d/clamav-milter start"
>     stop  program = "/etc/init.d/clamav-milter stop"
>     if failed unix /var/run/clamav/clamav-milter.ctl then restart
>     group virus
>     depends clamav-milter_init
>     depends clamav-milter_bin
>
> check file clamav-milter_init with path /etc/init.d/clamav-milter
>     group virus
>
> check file clamav-milter_bin with path /usr/sbin/clamav-milter
>     group virus
> -- END CONFIG --
>
> monit tells me that clamav-milter is not running and tries to  
> restart it;
>
> [GMT Nov 18 14:29:19] 'clamav-milter' process is not running
> [GMT Nov 18 14:29:19] 'clamav-milter' trying to restart
> [GMT Nov 18 14:29:19] 'clamav-milter' start: /etc/init.d/clamav-milter
>
> It's unsuccessful in doing so (because it's already running). It  
> seems that
> monit can't see clamav-milter running for some reason.
>
> Obviously I've checked to make sure "/var/run/clamav/clamav- 
> milter.pid" is
> really the correct PID, etc. Any help solving this would be greatly
> appreciated.
>
> All other monitoring (eg. bind9, apache, sendmail, et. al.) is  
> working fine
> (except openntpd which apparently can't be monitored because it  
> doesn't have
> a PID file?).
>
>
> --
> afraz "like a simile" ahmadzadeh

--
Jan-Henrik Haukeland
Mobil +47 97141255