Hi!
I'm using CentOS 5.1 (x86_64) machines which authenticate using
LDAP. At the start of booting I get messages like this:
udevd[1158]: nss_ldap: failed to bind to LDAP server ldaps://ldap.server.example.com/: Can't contact LDAP server
udevd[1158]: nss_ldap: reconnecting to LDAP server...
udevd[1158]: nss_ldap: could not connect to any LDAP server as (null) - Can't contact LDAP server
udevd[1158]: nss_ldap: failed to bind to LDAP server ldaps://ldap.server.example.com/: Can't contact LDAP server
udevd[1158]: nss_ldap: reconnecting to LDAP server (sleeping 1 seconds)...
This escaletes to 2, 4, 8, 16, 32, 64 seconds. After that
(==timeouting for 2 minutes) booting continues without problem, so
this is not really a showstopper, but inconvenient.
Googling around revealed some fixes for Debian/Ubuntu. The bottom line
i that udevd needs some user/group that is not in the local files but
on the LDAP-server. The fix usually was adding this user (nvram,
scanner ...) or group locally. The problem is, that on these systems
after the last attempt something like
udevd[1158]: lookup_group: error resolving group 'rdma': Illegal seek
is printed out, makeing it easy to find the right group/user. Is there
a way to get CentOS to a similar behaviour, making it easier to find
the culprit?
Bernhard
_______________________________________________
CentOS mailing list
CentOS@xxxxxxxxxx
http://lists.centos.org/mailman/listinfo/centos
