systemd restart-loops logind

[Thomas Mayer]

Syslog logs systemd trying to restart logind every few seconds:

May 7 00:51:29 server systemd[1]: Starting Login Service...
May 7 00:51:54 server systemd[1]: systemd-logind.service: Main process exited, code=exited, status=1/FAILURE
May 7 00:51:54 server systemd[1]: Failed to start Login Service.
May 7 00:51:54 server systemd[1]: systemd-logind.service: Unit entered failed state.
May 7 00:51:54 server systemd[1]: systemd-logind.service: Failed with result 'exit-code'.
May 7 00:51:54 server systemd[1]: systemd-logind.service: Service has no hold-off time, scheduling restart.
May 7 00:51:54 server systemd[1]: Stopped Login Service.
May 7 00:51:54 server systemd[1]: Starting Login Service...
May 7 00:52:19 server systemd[1]: systemd-logind.service: Main process exited, code=exited, status=1/FAILURE
May 7 00:52:19 server systemd[1]: Failed to start Login Service.
May 7 00:52:19 server systemd[1]: systemd-logind.service: Unit entered failed state.
May 7 00:52:19 server systemd[1]: systemd-logind.service: Failed with result 'exit-code'.
May 7 00:52:19 server systemd[1]: systemd-logind.service: Service has no hold-off time, scheduling restart.
May 7 00:52:19 server systemd[1]: Stopped Login Service.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: systemd 229-4ubuntu17
ProcVersionSignature: Ubuntu 4.8.0-51.54~16.04.1-generic 4.8.17
Uname: Linux 4.8.0-51-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
Date: Sun May 7 00:51:07 2017
InstallationDate: Installed on 2013-08-21 (1353 days ago)
InstallationMedia: Ubuntu-Server 13.04 "Raring Ringtail" - Release amd64 (20130423.1)
Lsusb:
 Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
 Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
ProcEnviron:
 TERM=screen.xterm-256color
 PATH=(custom, no user)
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-51-generic root=UUID=16120d81-8cde-4e81-87cd-f55f65a4923b ro rootflags=subvol=@
SourcePackage: systemd
SystemdDelta:
 [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf
 [EXTENDED] /lib/systemd/system/systemd-timesyncd.service → /lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf

 2 overridden configuration files found.
UpgradeStatus: Upgraded to xenial on 2016-10-24 (193 days ago)
dmi.bios.date: 03/13/2014
dmi.bios.vendor: Intel Corp.
dmi.bios.version: SWQ6710H.86A.0067.2014.0313.1347
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: DQ67OW
dmi.board.vendor: Intel Corporation
dmi.board.version: AAG12528-309
dmi.chassis.type: 3
dmi.modalias: dmi:bvnIntelCorp.:bvrSWQ6710H.86A.0067.2014.0313.1347:bd03/13/2014:svn:pn:pvr:rvnIntelCorporation:rnDQ67OW:rvrAAG12528-309:cvn:ct3:cvr:

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[David Anderson (daveanderson1)]

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

[kenn (whatnext)]

I just noticed that I have the same exact issue. I am running Ubuntu 16.04 Desktop, I enabled multiarch support and I am running 32 bit installation with 64 bit kernel.

May 24 12:59:13 kenn systemd-logind[1680]: Failed to send delayed message: Unit suspend-to-hibernate.service not found.
May 24 12:59:13 kenn systemd[1]: systemd-logind.service: Main process exited, code=exited, status=1/FAILURE
May 24 12:59:13 kenn systemd[1]: systemd-logind.service: Unit entered failed state.
May 24 12:59:13 kenn systemd[1]: systemd-logind.service: Failed with result 'exit-code'.
May 24 12:59:13 kenn systemd[1]: systemd-logind.service: Service has no hold-off time, scheduling restart.
May 24 12:59:13 kenn systemd[1]: Stopped Login Service.
May 24 12:59:13 kenn systemd[1]: Starting Login Service...

[Dan Streetman (ddstreet)]

please reopen if this is still an issue