Red Hat Bugzilla – Bug 427019
udevd: nss_ldap: could not connect to any LDAP server as
Last modified: 2008-09-15 10:38:42 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:188.8.131.52) Gecko/20071127 Firefox/184.108.40.206
Description of problem:
When you try to configure your system to check authentication against an LDAP server, as soon as you restart your system on runlevel 3 udevd: can't contact an LDAP server although the server is fine.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
2.$ choose LDAP authentication and enter a valid ldap server like dc=example,dc=com server 192.168.100.1 etc.
3. save configuration then restart your machine.
udevd: is scheduling a retry to contact an LDAP server for an indefinite time, pressing CTRL-C will continue the next execution in daemon. but since udevd is failing some hardware doesn't work anymore.
The server will continue to boot without an error
visit this site for more details
This should be marked as critical, it affects Redhat 4 and 5.
If ldap is specified before files in the nsswitch.conf it will hang indefinitely
on boot in an attempt to contact an ldap server.
The bug is explained clearly on the Gentoo bugzilla site, authors of start_udev.
Proposing for RHEL-5.3 and granting Devel ACK.
Read ya, Phil
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux maintenance release. Product Management has requested
further review of this request by Red Hat Engineering, for potential
inclusion in a Red Hat Enterprise Linux Update release for currently deployed
products. This request is not yet committed for inclusion in an Update
udev should not need to contact an ldap server, as long as you don't have custom rules with users/groups which are not in the standard passwd/group file.
No special configs in passwd/group files, just ldap before files in nsswitch.conf.
passwd: files ldap
shadow: files ldap
group: ldap files #<-This line in nsswitch.conf causes machine to hang on boot.
Not a problem if you know about it and real simple to fix, but it shouldn't try and do a ldap search before the network has been initialised and hang indefinitely if it doesn't respond.
not much udev itself can do about.
I am sorry, I can't fix that in udev.