It appears that I can fix this by editing the unit file and changing:
ProtectSystem=strict
to:
ProtectSystem=full
I'm not sure why that is but a resolution is good enough for me. Following
up on my own thread in case this helps someone else in the future.
Best,
Sean
On Thu, Dec 14, 2023 at
Sorry, perhaps apparmor is not completely disabled, but I don't think it's
enforcing. I tried shutting it off completely with:
systemctl stop apparmor
And that doesn't seem to have made a difference.
Best,
Sean
On Thu, Dec 14, 2023 at 11:57 AM Sean Caron wrote:
> Hi Mantas,
>
> Thanks for t
Hi Mantas,
Thanks for the suggestions! I took a look and I'm seeing entries like the
following in the logs:
Starting Hostname Service...
systemd-hostnamed.service: Failed to set up mount namespacing:
/run/systemd/unit-root/: Invalid argument
systemd-hostnamed.service: Failed at step NAMESPACE spa
Activation is not client-side, it's handled automatically by dbus-daemon –
which either spawns the service directly or starts it as a systemd service.
In this case, check whether your logs show systemd-hostnamed.service
attempting to start; either it fails to start (missing libraries?
Apparmor?) o
Hi everyone,
I'm on Ubuntu 20.04 LTS, kernel version 5.4.0-163-generic, systemd 245
(245.4-4ubuntu3.22).
I have some systems where I am receiving the following error messages when
people attempt to use timedatectl or hostnamectl:
Failed to query server: Failed to activate service
'org.freedeskt