Web lists-archives.com

systemd errors




I'm seeing the following errors in my daemon.log:

Jan  5 05:05:30 debian systemd[1]: File
/lib/systemd/system/systemd-journald.service:35 configures an IP
firewall (IPAddressDeny=any), but the local system does not support
BPF/cgroup based firewalling.
Jan  5 05:05:30 debian systemd[1]: Proceeding WITHOUT firewalling in effect!
Jan  5 05:05:30 debian systemd[1]: File
/lib/systemd/system/systemd-logind.service:37 configures an IP
firewall (IPAddressDeny=any), but the local system does not support
BPF/cgroup based firewalling.
Jan  5 05:05:30 debian systemd[1]: Proceeding WITHOUT firewalling in effect!
Jan  5 05:05:30 debian systemd[1]: File
/lib/systemd/system/systemd-udevd.service:34 configures an IP firewall
(IPAddressDeny=any), but the local system does not support BPF/cgroup
based firewalling.
Jan  5 05:05:30 debian systemd[1]: Proceeding WITHOUT firewalling in effect!
Jan  5 05:05:30 debian systemd[1]:
/lib/systemd/system/user@.service:21: Failed to parse boolean value,
ignoring: pids cpu
Jan  5 05:05:30 debian systemd[1]:
/lib/systemd/system/user@.service:21: Failed to parse boolean value,
ignoring: pids cpu
Jan  5 05:05:31 debian systemd[1]: Reloading.
Jan  5 05:05:31 debian systemd[1]: File
/lib/systemd/system/systemd-journald.service:35 configures an IP
firewall (IPAddressDeny=any), but the local system does not support
BPF/cgroup based firewalling.
Jan  5 05:05:31 debian systemd[1]: Proceeding WITHOUT firewalling in effect!
Jan  5 05:05:31 debian systemd[1]: File
/lib/systemd/system/systemd-logind.service:37 configures an IP
firewall (IPAddressDeny=any), but the local system does not support
BPF/cgroup based firewalling.
Jan  5 05:05:31 debian systemd[1]: Proceeding WITHOUT firewalling in effect!
Jan  5 05:05:31 debian systemd[1]: File
/lib/systemd/system/systemd-udevd.service:34 configures an IP firewall
(IPAddressDeny=any), but the local system does not support BPF/cgroup
based firewalling.
Jan  5 05:05:31 debian systemd[1]: Proceeding WITHOUT firewalling in effect!
Jan  5 05:05:31 debian systemd[1]:
/lib/systemd/system/user@.service:21: Failed to parse boolean value,
ignoring: pids cpu
Jan  5 05:05:31 debian systemd[1]:
/lib/systemd/system/user@.service:21: Failed to parse boolean value,
ignoring: pids cpu
Jan  5 05:05:31 debian systemd[1]: Reloading.
Jan  5 05:05:31 debian systemd[1]: File
/lib/systemd/system/systemd-journald.service:35 configures an IP
firewall (IPAddressDeny=any), but the local system does not support
BPF/cgroup based firewalling.
Jan  5 05:05:31 debian systemd[1]: Proceeding WITHOUT firewalling in effect!
Jan  5 05:05:31 debian systemd[1]: File
/lib/systemd/system/systemd-logind.service:37 configures an IP
firewall (IPAddressDeny=any), but the local system does not support
BPF/cgroup based firewalling.
Jan  5 05:05:31 debian systemd[1]: Proceeding WITHOUT firewalling in effect!
Jan  5 05:05:31 debian systemd[1]: File
/lib/systemd/system/systemd-udevd.service:34 configures an IP firewall
(IPAddressDeny=any), but the local system does not support BPF/cgroup
based firewalling.
Jan  5 05:05:31 debian systemd[1]: Proceeding WITHOUT firewalling in effect!
Jan  5 05:05:31 debian systemd[1]:
/lib/systemd/system/user@.service:21: Failed to parse boolean value,
ignoring: pids cpu
Jan  5 05:05:31 debian systemd[1]:
/lib/systemd/system/user@.service:21: Failed to parse boolean value,
ignoring: pids cpu
Jan  5 05:05:31 debian systemd[1]: Reloading.
Jan  5 05:05:31 debian systemd[1]: File
/lib/systemd/system/systemd-journald.service:35 configures an IP
firewall (IPAddressDeny=any), but the local system does not support
BPF/cgroup based firewalling.
Jan  5 05:05:31 debian systemd[1]: Proceeding WITHOUT firewalling in effect!
Jan  5 05:05:31 debian systemd[1]: File
/lib/systemd/system/systemd-logind.service:37 configures an IP
firewall (IPAddressDeny=any), but the local system does not support
BPF/cgroup based firewalling.
Jan  5 05:05:31 debian systemd[1]: Proceeding WITHOUT firewalling in effect!
Jan  5 05:05:31 debian systemd[1]: File
/lib/systemd/system/systemd-udevd.service:34 configures an IP firewall
(IPAddressDeny=any), but the local system does not support BPF/cgroup
based firewalling.
Jan  5 05:05:31 debian systemd[1]: Proceeding WITHOUT firewalling in effect!
Jan  5 05:05:31 debian systemd[1]:
/lib/systemd/system/user@.service:21: Failed to parse boolean value,
ignoring: pids cpu
Jan  5 05:05:31 debian systemd[1]:
/lib/systemd/system/user@.service:21: Failed to parse boolean value,
ignoring: pids cpu
Jan  5 05:05:31 debian systemd[1]: Reexecuting.
Jan  5 05:05:31 debian systemd[1]: systemd 236 running in system mode.
(+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP
+LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS
+KMOD -IDN2 +IDN default-hierarchy=hybrid)
Jan  5 05:05:31 debian systemd[1]: Detected virtualization kvm.
Jan  5 05:05:31 debian systemd[1]: Detected architecture x86-64.
Jan  5 05:05:31 debian systemd[1]: File
/lib/systemd/system/systemd-journald.service:35 configures an IP
firewall (IPAddressDeny=any), but the local system does not support
BPF/cgroup based firewalling.
Jan  5 05:05:31 debian systemd[1]: Proceeding WITHOUT firewalling in
effect! (This warning is only shown for the first loaded unit using IP
firewalling.)
Jan  5 05:05:32 debian systemd[1]: Stopped Flush Journal to Persistent Storage.
Jan  5 05:05:32 debian systemd[1]: Stopping Flush Journal to
Persistent Storage...
Jan  5 05:05:32 debian systemd[1]: Starting Flush Journal to
Persistent Storage...
Jan  5 05:05:32 debian systemd[1]: Started Flush Journal to Persistent Storage.
Jan  5 05:05:33 debian systemd[1]: Reloading.
Jan  5 05:05:33 debian systemd[1]: Reloading.
Jan  5 05:05:33 debian systemd[1]: Reloading.
Jan  5 05:05:33 debian systemd[1]: Reloading.

I'm running debian-testing, and I'm running a Linode kernel.

Some searches say to enable CONFIG_BPF_SYSCALL in the kernel config,
however, I running a Linode kernel, 4.14.12.  I really do not want to
get into compiling my own kernel.  Is there some easier way to fix
this?

And by the way, I do have a firewall, I'm using ipfilter and I have
confirmed that it continues to work.