Is sudo journalctl -f
better for seeing AppArmor errors in this case?
From what I can tell, the actual sysstemd feature is working, but then the attempt to redirect output to /dev/null in the subsequent start up script is failing.
:; rpm -q systemd
systemd-239-41.el8_3.1.x86_64
I am on CentOS, not Ubuntu, so no AppArmor…
BTW, sudo jounralctl
shows lot …