Hi,
the service name "fail2ban" is just descriptive name - it doesn't need
to match the process' name. Important is the pidfile content - monit
reads from it PID of the process to be monitored => in your case the
file "/var/run/fail2ban.pid" should contain 20099
Martin
On Jun 16, 2009, at 12:33 PM, [email protected] wrote:
Hi list,
i'm trying to keep fail2ban (http://www.fail2ban.org/) monitored on my
Centos5.2 server.
i've tried using a config like this:
check process fail2ban with pidfile /var/run/fail2ban.pid
start program = "/etc/init.d/fail2ban start"
stop program = "/etc/init.d/fail2ban stop"
if failed unixsocket /var/run/fail2ban/fail2ban.sock then restart
if 5 restarts within 5 cycles then timeout
the problem i'm having is that there is no process called "fail2ban"
to
monitor. the process that fail2ban starts up under looks like this:
ps ax | grep fail2ban
20099 ? Sl 0:31 /usr/bin/python /usr/bin/fail2ban-server -b
-s /var/run/fail2ban/fail2ban.sock -x
Do someone have an idea how on how to make it working?
Thanks
Andrea
--
To unsubscribe:
http://lists.nongnu.org/mailman/listinfo/monit-general
--
To unsubscribe:
http://lists.nongnu.org/mailman/listinfo/monit-general
