"Davide Perini wrote:"
You did not provide any information about what your running this on. If
the host is using firewalld you might need to use this action file,
firewallcmd-new.
>
> When I start fail2ban I can see this error now:
>
> Feb 06 22:10:21 netstar.acme.org fail2ban.actions[850]: NOT
On Fri, 06 Feb 2015, Davide Perini wrote:
> When I start fail2ban I can see this error now:
> Feb 06 22:10:21 netstar.acme.org fail2ban.actions[850]: NOTICE
> [ssh-iptables] Unban xx.xx.xx.xx
> Feb 06 22:10:21 netstar.acme.org fail2ban.action[850]: ERROR iptables -D
> fail2ban-SSH -s xx.xx.xx.
When I start fail2ban I can see this error now:
Feb 06 22:10:21 netstar.acme.org fail2ban.actions[850]: NOTICE
[ssh-iptables] Unban xx.xx.xx.xx
Feb 06 22:10:21 netstar.acme.org fail2ban.action[850]: ERROR iptables -D
fail2ban-SSH -s xx.xx.xx.xx -j -- stdout: ''
Feb 06 22:10:21 netstar.acme.org
Hi,
I'm experiencing some problems after the update to the fail2ban 0.9.1...
Initially I had problem starting fail2ban due to the error described here:
https://github.com/fail2ban/fail2ban/issues/851
than I edited my filtersystemd.py as suggested in that post and I was
able to start fail2ban suc
