Comment 1 for bug 372304

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