hard to figure out in all the config files if they are just in a list
(not in original directory structure targzipped for instance) but it
seems that fail2ban.conf/jail.conf wasn't even changed, and only
jail.local has modifications (the way it should be)
So -- fail2ban-server is crashing. Could you run it in foreground mode ?
(-f)
you might get even more information if running within ipython with smth
like
ipython -pdb /usr/bin/fail2ban-server -- -f -x
and then issuing that
fail2ban-client -v reload
hopefully that would trigger visible crash in the server with giving at
least some clue of WTF.
then I guess you could debug it a bit if msg would not be informative
start ipython
pdb on
run /usr/bin/fail2ban-server -f -x
and then ivoke that client command -- theoretically you should get into
the point of failure, so you could reveal stack of calls with bt, etc
On Tue, 26 Aug 2008, Stefan wrote:
> tisdagen den 26 augusti 2008 skrev Yaroslav Halchenko:
> > very interesting -- could we start with loglevel = 4 in fail2ban.conf
> > and send resultant fail2ban.log along with your configuration (full
> > /etc/fail2ban would be the best)
> Ok, you'll find the files attached to this mail. But as I wrote in the bug
> report, loglevel = 4 doesn't make any difference. The logfile is still empty.
> > after you started it manually you can try to do
> > fail2ban-client reload
> > and see if there is any 'effect'
--
Yaroslav Halchenko
Research Assistant, Psychology Department, Rutgers-Newark
Student Ph.D. @ CS Dept. NJIT
Office: (973) 353-5440x263 | FWD: 82823 | Fax: (973) 353-1171
101 Warren Str, Smith Hall, Rm 4-105, Newark NJ 07102
WWW: http://www.linkedin.com/in/yarik
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
