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 firewalld -- Logs begin at Thu 2020-05-07 14:07:43 CDT, end at Tue 2020-05-12 07:15:25 CDT. -- May 12 06:47:20 systemd[1]: Starting firewalld - dynamic firewall daemon... May 12 06:47:21 systemd[1]: Started firewalld - dynamic firewall daemon. May 12 07:01:26 systemd[1]: Stopping firewalld - dynamic firewall daemon... May 12 07:01:26 systemd[1]: firewalld.service: Succeeded. May 12 07:01:26 systemd[1]: Stopped firewalld - dynamic firewall daemon. May 12 07:01:26 systemd[1]: firewalld.service: Consumed 14min 1.157s CPU time. May 12 07:02:03 systemd[1]: Starting firewalld - dynamic firewall daemon... May 12 07:02:03 systemd[1]: Started firewalld - dynamic firewall daemon. I tried downgrading but it's still the version that ships with f32 so no dice... Anyone else seeing this? Thanks, Richard
_______________________________________________ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
