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.

Bug 1379774

Summary: ldbsearch error - indexed and full searches both failed!
Product: Red Hat Enterprise Linux 7 Reporter: Amith <apeetham>
Component: sssdAssignee: SSSD Maintainers <sssd-maint>
Status: CLOSED DUPLICATE QA Contact: Steeve Goveas <sgoveas>
Severity: high Docs Contact:
Priority: high    
Version: 7.3CC: apeetham, cparadka, fidencio, grajaiya, jhrozek, kcleveng, lslebodn, mkosek, mzidek, pbrezina, sbose
Target Milestone: rc   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
See Doc Text for BZ#888739
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-02-01 13:09:19 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Amith 2016-09-27 15:53:25 UTC
Description of problem:
This issue was observed during the testing of BZ888739 on rhel-7.3. It is kind of a load testing on sssd when enumeration is ON against an ldap server with over 25000 users and bulk groups. With default timeout value, the sssd_be process gets KILLED and restarts, every 50-60 seconds.

The sysdb and timestamp cache gets updated, however when you run ldbsearch on them, the command fails with search error - Indexed and full searches both failed!

Version-Release number of selected component (if applicable):
sssd-1.14.0-43.el7

How reproducible:
Always

Steps to Reproduce:
1. Create 30,000 users in ldap server.

2. Set enumerate = true, in sssd.conf and restart the service.

3. Wait for some time and allow users to be cached.

4. Run ldbsearch on sysdb and timestamp cache:
  # ldbsearch -H /var/lib/sss/db/cache_LDAP.ldb


Actual results:
You should see error : Indexed and full searches both failed!

Expected results:


Additional info:

Comment 7 Lukas Slebodnik 2017-01-26 11:29:45 UTC
Upstream ticket:
https://fedorahosted.org/sssd/ticket/3266

Comment 8 Lukas Slebodnik 2017-01-26 11:30:46 UTC
master:
* e6a5f8c58539fc31fd81fac89cfc85703b4250ea
* 087162b85e191af51637904702813969b35eaadc 

sssd-1-14:
* 0606a71b698c4acf954ba7284e62acbd0aa5e52d
* 442985a7af2262fab57f56c7a8cd40af10081610

Comment 9 Jakub Hrozek 2017-02-01 13:09:19 UTC
I'm closing this bug as a duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=1396912 -- simply because they are both the same issue but #1396912 has the customer cases attached to it.

*** This bug has been marked as a duplicate of bug 1396912 ***