Bug#770135: Bug#793814: systemd-logind: Logins via ssh and su are delayed by 25 seconds

[Felipe Sateler]

Control: forcemerge 770135 793814
Control: found 770135 222-2

Hi Steven,

On 27 July 2015 at 15:05, Steven Monai <smonai at sd57.bc.ca> wrote:
> Dear Maintainer,
>
> There is an issue with the systemd-logind daemon that appears to be
> triggered whenever the dbus daemon is restarted.
>
> Specifically, after a recent 'apt-get upgrade' to install a security
> update (of libexpat1, if that matters), I restarted the 'dbus' daemon,
> since 'needrestart' had flagged it as one of the daemons requiring a
> restart.
>
> After that, I noticed that logins via ssh and 'su -' were being
> delayed by about 25 seconds. Here is what I see in /var/log/syslog
> after every login attempt:
>
>     Jul 27 09:27:59 ldb dbus[27174]: [system] Activating via systemd: service name='org.freedesktop.login1' unit='dbus-org.freedesktop.login1.service'
>     Jul 27 09:28:24 ldb dbus[27174]: [system] Failed to activate service 'org.freedesktop.login1': timed out
>
> Notice the 25-second timespan between log entries.
>
> The problem goes away after I restart the systemd-logind daemon.
>
> To reliably trigger the problem on my system (it is a headless
> server, no Xorg installed), I merely need to do this:
>
>     systemctl restart dbus
>
> All subsequent logins or su's then experience a 25 second delay
> before proceeding successfully. The following command then returns
> login processing to normal, without the delay:
>
>     systemctl restart systemd-logind
>

This was already reported as #770135 , but the dbus connection was not
mentioned before. I can confirm the same behavior on systemd 222-2
(inside an nspawn container).

-- 

Saludos,
Felipe Sateler