On Thu, Apr 28, 2011 at 04:21:58PM +0200, Mattias Geniar wrote:
Hi Everyone,
So that's pretty straight forward. My LDAP systems are running fine, and I can authenticate to them.
However, the problem: when the client boots *without network connectivity*, the server gets stuck/hangs at "Start System Message Bus". I've tracked this down to the following known bug in Redhat, but it dates back to early 2010. https://bugzilla.redhat.com/show_bug.cgi?id=182464#c46
Yes, the bug is actually older than that---Don't know if it's only RH based systems (as so many things seem to work everywhere but RH and their offshoots) or ldap. You should be able to fix it by changing /etc/ldap.conf. There is a default commented line in there
#bind_policy hard
Uncomment it, change it to soft. (On the client.) Note this is /etc/ldap.conf--in Fedora, if that's the client, I believe it's now /etc/pam_ldap.conf or possibly /etc/nss_ldap.conf.
I can't find the earlier bug at first glance, but it's FAR older than 2010, and they never bothered to fix it.
Has anyone else ever solved this to still be able to keep the group ldap entry in nsswitch.conf without having a server hang on boot if there's no network?
See above. Darn, I wish I could find that older bug, so that I could go to the newer one you mention and point out that they've been unable to fix it for far longer than a year. :) (I might do it anyway)
Grouchily yours, (Not at you, at RH for being unable to get such a basic thing to work--actually, at one point, Fedora changed bind_policy to soft so that it would work, but now they're back to the broken way.)