firewalld failure after system update CentOS 8
After a recent system update on a CentOS 8 Stream system, firewalld will no longer start.
From what I can gather searching online, it has something to do with the default Linode kernel.
Can anyone shed some light on this?
Systemd status output:
firewalld.service - firewalld - dynamic firewall daemon
Loaded: loaded (/usr/lib/systemd/system/firewalld.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Tue 2022-11-08 09:56:42 EST; 2h 37min ago
Docs: man:firewalld(1)
Process: 1277 ExecStart=/usr/sbin/firewalld --nofork --nopid $FIREWALLD_ARGS (code=exited, status=3)
Main PID: 1277 (code=exited, status=3)
Nov 08 09:56:41 bunyan-bu systemd[1]: Starting firewalld - dynamic firewall daemon…
Nov 08 09:56:41 bunyan-bu systemd[1]: Started firewalld - dynamic firewall daemon.
Nov 08 09:56:42 bunyan-bu systemd[1]: firewalld.service: Main process exited, code=exited, status=3/NOTIMPLEMENTED
Nov 08 09:56:42 bunyan-bu systemd[1]: firewalld.service: Failed with result 'exit-code'.
1 Reply
tlambert
Linode Staff
If you've read this is related to the kernel, I suggest changing the kernel your instance is currently using.
I tested this on a fresh CentOS Stream 8 instance using both the GRUB2 and latest 64-bit Linode kernels. Each time, firewalld was running without any issues:
systemctl status firewalld
● firewalld.service - firewalld - dynamic firewall daemon
Loaded: loaded (/usr/lib/systemd/system/firewalld.service; enabled; vendor preset: enabled)
Active: active (running) since Fri 2023-03-31 15:08:12 UTC; 6min ago
Docs: man:firewalld(1)
Main PID: 473 (firewalld)
Tasks: 2 (limit: 6047)
Memory: 41.9M
CGroup: /system.slice/firewalld.service
└─473 /usr/libexec/platform-python -s /usr/sbin/firewalld --nofork --nopid
Mar 31 15:08:11 localhost systemd[1]: Starting firewalld - dynamic firewall daemon...
Mar 31 15:08:12 localhost systemd[1]: Started firewalld - dynamic firewall daemon.