Mike Pepe wrote:
Hmm - you can try to run monit in debug mode as well:
monit -vI
Sure- 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-milter
clamilt 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
--
To unsubscribe:
http://lists.nongnu.org/mailman/listinfo/monit-general
