Hi Nick -- Unfortunately I can't do it on a machine when it gets frozen due to the issue:
# cat /etc/systemd/system.conf.d/debug.conf [Manager] LogLevel=debug # systemctl daemon-reexec # systemd-analyze get-log-level Failed to get log level of org.freedesktop.systemd1: Connection timed out Extract from log files: Oct 08 01:30:37 <computer_name> systemd-journald[345]: Failed to send WATCHDOG=1 notification message: Transport endpoint is not connected Oct 08 01:31:04 <computer_name> dbus-daemon[1008]: [system] Failed to activate service 'org.freedesktop.systemd1': timed out (service_start_timeout=25000ms) Oct 08 01:31:30 <computer_name> dbus-daemon[1008]: [system] Failed to activate service 'org.freedesktop.systemd1': timed out (service_start_timeout=25000ms) Oct 08 01:31:30 <computer_name> systemd-journald[345]: Failed to send WATCHDOG=1 notification message: Transport endpoint is not connected Oct 08 01:32:57 <computer_name> systemd-journald[345]: Failed to send WATCHDOG=1 notification message: Transport endpoint is not connected Oct 08 01:34:47 <computer_name> systemd-journald[345]: Failed to send WATCHDOG=1 notification message: Transport endpoint is not connected Oct 08 01:35:01 <computer_name> CRON[921614]: pam_unix(cron:session): session opened for user root(uid=0) by root(uid=0) Oct 08 01:35:01 <computer_name> CRON[921615]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1) Oct 08 01:35:01 <computer_name> CRON[921614]: pam_unix(cron:session): session closed for user root Oct 08 01:36:37 <computer_name> systemd-journald[345]: Failed to send WATCHDOG=1 notification message: Transport endpoint is not connected Oct 08 01:37:47 <computer_name> systemd-journald[345]: Failed to send WATCHDOG=1 notification message: Transport endpoint is not connected Oct 08 01:39:37 <computer_name> systemd-journald[345]: Failed to send WATCHDOG=1 notification message: Transport endpoint is not connected Oct 08 01:40:47 <computer_name> systemd-journald[345]: Failed to send WATCHDOG=1 notification message: Transport endpoint is not connected Oct 08 01:42:37 <computer_name> systemd-journald[345]: Failed to send WATCHDOG=1 notification message: Transport endpoint is not connected Oct 08 01:43:47 <computer_name> systemd-journald[345]: Failed to send WATCHDOG=1 notification message: Transport endpoint is not connected Oct 08 01:43:58 <computer_name> Tor[2053]: Tor has been idle for 3600 seconds; assuming established circuits no longer work. Oct 08 01:44:11 <computer_name> dbus-daemon[1008]: [system] Failed to activate service 'org.freedesktop.systemd1': timed out (service_start_timeout=25000ms) Oct 08 01:44:36 <computer_name> dbus-daemon[1008]: [system] Failed to activate service 'org.freedesktop.systemd1': timed out (service_start_timeout=25000ms) Oct 08 01:45:01 <computer_name> CRON[924093]: pam_unix(cron:session): session opened for user root(uid=0) by root(uid=0) Oct 08 01:45:01 <computer_name> systemd-journald[345]: Failed to send WATCHDOG=1 notification message: Transport endpoint is not connected Oct 08 01:45:01 <computer_name> CRON[924094]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1) Oct 08 01:45:01 <computer_name> CRON[924093]: pam_unix(cron:session): session closed for user root Oct 08 01:46:47 <computer_name> systemd-journald[345]: Failed to send WATCHDOG=1 notification message: Transport endpoint is not connected Oct 08 01:48:37 <computer_name> systemd-journald[345]: Failed to send WATCHDOG=1 notification message: Transport endpoint is not connected Oct 08 01:49:47 <computer_name> systemd-journald[345]: Failed to send WATCHDOG=1 notification message: Transport endpoint is not connected and so on. I can't reboot the PC remotely -- need to do hard reboot tomorrow. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/2126437 Title: system] Failed to activate service 'org.freedesktop.systemd1': timed out Status in systemd package in Ubuntu: Incomplete Bug description: We have the following issue affecting a significant portion of our machines running the latest stable Ubuntu 24.04.3 LTS. This happens from time to time. Typical messages: "Reload daemon failed: Failed to activate service 'org.freedesktop.systemd1': timed out (service_start_timeout=25000ms)" or "dbus-daemon[948]: [system] Failed to activate service .. " 'org.freedesktop.systemd1': timed out" # busctl | grep org.freedesktop.systemd1 command shows it is as 'activatable' The error indicates a system deadlock, most commonly between systemd and the DBus service, preventing system services from starting. The only solution is to hard reboot the system. AFAIK, here systemd is trying to talk to D-Bus (or a systemd D-Bus interface) and not getting a timely reply. dbus is just reporting the timeout — not the root cause. systemd is the provider of org.freedesktop.systemd1, and if it’s not answering D-Bus in time, the deadlock is on its side. Google suggests updating the operating system and systemd to a newer, however we already run the latest stable version of systemd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2126437/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
