Hi!
As it is shown in the fail2ban logs:
2015-11-16 07:58:26,043 fail2ban.action [3074]: ERROR iptables -D
INPUT -p tcp -m multiport --dports ssh -j f2b-sshd
iptables -F f2b-sshd
iptables -X f2b-sshd -- stdout: b''
2015-11-16 07:58:26,044 fail2ban.action [3074]: ERROR iptables
In my opinion, your issue is not a PATH issue, but simply that the
fail2ban chain does not exist anymore after the firewall has been reset.
Restarting fail2ban does recreate the chain, which is why it works
thereafter. I see two solutions:
- either you add the creation of the fail2ban chain to y
Hi!
Yes, I understand this is happening because of the flushing of rules, but
it seems that fail2ban has a built-in recovery mechanism to handle this
situation.
The recovery mechanism is to readd the iptables rules (see log from my
original mail).
The issue is that the recovery mechanism is not
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi,
The directory /var/run/fail2ban is on tmpfs, and the init script used
on ubuntu (typically added by the packager) is supposed to create the
directory when you start the daemon.
If you want to install f2b by hand (which apparently you did, since
Hi!
I am using fail2ban and very happy with that. But I have one use case where
behavior is not optimal.
I store my iptables rules in a file an occasionally run iptables-restore if
I have modified the rule set.
After I have done this, I see the following errors in fail2ban-log:
2015-11-16 07:58
Hi
Just to let you know I set up a virtual machine with Ubuntu 14.04 and Fail2ban
0.9.3 and Fail2ban started after instalation but after a restart of ubuntu I
had the same issues as in my previous post.
allanit wrote .. Hi My Server is ubuntu 14.04, and
Fail2ban is 0.9.3 which I recent
