Does anyone have an idea how to do a temp fix job on this? For us, this happens on an off the shelf gitlab AWS image (Ubuntu 16.04) Because the gitlab runners ssh into the gitlab server very many times, each one of those ssh logins needs to timeout on the login1 hand off and sometimes it crashes the build, so it's pretty serious for us. This is our log
Nov 20 09:37:59 ip-10-159-8-x systemd[1]: Stopped Login Service. Nov 20 09:37:59 ip-10-159-8-x systemd[1]: Starting Login Service... Nov 20 09:38:07 ip-10-159-8-x dbus[25038]: [system] Activating systemd to hand-off: service name='org.freedesktop.login1' uni t='dbus-org.freedesktop.login1.service' Nov 20 09:38:24 ip-10-159-8-x systemd[1]: systemd-logind.service: Main process exited, code=exited, status=1/FAILURE Nov 20 09:38:24 ip-10-159-8-x systemd[1]: Failed to start Login Service. Nov 20 09:38:24 ip-10-159-8-x systemd[1]: systemd-logind.service: Unit entered failed state. Nov 20 09:38:24 ip-10-159-8-x systemd[1]: systemd-logind.service: Failed with result 'exit-code'. Nov 20 09:38:24 ip-10-159-8-x systemd[1]: systemd-logind.service: Service has no hold-off time, scheduling restart. Nov 20 09:38:24 ip-10-159-8-x systemd[1]: Stopped Login Service. many thanks Dave -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1688933 Title: systemd restart-loops logind To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1688933/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
