Re: firewalld 100% CPU and unresponsive

2020-05-12 Thread Richard Shaw
On Tue, May 12, 2020 at 12:56 PM Jonathan Billings wrote: > On Tue, May 12, 2020 at 12:32:29PM -0500, Richard Shaw wrote: > > Using ipsets in FirewallD is broken in F32... > > > > Filed: > > https://bugzilla.redhat.com/show_bug.cgi?id=1834853 > > Is this because of the backend change to nftables?

Re: firewalld 100% CPU and unresponsive

2020-05-12 Thread Jonathan Billings
On Tue, May 12, 2020 at 12:32:29PM -0500, Richard Shaw wrote: > Using ipsets in FirewallD is broken in F32... > > Filed: > https://bugzilla.redhat.com/show_bug.cgi?id=1834853 Is this because of the backend change to nftables? Can you change FirewallBackend=iptables in /etc/firewalld/firewalld.co

Re: firewalld 100% CPU and unresponsive

2020-05-12 Thread Richard Shaw
Using ipsets in FirewallD is broken in F32... Filed: https://bugzilla.redhat.com/show_bug.cgi?id=1834853 Thanks, Richard ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora C

firewalld 100% CPU and unresponsive

2020-05-12 Thread Richard Shaw
I don't know if this has been a problem the whole time after upgrade but I noticed while checking system load for a different reason that filrewalld is using 100% of one core. It is not responsive to firewall-cmd nor is there anything useful in the journal log: # journalctl --no-hostname -b0 -u f