> 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)
Oh, sorry about that. I've attached a tarball with the complete directory structure to this mail. I also attached the new fail2ban.log from after I tested the suggested actions below (still empty, though). > So -- fail2ban-server is crashing. Could you run it in foreground mode ? > (-f) Jotunheim:~# fail2ban-server -f 2008-08-27 19:58:00,666 fail2ban.server : INFO Starting Fail2ban v0.8.3 And then from another shell: Jotunheim:~# ps -A | grep fail2ban 10399 pts/0 00:00:01 fail2ban-server Jotunheim:~# fail2ban-client reload ERROR Could not find server Jotunheim:~# Back in the first shell: Jotunheim:~# fail2ban-server -f 2008-08-27 19:58:00,666 fail2ban.server : INFO Starting Fail2ban v0.8.3 error: uncaptured python exception, closing channel <server.asyncserver.AsyncServer listening '/var/run/fail2ban/fail2ban.sock' at 0x1d8b0c> (<type 'exceptions.SystemError'>:Negative size passed to PyString_FromStringAndSize [/usr/lib/python2.5/asyncore.py|readwrite|93] [/usr/lib/python2.5/asyncore.py|handle_read_event|384] [/usr/share/fail2ban/server/asyncserver.py|handle_accept|97] [/usr/lib/python2.5/asyncore.py|accept|321] [/usr/lib/python2.5/socket.py| accept|172]) 2008-08-27 20:00:21,530 fail2ban.server : INFO Exiting Fail2ban Jotunheim:~# > 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. Jotunheim:~# ipython -pdb /usr/bin/fail2ban-server -- -f -x 2008-08-27 20:11:52,032 fail2ban.server : INFO Starting Fail2ban v0.8.3 At second shell: Jotunheim:~# fail2ban-client -v reload INFO Using socket file /var/run/fail2ban/fail2ban.sock ERROR Could not find server Jotunheim:~# Back at first shell: Jotunheim:~# ipython -pdb /usr/bin/fail2ban-server -- -f -x 2008-08-27 20:11:52,032 fail2ban.server : INFO Starting Fail2ban v0.8.3 error: uncaptured python exception, closing channel <server.asyncserver.AsyncServer listening '/var/run/fail2ban/fail2ban.sock' at 0x47644c> (<type 'exceptions.SystemError'>:Negative size passed to PyString_FromStringAndSize [/usr/lib/python2.5/asyncore.py|readwrite|93] [/usr/lib/python2.5/asyncore.py|handle_read_event|384] [/usr/share/fail2ban/server/asyncserver.py|handle_accept|97] [/usr/lib/python2.5/asyncore.py|accept|321] [/usr/lib/python2.5/socket.py| accept|172]) 2008-08-27 20:12:59,440 fail2ban.server : INFO Exiting Fail2ban Python 2.5.2 (r252:60911, Aug 8 2008, 12:53:08) Type "copyright", "credits" or "license" for more information. IPython 0.8.4 -- An enhanced Interactive Python. ? -> Introduction and overview of IPython's features. %quickref -> Quick reference. help -> Python's own help system. object? -> Details about 'object'. ?object also works, ?? prints more. In [1]: quit() Do you really want to exit ([y]/n)? Jotunheim:~# > 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 Ok, this is a little too much for my current knowledge of ipython. I just installed it. I hope the above messages will suffice. If not, I'll need guidence. /Stefan
fail2ban.tar.gz
Description: application/tgz
