Re: Troubleshooting timedatectl and hostnamectl failed to activate service: timed out

2023-12-14 Thread Sean Caron
23 at 12:02 PM Sean Caron wrote: > 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, >

Re: Troubleshooting timedatectl and hostnamectl failed to activate service: timed out

2023-12-14 Thread Sean Caron
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 Mant

Re: Troubleshooting timedatectl and hostnamectl failed to activate service: timed out

2023-12-14 Thread Sean Caron
ther it fails to start (missing libraries? > Apparmor?) or dbus-daemon fails to contact systemd (pid1 crashed?). > > On Wed, Dec 13, 2023, 19:45 Sean Caron wrote: > >> Hi everyone, >> >> I'm on Ubuntu 20.04 LTS, kernel version 5.4.0-163-generic, systemd 245 >&g

Troubleshooting timedatectl and hostnamectl failed to activate service: timed out

2023-12-13 Thread Sean Caron
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