Looking at the logs, I think the root cause is that a generator is hanging which leads to a timeout and freezing execution of pid1. Hence, the DBus service is no longer available and services cannot be started.
Mar 24 06:55:05 myhost.xxx.domain.tld systemd[1]: Successfully forked off '(sd-gens)' as PID 1158420. Mar 24 06:55:05 myhost.xxx.domain.tld (sd-gens)[1158420]: File '/etc/systemd/system-generators/systemd-gpt-auto-generator' is a mask. Mar 24 06:55:05 myhost.xxx.domain.tld (sd-gens)[1158420]: File '/usr/lib/systemd/system-generators/systemd-gpt-auto-generator' is masked by previous entry. Mar 24 06:55:05 myhost.xxx.domain.tld (sd-gens)[1158420]: Successfully forked off '(sd-exec-strv)' as PID 1158421. Mar 24 06:55:05 myhost.xxx.domain.tld (sd-exec-[1158421]: About to execute /usr/lib/systemd/system-generators/cloud-init-generator (null) Mar 24 06:55:05 myhost.xxx.domain.tld (sd-exec-[1158421]: Successfully forked off '(direxec)' as PID 1158422. Mar 24 06:55:05 myhost.xxx.domain.tld (sd-exec-[1158421]: About to execute /usr/lib/systemd/system-generators/friendly-recovery (null) Mar 24 06:55:05 myhost.xxx.domain.tld (sd-exec-[1158421]: Successfully forked off '(direxec)' as PID 1158423. Mar 24 06:55:05 myhost.xxx.domain.tld (sd-exec-[1158421]: About to execute /usr/lib/systemd/system-generators/netplan (null) Mar 24 06:55:05 myhost.xxx.domain.tld (sd-exec-[1158421]: Successfully forked off '(direxec)' as PID 1158424. Mar 24 06:55:05 myhost.xxx.domain.tld (sd-exec-[1158421]: About to execute /usr/lib/systemd/system-generators/rpc-pipefs-generator (null) Mar 24 06:55:05 myhost.xxx.domain.tld (sd-exec-[1158421]: Successfully forked off '(direxec)' as PID 1158425. Mar 24 06:55:05 myhost.xxx.domain.tld (sd-exec-[1158421]: About to execute /usr/lib/systemd/system-generators/snapd-generator (null) Mar 24 06:55:05 myhost.xxx.domain.tld (sd-exec-[1158421]: Successfully forked off '(direxec)' as PID 1158426. Mar 24 06:55:05 myhost.xxx.domain.tld (sd-exec-[1158421]: About to execute /usr/lib/systemd/system-generators/sshd-socket-generator (null) Mar 24 06:55:05 myhost.xxx.domain.tld (sd-exec-[1158421]: Successfully forked off '(direxec)' as PID 1158428. Mar 24 06:55:05 myhost.xxx.domain.tld (sd-exec-[1158421]: About to execute /usr/lib/systemd/system-generators/systemd-cryptsetup-generator (null) Mar 24 06:55:05 myhost.xxx.domain.tld (sd-exec-[1158421]: Successfully forked off '(direxec)' as PID 1158430. Mar 24 06:55:05 myhost.xxx.domain.tld (sd-exec-[1158421]: About to execute /usr/lib/systemd/system-generators/systemd-debug-generator (null) Mar 24 06:55:05 myhost.xxx.domain.tld (sd-exec-[1158421]: Successfully forked off '(direxec)' as PID 1158431. Mar 24 06:55:05 myhost.xxx.domain.tld (sd-exec-[1158421]: About to execute /usr/lib/systemd/system-generators/systemd-fstab-generator (null) Mar 24 06:55:05 myhost.xxx.domain.tld (sd-exec-[1158421]: Successfully forked off '(direxec)' as PID 1158432. Mar 24 06:55:05 myhost.xxx.domain.tld (sd-exec-[1158421]: About to execute /usr/lib/systemd/system-generators/systemd-getty-generator (null) Mar 24 06:55:05 myhost.xxx.domain.tld (sd-exec-[1158421]: Successfully forked off '(direxec)' as PID 1158433. Mar 24 06:55:05 myhost.xxx.domain.tld (sd-exec-[1158421]: About to execute /usr/lib/systemd/system-generators/systemd-hibernate-resume-generator (null) Mar 24 06:55:05 myhost.xxx.domain.tld (sd-exec-[1158421]: Successfully forked off '(direxec)' as PID 1158436. Mar 24 06:55:05 myhost.xxx.domain.tld (sd-exec-[1158421]: About to execute /usr/lib/systemd/system-generators/systemd-integritysetup-generator (null) Mar 24 06:55:05 myhost.xxx.domain.tld (sd-exec-[1158421]: Successfully forked off '(direxec)' as PID 1158437. Mar 24 06:55:05 myhost.xxx.domain.tld (sd-exec-[1158421]: About to execute /usr/lib/systemd/system-generators/systemd-rc-local-generator (null) Mar 24 06:55:05 myhost.xxx.domain.tld (sd-exec-[1158421]: Successfully forked off '(direxec)' as PID 1158438. Mar 24 06:55:05 myhost.xxx.domain.tld (sd-exec-[1158421]: About to execute /usr/lib/systemd/system-generators/systemd-run-generator (null) Mar 24 06:55:05 myhost.xxx.domain.tld (sd-exec-[1158421]: Successfully forked off '(direxec)' as PID 1158439. Mar 24 06:55:05 myhost.xxx.domain.tld (sd-exec-[1158421]: About to execute /usr/lib/systemd/system-generators/systemd-system-update-generator (null) Mar 24 06:55:05 myhost.xxx.domain.tld (sd-exec-[1158421]: Successfully forked off '(direxec)' as PID 1158440. Mar 24 06:55:05 myhost.xxx.domain.tld (sd-exec-[1158421]: About to execute /usr/lib/systemd/system-generators/systemd-sysv-generator (null) Mar 24 06:55:05 myhost.xxx.domain.tld (sd-exec-[1158421]: Successfully forked off '(direxec)' as PID 1158441. Mar 24 06:55:05 myhost.xxx.domain.tld (sd-exec-[1158421]: About to execute /usr/lib/systemd/system-generators/systemd-veritysetup-generator (null) Mar 24 06:55:05 myhost.xxx.domain.tld (sd-exec-[1158421]: Successfully forked off '(direxec)' as PID 1158442. Mar 24 06:55:05 myhost.xxx.domain.tld rpc.gssd[611]: handle_gssd_upcall(0x71eca0d70740): 'mech=krb5 uid=0 enctypes=20,19,26,25,18,17' (nfs/clnt0) Mar 24 06:55:05 myhost.xxx.domain.tld rpc.gssd[611]: start_upcall_thread(0x71eca0d70740): created thread id 0x71ec9d3fb6c0 Mar 24 06:55:05 myhost.xxx.domain.tld rpc.gssd[611]: krb5_use_machine_creds(0x71ec9d3fb6c0): uid 0 tgtname (null) Mar 24 06:55:06 myhost.xxx.domain.tld rpc.gssd[611]: No key table entry found for [email protected] while getting keytab entry for '[email protected]' Mar 24 06:55:06 myhost.xxx.domain.tld rpc.gssd[611]: find_keytab_entry(0x71ec9d3fb6c0): Success getting keytab entry for '[email protected]' Mar 24 06:55:06 myhost.xxx.domain.tld rpc.gssd[611]: gssd_get_single_krb5_cred(0x71ec9d3fb6c0): Credentials in CC 'FILE:/tmp/krb5ccmachine_ADSERVER.AD.DOMAIN.TLD' are good until Tue Mar 24 15:38:37 2026 Mar 24 06:55:06 myhost.xxx.domain.tld rpc.gssd[611]: gssd_get_single_krb5_cred(0x71ec9d3fb6c0): Credentials in CC 'FILE:/tmp/krb5ccmachine_ADSERVER.AD.DOMAIN.TLD' are good until Tue Mar 24 15:38:37 2026 Mar 24 06:55:06 myhost.xxx.domain.tld rpc.gssd[611]: create_auth_rpc_client(0x71ec9d3fb6c0): creating tcp client for server nfsserver.domain.tld Mar 24 06:55:06 myhost.xxx.domain.tld rpc.gssd[611]: create_auth_rpc_client(0x71ec9d3fb6c0): creating context with server [email protected] Mar 24 06:55:06 myhost.xxx.domain.tld rpc.gssd[611]: in authgss_create_default() Mar 24 06:55:06 myhost.xxx.domain.tld rpc.gssd[611]: in authgss_create() Mar 24 06:55:06 myhost.xxx.domain.tld rpc.gssd[611]: authgss_create: name is 0x71ec90003c90 Mar 24 06:55:06 myhost.xxx.domain.tld rpc.gssd[611]: authgss_create: gd->name is 0x71ec900079d0 Mar 24 06:55:06 myhost.xxx.domain.tld rpc.gssd[611]: in authgss_refresh() Mar 24 06:55:06 myhost.xxx.domain.tld rpc.gssd[611]: The token being sent (length 1613): Mar 24 06:55:06 myhost.xxx.domain.tld rpc.gssd[611]: in authgss_marshal() Mar 24 06:55:06 myhost.xxx.domain.tld rpc.gssd[611]: xdr_rpc_gss_buf: encode success ((nil):0) Mar 24 06:55:06 myhost.xxx.domain.tld rpc.gssd[611]: xdr_rpc_gss_cred: encode success (v 1, proc 1, seq 0, svc 1, ctx (nil):0) Mar 24 06:55:06 myhost.xxx.domain.tld rpc.gssd[611]: in authgss_wrap() Mar 24 06:55:06 myhost.xxx.domain.tld rpc.gssd[611]: xdr_rpc_gss_buf: encode success (0x71ec900292c0:1613) Mar 24 06:55:06 myhost.xxx.domain.tld rpc.gssd[611]: xdr_rpc_gss_init_args: encode success (token 0x71ec900292c0:1613) Mar 24 06:55:06 myhost.xxx.domain.tld rpc.gssd[611]: in authgss_validate() Mar 24 06:55:06 myhost.xxx.domain.tld rpc.gssd[611]: in authgss_unwrap() Mar 24 06:55:06 myhost.xxx.domain.tld rpc.gssd[611]: xdr_rpc_gss_buf: decode success (0x71ec900289b0:4) Mar 24 06:55:06 myhost.xxx.domain.tld rpc.gssd[611]: xdr_rpc_gss_buf: decode success (0x71ec90028e50:155) Mar 24 06:55:06 myhost.xxx.domain.tld rpc.gssd[611]: xdr_rpc_gss_init_res decode success (ctx 0x71ec900289b0:4, maj 0, min 0, win 128, token 0x71ec90028e50:155) Mar 24 06:55:06 myhost.xxx.domain.tld rpc.gssd[611]: The token we just received (length 155): Mar 24 06:55:06 myhost.xxx.domain.tld rpc.gssd[611]: authgss_create_default: freeing name 0x71ec90003c90 Mar 24 06:55:06 myhost.xxx.domain.tld rpc.gssd[611]: in authgss_get_private_data() Mar 24 06:55:06 myhost.xxx.domain.tld rpc.gssd[611]: do_downcall(0x71ec9d3fb6c0): lifetime_rec=8h:43m:31s [email protected] Mar 24 06:55:06 myhost.xxx.domain.tld rpc.gssd[611]: in authgss_free_private_data() Mar 24 06:55:06 myhost.xxx.domain.tld rpc.gssd[611]: in authgss_destroy() Mar 24 06:55:06 myhost.xxx.domain.tld rpc.gssd[611]: in authgss_destroy_context() Mar 24 06:55:06 myhost.xxx.domain.tld rpc.gssd[611]: authgss_destroy: freeing name 0x71ec900079d0 [ note timestamp of the next message ] Mar 24 06:56:35 myhost.xxx.domain.tld (sd-gens)[1158420]: (sd-exec-strv) terminated by signal ALRM. Mar 24 06:56:35 myhost.xxx.domain.tld systemd[1]: (sd-gens) failed with exit status 1. Mar 24 06:56:35 myhost.xxx.domain.tld systemd[1]: Failed to fork off sandboxing environment for executing generators: Protocol error Mar 24 06:56:35 myhost.xxx.domain.tld systemd[1]: Closing set fd 274 (socket:[6691]) Mar 24 06:56:35 myhost.xxx.domain.tld systemd[1]: Closing set fd 233 (socket:[14722]) [...] Mar 24 06:56:35 myhost.xxx.domain.tld systemd[1]: Freezing execution. It also looks from the logs like you are using NFS, so this sounds like it could be the same as bug 2165295. There is a patch [1] in newer versions of systemd that should fix this, but it is not trivial to backport (requires a lot of re-working of chase.c as-is). One workaround could be to disable systemd-fstab-generator if you do not strictly need it (this depends on the contents of your /etc/fstab, and which units are generated as a result). You can do a dry-run of the generator to see what it creates: $ mkdir /tmp/fstab-generator $ SYSTEMD_LOG_LEVEL=debug /usr/lib/systemd/system-generators/systemd-fstab-generator /tmp/fstab-generator You can read more about that generator at [2]. But, ultimately I think we need to backport a patch similar to the one from upstream. [1] https://github.com/systemd/systemd/commit/36344cd1f1283ed609746e29137c8439c41ccd5d [2] https://manpages.ubuntu.com/manpages/noble/man8/systemd-fstab-generator.8.html ** Changed in: systemd (Ubuntu) Status: Confirmed => Triaged ** Changed in: systemd (Ubuntu) Importance: Undecided => Medium ** Also affects: systemd (Ubuntu Resolute) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Stonking) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Noble) Importance: Undecided Status: New ** Changed in: systemd (Ubuntu Noble) Importance: Undecided => Medium ** Changed in: systemd (Ubuntu Resolute) Importance: Undecided => High ** Changed in: systemd (Ubuntu Resolute) Importance: High => Medium ** Changed in: systemd (Ubuntu Stonking) Importance: Undecided => Medium ** Changed in: systemd (Ubuntu Noble) Status: New => Triaged ** Changed in: systemd (Ubuntu Resolute) Status: New => Triaged ** Changed in: systemd (Ubuntu Stonking) Status: New => Triaged ** Tags added: systemd-sru-next -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2126437 Title: system] Failed to activate service 'org.freedesktop.systemd1': timed out To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2126437/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
