Of course you have it installed. The url mentioned in my previous post contains a patch to fix it, what you need to do is apply it.
Steps to fix it:
1) Backup file first which will be patched, remove compiled python binary file.
# cp /usr/share/fail2ban/server/action.py /usr/share/fail2ban/server/action.py.bak
# rm -f /usr/share/fail2ban/server/action.py.pyc /usr/share/fail2ban/server/action.pyo
2) Upload attached patch to your server, verify this patch with command 'patch --dry-run -p0':
# cd /root
# patch --dry-run -p0 < action.patch
patching file /usr/share/fail2ban/server/action.py
3) If you got the SAME output message, it's now safe to apply it immediately with command 'patch -p0':
# cd /root
# patch -p0 < action.patch
4) Restart fail2ban service and keep monitoring its log file to see whether the same issue happened again or not.
If it doesn't work for you after patch applied, please reverse this patch with below steps, then restart Fail2ban service:
# rm -f /usr/share/fail2ban/server/action.py.pyc /usr/share/fail2ban/server/action.pyo
# cp /usr/share/fail2ban/server/action.py.bak /usr/share/fail2ban/server/action.py
Post's attachmentsaction.patch 1.52 kb, 6 downloads since 2012-03-03
You don't have the permssions to download the attachments of this post.