|
From: | Martin Pala |
Subject: | Re: clamav-milter's pid |
Date: | Sat, 08 Apr 2006 01:58:31 +0200 |
User-agent: | Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.12) Gecko/20060205 Debian/1.7.12-1.1 |
Mike Pepe wrote:
Hmm - you can try to run monit in debug mode as well: monit -vISure- sorry, this is rather long, but I'm not sure what exactly is being looked for:
The cause of the problem may be in pidfile ... in your previous mail you compared the contents of /var/run/clamav/clamav-milter.pid.fixed file with the running process:
--8<-- # cat /var/run/clamav/clamav-milter.pid.fixed 12781 # ps -ef | grep clamav-milterclamilt 12781 1 0 16:19 ? 00:00:00 /usr/sbin/clamav-milter --quiet --external --dont-wait --force-scan --dont-log-clean --server=localhost --pidfile=/var/run/clamav/clamav-milter.pid local:/var/run/clamav/clamav-milter.sock
--8<--however, monit was configured to check the pid which is stored in /var/run/clamav/clamav-milter.pid (containg the incompatible format):
--8<-- Process Name = clamav-milter Group = milter Pid file = /var/run/clamav/clamav-milter.pid ... --8<-- Martin
[Prev in Thread] | Current Thread | [Next in Thread] |