On 3/8/2021 1:51 AM, Nick Howitt wrote:
All your script is showing is that, when shutting down, iptables is
failing to remove a rule for some reason (try running the command
manually). This leaves the rule in place which then means ipset can't
delete the set.
There is nothing here to show why f2b is not starting.
Nick
Well, the set WAS in fact deleted, which is what initially attracted my
attention.
Before posting yesterday, I started the fail2ban server and it did start
up ok. (Not sure why it needed the manual start, except for the logged
sequence I posted.)
My main concern was that after startup it didn't process the log it
watches, and hence there was no ipset recreated for that jail.
However, exactly one hour later it logged "purge database event
occurred" and then processed the log, created the ipset, and has been
working normally since.
All is well today. I will just need to check it for manual restart
whenever csf does one of its automatic updates.
Phil
_______________________________________________
Fail2ban-users mailing list
Fail2ban-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/fail2ban-users