systemd user@###.service failure causing 90 sec delays during boot, login
I installed Debian 11 (Bullseye) with GNOME 3.38.5 (Wayland), LINUX kernel Linux version 5.10.0-11-amd64 (gcc-10 (Debian 10.2.1-6) 10.2.1 20210110, GNU ld 2.35.2) #1 SMP Debian 5.10.92-1 (2022-01-18) on a USB stick, and am using it with an ACER Aspire 514 laptop.
This operating system has worked excellently for months, but for the last 2 days has suddenly been taking a very long time to boot. The cause of the delay can be seen from the syslog:
Feb 28 10:09:30 cpe-67-241-65-193 systemd[1]: Started GNOME Display Manager.
(The above is the last line on the verbose boot log printed on screen during boot process)
(omitted next lines from network manager, & kernel, about setting up network & loading audio firmware, etc.)
Feb 28 10:09:31 cpe-67-241-65-193 systemd[1]: Created slice User Slice of UID 119.
Feb 28 10:09:31 cpe-67-241-65-193 systemd[1]: Starting User Runtime Directory /run/user/119...
Feb 28 10:09:31 cpe-67-241-65-193 systemd[1]: Finished User Runtime Directory /run/user/119.
Feb 28 10:09:31 cpe-67-241-65-193 systemd[1]: Starting User Manager for UID 119...
...
Feb 28 10:11:01 cpe-67-241-65-193 systemd[1]: user@119.service: Main process exited, code=exited, status=1/FAILURE
Feb 28 10:11:01 cpe-67-241-65-193 systemd[1]: user@119.service: Killing process 1144 (gpgconf) with signal SIGKILL.
Feb 28 10:11:01 cpe-67-241-65-193 systemd[1]: user@119.service: Killing process 1145 (awk) with signal SIGKILL.
Feb 28 10:11:01 cpe-67-241-65-193 systemd[1]: user@119.service: Killing process 1174 (dirmngr) with signal SIGKILL.
Feb 28 10:11:01 cpe-67-241-65-193 systemd[1]: user@119.service: Killing process 1144 (gpgconf) with signal SIGKILL.
Feb 28 10:11:01 cpe-67-241-65-193 systemd[1]: user@119.service: Killing process 1145 (awk) with signal SIGKILL.
Feb 28 10:11:01 cpe-67-241-65-193 systemd[1]: user@119.service: Killing process 1174 (dirmngr) with signal SIGKILL.
Feb 28 10:11:01 cpe-67-241-65-193 systemd[1]: user@119.service: Failed with result 'exit-code'.
Feb 28 10:11:01 cpe-67-241-65-193 systemd[1]: user@119.service: Unit process 1174 (dirmngr) remains running after unit stopped.
Feb 28 10:11:01 cpe-67-241-65-193 systemd[1]: Failed to start User Manager for UID 119.
Feb 28 10:11:01 cpe-67-241-65-193 systemd[1]: Started Session c1 of user Debian-gdm.
The login screen appeared at 10:11:09:
Feb 28 10:11:09 cpe-67-241-65-193 systemd[1]: Startup finished in 51.017s (kernel) + 1min 48.624s (userspace) = 2min 39.642s.
The same 90 sec delay then occurs again after any user enters his password (at 10:11:46):
Feb 28 10:11:46 cpe-67-241-65-193 systemd[1]: Created slice User Slice of UID 1003.
Feb 28 10:11:46 cpe-67-241-65-193 systemd[1]: Starting User Runtime Directory /run/user/1003...
Feb 28 10:11:46 cpe-67-241-65-193 systemd[1]: Finished User Runtime Directory /run/user/1003.
Feb 28 10:11:46 cpe-67-241-65-193 systemd[1]: Starting User Manager for UID 1003...
....
Feb 28 10:13:16 cpe-67-241-65-193 systemd[1]: user@1003.service: Main process exited, code=exited, status=1/FAILURE
.... (as above)
Feb 28 10:13:16 cpe-67-241-65-193 systemd[1]: Failed to start User Manager for UID 1003.
Feb 28 10:13:16 cpe-67-241-65-193 systemd[1]: Started Session 2 of user kcl.
The first 90 sec. delay only occurs on initial startup, & the second only when any user logs in (the problem is not particular to UID1003, but occurs for all UIDs 100[0-5]. Once the machine has booted & the user is logged in, it functions normally with no observable problems.
I do not know what caused this, but it occurred right after I:
> allowed the installation of the latest software update (some lib files, the names of which I unfortunately did not record)
> installed the ufw firewall package.
I would be very grateful for any information about how to resolve this (apart from re-installing the system) or even any reference that might give information about how I might resolve this problem. (I have looked at the systemd.service man page, but although I have experience with the unix command line, I have only been using Debian since Nov. 2021 & am not familiar with its system administration, & I could find no information there about this problem.)
Reply to: