Fail2Ban has some incompatibilities with Python 2.6. So, it should use Python 2.5
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Gentoo Linux |
Fix Released
|
Medium
|
|||
fail2ban (Fedora) |
Fix Released
|
High
|
|||
fail2ban (Ubuntu) |
Fix Released
|
Medium
|
Chris Coulson | ||
fail2ban (openSUSE) |
Fix Released
|
Medium
|
Bug Description
Binary package hint: fail2ban
After upgrading all my Ubuntu servers from Intrepid to Jaunty, Fail2Ban log files begun showing strange messages:
2009-05-05 03:34:26,742 fail2ban.server : ERROR Unexpected communication error
2009-05-05 03:34:26,743 fail2ban.server : ERROR Unexpected communication error
2009-05-05 03:34:26,745 fail2ban.server : ERROR Unexpected communication error
2009-05-05 03:34:26,762 fail2ban.server : ERROR Unexpected communication error
2009-05-05 03:34:26,764 fail2ban.server : ERROR Unexpected communication error
2009-05-05 03:34:26,765 fail2ban.server : ERROR Unexpected communication error
2009-05-05 03:34:26,767 fail2ban.server : ERROR Unexpected communication error
2009-05-05 03:34:26,768 fail2ban.server : ERROR Unexpected communication error
2009-05-05 03:34:26,770 fail2ban.server : ERROR Unexpected communication error
2009-05-05 03:34:26,771 fail2ban.jail : INFO Creating new jail 'sshd-ddos'
2009-05-05 03:34:26,771 fail2ban.jail : INFO Jail 'sshd-ddos' uses poller
2009-05-05 03:34:26,772 fail2ban.server : ERROR Unexpected communication error
2009-05-05 03:34:26,773 fail2ban.filter : INFO Added logfile = /var/log/auth.log
2009-05-05 03:34:26,775 fail2ban.server : ERROR Unexpected communication error
2009-05-05 03:34:26,775 fail2ban.filter : INFO Set maxRetry = 5
2009-05-05 03:34:26,776 fail2ban.server : ERROR Unexpected communication error
2009-05-05 03:34:26,811 fail2ban.server : ERROR Unexpected communication error
2009-05-05 03:34:26,822 fail2ban.server : ERROR Unexpected communication error
2009-05-05 03:34:26,823 fail2ban.filter : INFO Set findtime = 300
2009-05-05 03:34:26,826 fail2ban.server : ERROR Unexpected communication error
2009-05-05 03:34:26,828 fail2ban.actions: INFO Set banTime = 86400
2009-05-05 03:34:26,831 fail2ban.server : ERROR Unexpected communication error
2009-05-05 03:34:26,834 fail2ban.server : ERROR Unexpected communication error
2009-05-05 03:34:26,848 fail2ban.server : ERROR Unexpected communication error
2009-05-05 03:34:26,849 fail2ban.server : ERROR Unexpected communication error
2009-05-05 03:34:26,851 fail2ban.server : ERROR Unexpected communication error
2009-05-05 03:34:26,854 fail2ban.server : ERROR Unexpected communication error
2009-05-05 03:34:26,857 fail2ban.server : ERROR Unexpected communication error
2009-05-05 03:34:26,860 fail2ban.server : ERROR Unexpected communication error
2009-05-05 03:34:26,874 fail2ban.server : ERROR Unexpected communication error
2009-05-05 03:34:26,876 fail2ban.server : ERROR Unexpected communication error
2009-05-05 03:34:26,877 fail2ban.server : ERROR Unexpected communication error
I didn't investigated so much... Instead, I looked for a solution at Google. I found it at:
http://
After installing Python 2.5 and applying the proposed fix, those strange messages disappear.
So... Could Fail2Ban package in Ubuntu Jaunty have /usr/bin/python2.5 as interpreter? Could Fail2Ban package request installing Python 2.5 also?
Related branches
Changed in fail2ban (Fedora): | |
status: | Unknown → In Progress |
Changed in fail2ban (openSUSE): | |
status: | Unknown → Confirmed |
Changed in gentoo: | |
status: | Unknown → Confirmed |
Changed in fail2ban (Fedora): | |
status: | In Progress → Fix Released |
Changed in fail2ban (openSUSE): | |
status: | Confirmed → Fix Released |
Changed in gentoo: | |
status: | Confirmed → Fix Released |
Changed in gentoo: | |
importance: | Unknown → Medium |
Changed in fail2ban (openSUSE): | |
importance: | Unknown → Medium |
Changed in fail2ban (Fedora): | |
importance: | Unknown → High |
Hi there - new around here, so I don't know if "me too"-type comments are appreciated or not.
I upgraded from Intrepid->Jaunty this weekend and experienced the exact same issue as described above, including the "Unexpected communication error"; there was nothing in the logfile to indicate that fail2ban was actually functioning. No one had been banned.
Switched the first line as suggested in the link, restarted it, and no more "Unexpected Communication Errors". Furthermore, my logfile indicates that there has already been multiple bans, as expected.
cheers,
arm