I was getting the same behavior as the reporter of this bug (Mike) and when I finally found this page and realized that this is an bug of fail2ban itself. My system is Ubuntu 10.04 with 0.8.4-1ubuntu1 version of the fail2ban package for Ubuntu.
I just added the time.sleep(0.1) line to /usr/bin/fail2ban-client and now it works but with a slower response time.
Please change the designation of this report back from "Invalid" to "New".
Please add the time.sleep(0) to the package maintainer's version of /usr/bin/fail2ban-client or another fix that corrects the behavior of this * bug *.
I was getting the same behavior as the reporter of this bug (Mike) and when I finally found this page and realized that this is an bug of fail2ban itself. My system is Ubuntu 10.04 with 0.8.4-1ubuntu1 version of the fail2ban package for Ubuntu.
I just added the time.sleep(0.1) line to /usr/bin/ fail2ban- client and now it works but with a slower response time.
Please change the designation of this report back from "Invalid" to "New".
Please add the time.sleep(0) to the package maintainer's version of /usr/bin/ fail2ban- client or another fix that corrects the behavior of this * bug *.
Thank you