Folks, I've had a couple complaints of RHEL 5 machines using nscd/nss_ldap pegging a CPU at 100% with errors such as:
Dec 26 08:45:01 xxx nscd: nss_ldap: failed to bind to LDAP server ldap://yyy/: Can't contact LDAP server Dec 26 08:45:01 xxx nscd: nss_ldap: failed to bind to LDAP server ldap://yyy/: Can't contact LDAP server Dec 26 08:45:01 xxx nscd: nss_ldap: reconnecting to LDAP server (sleeping 4 seconds)... Dec 26 08:45:05 xxx nscd: nss_ldap: failed to bind to LDAP server ldap://yyy/: Can't contact LDAP server Dec 26 08:45:05 xxx nscd: nss_ldap: reconnecting to LDAP server (sleeping 8 seconds)... Dec 26 08:45:13 xxx nscd: nss_ldap: failed to bind to LDAP server ldap://yyy/: Can't contact LDAP server ... Dec 26 08:47:05 xxx nscd: nss_ldap: could not search LDAP server -Server is unavailable This behavior continues until we kill nscd and restart it. After restarting nscd the load will drop and it will be able to bind to the ldap server. The URI we are using runs through a load balancer to a pool of several ldap servers so I would imagine that reconnecting after a server glitch would be pretty fast. (LVS) Anyone know what's happening here? Jack Neely -- Jack Neely <[EMAIL PROTECTED]> Linux Czar, OIT Campus Linux Services Office of Information Technology, NC State University GPG Fingerprint: 1917 5AC1 E828 9337 7AA4 EA6B 213B 765F 3B6A 5B89 _______________________________________________ rhelv5-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/rhelv5-list
