[Edgy] Problems with latest upgrades and ldap

[Eamonn Sullivan]

I'm running beta Edgy. I had a working ldap server on localhost (serving also another PC in the house running Dapper). I did a dist-upgrade last night. There were 98 new packages, among them a new version of udev (ubuntu17) and hal.

On restart, the system took more than 20 minutes to boot and displayed lots of messages about being unable to connect to the ldap server.

udevd [2128]: nss_ldap: could not connect to any LDAP server.

Unfortunately, I'm about to leave on a trip to the u.s. until next tuesday, so I'm going to attach a bunch of files in the hope that one of them will be able to help you narrow the problem down.

The only work around I found was to revert the ldap changes and use files/compat instead. The system works fine without ldap.

[Matt Mossholder (matt-mossholder)]

You need to put in a statement "bind_policy soft" in your /etc/libnss_ldap.conf file. udev is starting before LDAP is available, and when it tries too lookup the users and groups associated with the /dev devices, it is attempting to hit the not-yet-available LDAP server. I had the same problem, and the same situation (worked in Dapper, broke in Edgy), and this was the solution, for me. This link:

http://www.liquidx.net/blog/2006/04/03/nss_ldap-undocumented-nss_reconnect_tries/

... also covers some other changes you might require.

   --Matt

[Torsten Flammiger (flammiger)]

yes, now udev complains only half a second (or so...) and all went fine
Thanks