[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [monit] using monit with fail2ban
From: |
Charles Mangin |
Subject: |
Re: [monit] using monit with fail2ban |
Date: |
Mon, 8 Sep 2008 10:27:04 -0400 |
perhaps i failed to quote the pertinent line in my logs:
Sep 7 12:30:25 foo monit[24122]: 'fail2ban' process is not running
the problem is not that monit can't start fil2ban with /etc/init.d/
fail2ban start - it stops and starts just fine - the problem seems to
be that monit can't detect that a fail2ban process is running, and
keeps trying to restart it. my thought being that it's because the
running process is listed as:
20099 ? Sl 0:31 /usr/bin/python /usr/bin/fail2ban-server -b
-s /var/run/fail2ban/fail2ban.sock -x
charles mangin | Alpha Geek and Chief Mental Hygienist
address@hidden
http://mentalhygiene.com
On Sep 8, 2008, at 5:03 AM, Nick Upson wrote:
I suggest that the problem is related to the highly restricted path
that monit uses, monit itself appears to be working correctly.
suggest you go through /etc/init.d/fail2ban and make sure all paths
are absolute paths that don't rely upon external variables