debcrafters-packages team mailing list archive

[doug rady <2126437@xxxxxxxxxxxxxxxxxx>]

We are also seeing this with 24.04.3 LTS (Noble Numbat).
Our ssh logins seem to pause until we see the in /var/log/auth.log:
2025-10-01T17:57:10.136863+00:00 xyzzy systemd-logind[2569]: Failed to start user service 'user@5118.service', ignoring: Connection timed out
2025-10-01T17:57:10.138107+00:00 xyzzy dbus-daemon[2339]: [system] Failed to activate service 'org.freedesktop.systemd1': timed out (service_start_timeout=25000ms)
2025-10-01T17:57:35.162446+00:00 xyzzy systemd-logind[2569]: Failed to start session scope session-474.scope: Connection timed out
2025-10-01T17:57:35.163026+00:00 xyzzy dbus-daemon[2339]: [system] Failed to activate service 'org.freedesktop.systemd1': timed out (service_start_timeout=25000ms)
2025-10-01T17:57:35.163400+00:00 xyzzy sshd[1086837]: pam_systemd(sshd:session): Failed to create session: Connection timed out

-- 
You received this bug notification because you are a member of
Debcrafters 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:
  New

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