I created a bug report at https://bugzilla.redhat.com/show_bug.cgi?id=1983116 for firewalld which stopped with a segfault and hence Fail2ban starting spewing errors like: 2021-07-11 00:02:40,815 fail2ban.utils [2638170]: ERROR 7f73c01d4390 -- exec: ports="$(echo '0-65535' | sed s/:/-/g )"; for p in $(echo $ports | tr ", " " "); do firewall-cmd --add-rich-rule="rule family='ipv4' source address='170.84.126.51' port port='$p' protocol='tcp' reject type='icmp-port-unreachable'"; done 2021-07-11 00:02:40,815 fail2ban.utils [2638170]: ERROR 7f73c01d4390 -- stderr: 'FirewallD is not running' 2021-07-11 00:02:40,816 fail2ban.utils [2638170]: ERROR 7f73c01d4390 -- killed with signal 124 (return code: 252) 2021-07-11 00:02:40,816 fail2ban.actions [2638170]: ERROR Failed to execute ban jail 'pam-generic' action 'firewallcmd-rich-rules' info 'ActionInfo({'ip': '170.84.126.51', 'family': 'inet4', 'fid': <function Actions.ActionInfo.<lambda> at 0x7f73f4322430>, 'raw-ticket': <function Actions.ActionInfo.<lambda> at 0x7f73f4322af0>})': Error banning 170.84.126.51
Is there a graceful way or alert that can be set to handle this? fail2ban-0.11.2-6.fc34.noarch (Fedora 34, kernel 5.12.8-300.fc34.x86_64)
_______________________________________________ Fail2ban-users mailing list Fail2ban-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/fail2ban-users
