You are not logged in.
Hi. I've been having some problems with my Arch HTPC where sometimes I get a message "A stop job is running for User Login Management" when rebooting the system. I've added an image below. It starts waiting for it for 1 minute 30 seconds, but when it exceeds that value it keeps increasing the timeout. It eventually reboots after about 5-6 minutes. This does not always happen, sometimes it reboots immediately as it should.
I'm using the LightDM method of running Kodi (https://wiki.archlinux.org/title/Kodi#X … th_LightDM). The systemd service file I'm using is a slightly modified version of the stock one. It's identical except I added restart on failure since it sometimes didn't start properly on boot.
[Unit]
Description=Light Display Manager
Documentation=man:lightdm(1)
Conflicts=getty@tty1.service
After=getty@tty1.service systemd-user-sessions.service plymouth-quit.service acpid.service
StartLimitIntervalSec=500
StartLimitBurst=5
[Service]
ExecStart=/usr/bin/lightdm
Restart=on-failure
RestartSec=5s
IgnoreSIGPIPE=no
BusName=org.freedesktop.DisplayManager
[Install]
Alias=display-manager.serviceI'd appreciate any suggestions for how this could be resolved.
https://i.imgur.com/oU3io6O.jpeg
moderator edit -- replaced oversized image with link.
Pasting pictures and code
Last edited by wrongturn (2021-12-04 02:19:21)
Offline
See LightDM#LightDM_does_not_appear_or_monitor_only_displays_TTY_output for lightdm needing to be restarted on boot.
Please post the journal for a shutdown with the stuck service. Please also replace the oversized image with a thumbnail or link.
Offline
Thanks loqs. Setting the option you mentioned in the lightdm.conf seems to have fixed the issues. I changed back to the stock service file, and I haven't noticed any problems when rebooting. Here are the relevant lines from journalctl -x.
dec 03 22:25:58 ruby audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-networkd comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
dec 03 22:25:58 ruby audit: BPF prog-id=0 op=UNLOAD
dec 03 22:25:58 ruby audit: BPF prog-id=0 op=UNLOAD
dec 03 22:27:28 ruby systemd[1]: systemd-logind.service: State 'stop-sigterm' timed out. Killing.
dec 03 22:27:28 ruby systemd[1]: systemd-logind.service: Killing process 420 (systemd-logind) with signal SIGKILL.
dec 03 22:27:28 ruby systemd[1]: systemd-logind.service: Killing process 7882 (close) with signal SIGKILL.
dec 03 22:28:58 ruby systemd[1]: systemd-logind.service: Processes still around after SIGKILL. Ignoring.
dec 03 22:29:01 ruby kernel: nfs: server 192.168.1.195 not responding, timed out
dec 03 22:30:29 ruby systemd[1]: systemd-logind.service: State 'final-sigterm' timed out. Killing.
dec 03 22:30:29 ruby systemd[1]: systemd-logind.service: Killing process 420 (systemd-logind) with signal SIGKILL.
dec 03 22:30:29 ruby systemd[1]: systemd-logind.service: Killing process 7882 (close) with signal SIGKILL.
dec 03 22:31:59 ruby systemd[1]: systemd-logind.service: Processes still around after final SIGKILL. Entering failed mode.
dec 03 22:31:59 ruby systemd[1]: systemd-logind.service: Failed with result 'timeout'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ The unit systemd-logind.service has entered the 'failed' state with result 'timeout'.
dec 03 22:31:59 ruby systemd[1]: Stopped User Login Management.
░░ Subject: A stop job for unit systemd-logind.service has finished
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ A stop job for unit systemd-logind.service has finished.
░░
░░ The job identifier is 1628 and the job result is done.
dec 03 22:31:59 ruby audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-logind comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'Sorry for the large image, I'll use links from now on. I'll mark this solved.
Offline