Bug#792519: systemd-logind fails to start on system using LDAP

Felipe Sateler fsateler at debian.org
Wed Jul 15 18:18:07 BST 2015


Control: tags -1 moreinfo

Hi,

On 15 July 2015 at 14:01, Daniel Schepler <dschepler at gmail.com> wrote:
> Package: systemd
> Version: 222-1
> Severity: important
>
> Since about a week ago, when systemd got upgraded to 221-1, the system almost
> always does not boot properly.  It gets to the kdm prompt, but then trying to
> log in to a KDE session as an LDAP user takes a very long time - also even
> logging in on the console takes a minute or so.  It would appear that systemd-
> logind is unable to start.
>
> The only way I've been able to work around this is: edit /etc/nsswitch.conf to
> disable ldap, reboot, login as root and reenable ldap in /etc/nsswitch.conf,
> then restart nscd and kdm.  Even then, a KDE session run as an LDAP user
> doesn't fully work - it first warns about being unable to start the KDE power
> service (or something like that) and then eventually plasma-desktop crashes.
> (I'm guessing that the inability to restart the system dbus instance is causing
> issues here.)  So, I end up having to log in using my local backup account,
> then su to my real LDAP account in a terminal.
>
> The failure to boot properly isn't 100% reproducible, but I'd say it fails
> about 80-90% of the time.
>
> (I'm still running testing, I just upgraded systemd packages manually to the
> version from unstable to satisfy reportbug - and version 222-1 still manifests
> the same problem.)
>
> I'll attach the output of journalctl from a broken boot.

This contains a massive amount of:

Jul 15 09:34:37 deb-dschepler nslcd[905]: nss_ldap: could not connect
to any LDAP server as (null) - Can't contact LDAP server
Jul 15 09:34:37 deb-dschepler nslcd[905]: nss_ldap: failed to bind to
LDAP server ldap://dirsrv.snt.loc: Can't contact LDAP server
Jul 15 09:34:37 deb-dschepler nslcd[905]: nss_ldap: reconnecting to
LDAP server (sleeping 1 seconds)...

But with the service varying.

I note that the NetworkManager service is started after many of those
messages. And after a while:

Jul 15 09:35:09 deb-dschepler nscd[851]: nss_ldap: reconnected to LDAP
server ldap://dirsrv.snt.loc after 2 attempts
Jul 15 09:35:10 deb-dschepler ntpd[893]: Listen normally on 4 eth0
10.10.3.14 UDP 123
Jul 15 09:35:10 deb-dschepler ntpd[893]: peers refreshed


So it looks like the problem is with your dns resolution?


-- 

Saludos,
Felipe Sateler




More information about the Pkg-systemd-maintainers mailing list