Firewall kicks on and off after update


(Jeremy Lizzotte) #1

I have an issue with the firewall where it keeps going on and off every 15 minutes. It appears to be caused by Fail2ban and its because iptables is locked by another program. It gives me this message:

Another app is currently holding the xtables lock. Perhaps you want to use the -w option?

I have attached the firewall log. Its up to date with freepbx 15 and the newest certman and firewall modules that were edged

Redirecting to /bin/systemctl restart iptables.service
Redirecting to /bin/systemctl restart ip6tables.service
Redirecting to /bin/systemctl restart iptables.service
Redirecting to /bin/systemctl restart ip6tables.service
Redirecting to /bin/systemctl restart iptables.service
Redirecting to /bin/systemctl restart ip6tables.service
Redirecting to /bin/systemctl restart iptables.service
Redirecting to /bin/systemctl restart ip6tables.service
Redirecting to /bin/systemctl restart iptables.service
Redirecting to /bin/systemctl restart ip6tables.service
Redirecting to /bin/systemctl restart iptables.service
Redirecting to /bin/systemctl restart ip6tables.service
Redirecting to /bin/systemctl restart iptables.service
Redirecting to /bin/systemctl restart ip6tables.service
Redirecting to /bin/systemctl restart iptables.service
Redirecting to /bin/systemctl restart ip6tables.service
Redirecting to /bin/systemctl restart iptables.service
Redirecting to /bin/systemctl restart ip6tables.service
Redirecting to /bin/systemctl restart iptables.service
Redirecting to /bin/systemctl restart ip6tables.service
Redirecting to /bin/systemctl restart iptables.service
Redirecting to /bin/systemctl restart ip6tables.service
Redirecting to /bin/systemctl restart iptables.service
Redirecting to /bin/systemctl restart ip6tables.service
Redirecting to /bin/systemctl restart iptables.service
Redirecting to /bin/systemctl restart ip6tables.service
Redirecting to /bin/systemctl restart iptables.service
Redirecting to /bin/systemctl restart ip6tables.service
Redirecting to /bin/systemctl restart iptables.service
Redirecting to /bin/systemctl restart ip6tables.service
Redirecting to /bin/systemctl restart iptables.service
Redirecting to /bin/systemctl restart ip6tables.service
Redirecting to /bin/systemctl restart iptables.service
Redirecting to /bin/systemctl restart ip6tables.service
Redirecting to /bin/systemctl restart iptables.service
Redirecting to /bin/systemctl restart ip6tables.service
Redirecting to /bin/systemctl restart iptables.service
Redirecting to /bin/systemctl restart ip6tables.service
Redirecting to /bin/systemctl restart iptables.service
Redirecting to /bin/systemctl restart ip6tables.service
Redirecting to /bin/systemctl restart iptables.service
Redirecting to /bin/systemctl restart ip6tables.service
Redirecting to /bin/systemctl restart iptables.service
Redirecting to /bin/systemctl restart ip6tables.service
Redirecting to /bin/systemctl restart iptables.service
Redirecting to /bin/systemctl restart ip6tables.service
Redirecting to /bin/systemctl restart iptables.service
Redirecting to /bin/systemctl restart ip6tables.service
Redirecting to /bin/systemctl restart iptables.service
Redirecting to /bin/systemctl restart ip6tables.service
Redirecting to /bin/systemctl restart iptables.service
Redirecting to /bin/systemctl restart ip6tables.service
Starting firewall.
1592309291: Wall: 'Firewall service now starting.

’ returned 0


(Jeremy Lizzotte) #2

Nevermind this was an ongoing issue for the last couple weeks, turns out the firewall has been updated to .16 (as of this issue, the edge was .12) so disregard this.


(system) closed #3

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.