sorry, I gave a wrong Python version.
The correct Python version is 2.6.7
---------- Forwarded Message ----------
Subject: no more banning after upgrade
Date: Saturday 25 June 2011, 12:57:03
From: "tom@..." <tom@...>
I had fail2ban running greatly for at least a year. But after the recent
upgrade to 0.84 I got stock with getting it to run again. The wiki pages did
not help so far so I hope to get a hint on the list.
Fail2ban 0.8.4 with Python 2.7 on FreeBSD 8.0
SSH auth loglines to check (example):
Jun 25 04:06:19 jan sshd: Did not receive identification string from
After the upgrade, the formerly nice working ssh filters did not work any
more. I triple checked all conf files with not probs found there. Also,
fail2ban.log doesn't show anything looking unusual - not on loglevel 3 or
The filters were written like the following example:
^%(__prefix_line)sDid not receive identification string from <HOST>$
Fail2ban started with these filters but did not ban anything more
(threw no errors either). From a test with fail2ban-regex from the command
line I learned, that the filters did not work any longer (none of the
failure log lines were recognized).
I then changed the filters that way:
sshd(?:\[\d+\])?: Did not receive identification string from <HOST>$
The command line test with fail2ban-regex then was successful.
Fail2ban again started up without complaining about anything.
Nonetheless, still no single IP was banned.
Though I did not change anything regarding time zones, time settings or
anything similar, I also restarted the syslog daemon. With no effect on the
So I'm out of any further ideas on what to check to get Fail2ban banning
Any hints from your side ?
Get latest updates about Open Source Projects, Conferences and News.