You are not logged in.
Updated 20 minutes ago and now my system hangs on boot. "Starting D-BUS..." remains BUSY.
Offline
The problem is LDAP-related. In everything.log:
nss_ldap: failed to bind to LDAP server ldap://192.168.0.50: Can't contact LDAP serverBut I don't know how to fix the issue. TIA.
Offline
Upon further investigation I don't think this is update-related. D-BUS made an LDAP request, but slapd wasn't started. If I start net-profiles and slapd before dbus, then slapd hangs. Changing bind_policy to soft in ldap.conf allows the system to boot, but several error messages are printed when dbus tries to contact the server. I can't find a clean solution.
Offline
Actually I was experiencieng the same problems, whenever I tried to authenticate to an ldap server in our setup. As far as I can tell, the problem is related to the nss_ldap package as outlined in the old bug report here
https://bugzilla.redhat.com/show_bug.cgi?id=502072
It is somehow related to the group lookup in nsswitch.conf, because when i remove the ldap entry in said from
group: files ldapto
group: filesit boots also without any problem, but is of course an unacceptable workaround. I also tried to use nscd, but I was still unable to boot. One way to resolve this issue in our setup is to start the network before you start dbus. This of course makes it impossible to use with networkmanager or in a pure systemd setting (since dbus seems to be started too early in the boot process). As suggested above another way to resolve it is to use another ldap authentication module, e.g sssd, nss-pam-ldapd. In our setup we are using nss-pam-ldapd successfully, since it has less dependencies then sssd (and I don't want to include too much aur dependencies on our machines). For a pkg see for instance the build in the comments of
https://aur.archlinux.org/packages.php?ID=38167
Offline