Hide Forgot
This bug is created as a clone of upstream ticket: https://fedorahosted.org/389/ticket/260 The SSSD maintains a single connection to the LDAP server. Each of our requests to LDAP uses a paging control to handle situations where the returned values exceed the single-request limit. However, when we're under load and performing many concurrent requests, we see "Server is unwilling to perform(53), Simple Paged Results Search already in progress on this connection" It appears that 389 DS does not maintain paging controls on a per-request basis.
This request was not resolved in time for the current release. Red Hat invites you to ask your support representative to propose this request, if still desired, for consideration in the next release of Red Hat Enterprise Linux.
This request was erroneously removed from consideration in Red Hat Enterprise Linux 6.4, which is currently under development. This request will be evaluated for inclusion in Red Hat Enterprise Linux 6.4.
test coverage :: trac260 and trac260_1 in simplepaged
verified ##############################trac260############################### trac260: 389 DS does not support multiple paging controls on a single connection TestCase [trac260] result-> [PASS] #################################################################### ##############################trac260############################### trac260: 389 DS does not support multiple paging controls on a single connection check instance: [/usr/lib64/dirsrv/slapd-dell-pe2800-01] dn: supportedldapversion: 2 supportedldapversion: 3 instance [/usr/lib64/dirsrv/slapd-dell-pe2800-01] is alive on port [30541] Server up and running. Simple Paged Results request failed as expected. TestCase [trac260_1] result-> [PASS] #################################################################### version 389-ds-base-1.2.11.15-3.el6
Any chance we'll see a fix for this in 6.4? A vanilla IPA install with clients using sssd exhibits breakage because of this bug (or at least did in 6.3, haven't tested 6.4 just yet).
Shit, nevermind. Just saw the "fixed in version 389-ds-base-1.2.11.12-1.el6" after submitting the comment. Sorry.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHSA-2013-0503.html