You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
bsd-ipfw.conf have
startstatefile = /var/run/fail2ban/ipfw-started-table_<table>
<table> is not expanded here perhaps because of
Values: STRING
instead of
# Values: CMD
for startstatefile causing lots of on-stop errors like that:
2014-05-02 17:46:39,615 fail2ban.server.action[74335]: ERROR [ ! -f /var/run/fail2ban/ipfw-started-table_<table>
] || ( read num < "/var/run/fail2ban/ipfw-started-table_<table>"
ipfw -q delete $num
rm "/var/run/fail2ban/ipfw-started-table_<table>" ) -- stderr: 'cannot open table: No such file or directory\ncann
ot open /var/run/fail2ban/ipfw-started-table_<table>: No such file or directory\nipfw: missing rule specification\n
rm: /var/run/fail2ban/ipfw-started-table_<table>: No such file or directory\n'
The text was updated successfully, but these errors were encountered:
kwirk
added a commit
to kwirk/fail2ban
that referenced
this issue
May 3, 2014
Note: recursive check ignored for "matches", as tags would be escaped,
and hence shouldn't match "<%s>" as "<ip>" would become "\<ip\>". This
therefore maintains advantage of delayed call for {ip,jail,}matches.
Fixesfail2bangh-713
bsd-ipfw.conf have
startstatefile = /var/run/fail2ban/ipfw-started-table_<table>
<table> is not expanded here perhaps because of
Values: STRING
# Values: CMD
for startstatefile causing lots of on-stop errors like that:2014-05-02 17:46:39,615 fail2ban.server.action[74335]: ERROR [ ! -f /var/run/fail2ban/ipfw-started-table_<table> ] || ( read num < "/var/run/fail2ban/ipfw-started-table_<table>" ipfw -q delete $num rm "/var/run/fail2ban/ipfw-started-table_<table>" ) -- stderr: 'cannot open table: No such file or directory\ncann ot open /var/run/fail2ban/ipfw-started-table_<table>: No such file or directory\nipfw: missing rule specification\n rm: /var/run/fail2ban/ipfw-started-table_<table>: No such file or directory\n'
The text was updated successfully, but these errors were encountered: