Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
When nslcd was configured to use multiple LDAP servers, it failed to fall back to a different server in case the primary server could not be reached. This was due to nslcd trying to keep the first connection alive even when the connection was dropped. With this update, nslcd correctly falls back to a different server after loosing connection with the current one.
DescriptionJ.H.M. Dassen (Ray)
2011-04-01 09:55:02 UTC
Description of problem:
Customer is being hit by this bug:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=596983
(author of nss-pam-ldapd fixed in in 0.7.10, RHEL6 uses 0.7.5)
As they are using LDAP to distribute user information to their computing
nodes, this bug is quite critical for them: if the first LDAP server becomes
unreachable they loose all LDAP access from client. (The only workaround
being to restart nslcd on the system - it will fallback at the bind time).
Version-Release number of selected component (if applicable):
nss-pam-ldapd-0.7.5-3.el6
How reproducible:
100%
Steps to Reproduce:
1. Configure nslcd to use more than one LDAP server
2. Use iptables to drop connections to the first configured LDAP server
Actual results:
nslcd continues to attempt to connect to the first configured LDAP server.
Expected results:
nslcd falls over to using a different LDAP server than the first configured
one.
Comment 1J.H.M. Dassen (Ray)
2011-04-01 10:00:28 UTC
Technical note added. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
New Contents:
When nslcd was configured to use multiple LDAP servers, it failed to fall back to a different server in case the primary server could not be reached. This was due to nslcd trying to keep the first connection alive even when the connection was dropped. With this update, nslcd correctly falls back to a different server after loosing connection with the current one.
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.
http://rhn.redhat.com/errata/RHBA-2011-0796.html