I have an old arm5 plug computer that is running latest arch linux arm.
# uname -a Linux delilah 4.4.77-1-ARCH #1 PREEMPT Tue Jul 18 02:17:24 UTC 2017 armv5tel GNU/Linux
# systemctl --version systemd 234 +PAM -AUDIT -SELINUX -IMA -APPARMOR +SMACK -SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 -SECCOMP +BLKID +ELFUTILS +KMOD -IDN2 +IDN default-hierarchy=hybrid
After a recent update I started having problems logging in. It seems systemd-logind is timing out for some reason. I see this in the journalctl -xe output
-- Unit systemd-logind.service has begun starting up. Aug 14 09:54:27 delilah systemd-logind[484]: Failed to enable subscription: Connection timed out Aug 14 09:54:27 delilah systemd-logind[484]: Failed to fully start up daemon: Connection timed out Aug 14 09:54:27 delilah dbus[231]: [system] Failed to activate service 'org.freedesktop.systemd1': timed out Aug 14 09:54:27 delilah systemd[1]: systemd-logind.service: Main process exited, code=exited, status=1/FAILURE Aug 14 09:54:27 delilah systemd[1]: Failed to start Login Service. -- Subject: Unit systemd-logind.service has failed -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit systemd-logind.service has failed. -- -- The result is failed. Aug 14 09:54:27 delilah systemd[1]: systemd-logind.service: Unit entered failed state. Aug 14 09:54:27 delilah systemd[1]: systemd-logind.service: Failed with result 'exit-code'. Aug 14 09:54:27 delilah systemd[1]: systemd-logind.service: Service has no hold-off time, scheduling restart. Aug 14 09:54:27 delilah systemd[1]: Stopped Login Service. -- Subject: Unit systemd-logind.service has finished shutting down -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit systemd-logind.service has finished shutting down. Aug 14 09:54:27 delilah systemd[1]: Starting Login Service... -- Subject: Unit systemd-logind.service has begun start-up -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit systemd-logind.service has begun starting up.
I cannot use systemd-analyze because it reports
# systemd-analyze Bootup is not yet finished. Please try again later.
I did try to restore the status quo ante, but this failed. It seems I can login after a delay (presumably something is timing out).
systemctl status shows> # systemctl status
* delilah State: starting Jobs: 2 queued Failed: 1 units Since: Sat 2000-01-01 00:00:06 GMT; 17 years 7 months ago CGroup: / |-init.scope | `-1 /sbin/init `-system.slice |-dbus.service | `-231 /usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation |-system-sshd.slice | `-sshd@0-192.168.0.9:22-213.78.87.157:65502.service | |-421 sshd: robin [priv] | |-427 sshd: robin@pts/0 | |-428 -bash | |-442 sudo su | |-443 su | |-444 bash | |-547 systemctl status | `-548 less |-nginx.service | |-374 nginx: master process /usr/bin/nginx -g pid /run/nginx.pid; error_log stderr; | |-375 nginx: worker process | |-376 nginx: worker process | |-377 nginx: worker process | `-378 nginx: worker process |-system-serial\x2dgetty.slice | `-serial-getty@ttyS0.service | `-350 /sbin/agetty -o -p -- \u --keep-baud 115200,38400,9600 ttyS0 vt220 |-atd.service | `-228 /usr/bin/atd -f |-systemd-journald.service | `-132 /usr/lib/systemd/systemd-journald |-systemd-timesyncd.service | `-206 /usr/lib/systemd/systemd-timesyncd |-systemd-logind.service | `-545 /usr/lib/systemd/systemd-logind |-system-uwsgi.slice | |-uwsgi@thing.service | | |-226 /usr/bin/uwsgi --ini /etc/uwsgi/thing.ini | | |-255 /usr/bin/uwsgi --ini /etc/uwsgi/thing.ini | | `-256 /usr/bin/uwsgi --ini /etc/uwsgi/thing.ini | `-uwsgi@notes.service | |-219 /usr/bin/uwsgi --ini /etc/uwsgi/notes.ini | |-253 /usr/bin/uwsgi --ini /etc/uwsgi/notes.ini | `-254 /usr/bin/uwsgi --ini /etc/uwsgi/notes.ini |-systemd-udevd.service | `-148 /usr/lib/systemd/systemd-udevd |-haveged.service | `-216 /usr/bin/haveged -F -w 1024 -v 1 |-nmbd.service | `-383 /usr/bin/nmbd -D |-smbd.service | |-412 /usr/bin/smbd -D | |-413 /usr/bin/smbd -D | |-414 /usr/bin/smbd -D | `-416 /usr/bin/smbd -D `-cronie.service |-210 /usr/bin/crond -n |-397 /bin/bash /home/robin/bin/check-connected --check-connected-detached `-543 sleep 60
I'm wondering how I can find out what's wrong. Is there some timer that my ancient sheevaplug lacks. The above shows I have no permanent hardware clock on this machine so perhaps that's the issue. Some of my filesystems seem to have very ancient dates etc etc.
-- Robin Becker _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel