2.6.20-16 kernel upgrade kills ldap authentication...boot crasher

Bug #117566 reported by TinCan
10
Affects Status Importance Assigned to Milestone
libnss-ldap (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: libnss-ldap

I'm using LDAP client auththentication via community documentation (https://help.ubuntu.com/community/LDAPClientAuthentication).

After the most recent kernel upgrade (2.6.16) I receive the following message:

/lib/init/rw/libnss-ldap.bind_policy_soft: No such file or directory
* Rpeparing restricted driver....
***HANGS HERE***

"Soft" policy appears to be required to to make udev behave properly. I will try removing soft policy and see if that helps matters. Perhaps udev is behaving better these days.

Revision history for this message
TinCan (jcanfield-tshmail) wrote :

I tried commenting out "bind_policy soft" and booting with 2.6.20-16 kernel and I still have the same issues. The error changes somewhat to read:

touch: Cannot touch /lib/init/rw/libnss-ldap.bind_policy_soft: No such file or directory (not exact, from memory)

Note: udev does appears to be behaving properly now without soft binding on 2.6.20-15 kernel, that is good. :) I will keep playing with it until someone who knows a bit more about this steps in.

Revision history for this message
Adam Niedling (krychek) wrote :

Which version of Ubuntu are you using? Is this still an issue?

Changed in libnss-ldap:
status: New → Incomplete
Revision history for this message
Victor Vargas (kamus) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Changed in libnss-ldap (Ubuntu):
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.