nslcd ignoring operation timeout on RHEL6
- When the SSL connection to LDAP server is in ESTABLISHED state on a client but no data is passed through the socket, nslcd hangs and does not failover to a healthy LDAP URI. When a client detects the connection is not passing data through the TCP channel, even it is in ´ESTABLISHED´ state , the client should fail over to the secondary LDAP server. This behaviour is not seen for non-encrypted LDAP server connections.
- Red Hat Enterprise Linux 6, several minor versions
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.