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.
Cause: for an extended search filter component, the attribute value is cleared resulting with a comparison with an empty value
Consequence: invalid results (missing entries or entries not matching) to a search using extended search filter component
Fix: keep the attribute value without the heading/ending spaces
Results: an extended search retrieves all and only the entries matching the extended component
Description of problem:
Critical errors are logged after performing a simple search with a matching rule.
Version-Release number of selected component (if applicable):
389-ds-base-1.3.8.4-10.el7.x86_64
How reproducible:
always
Steps to Reproduce:
1. ldapsearch -xLLL -b dc=example,dc=com "(sn:de:=test)"
2. Check the error logs
Actual results:
[12/Aug/2018:22:02:52.915166781 +0200] - CRIT - list_candidates - NULL idl was recieved from filter_candidates_ext.[12/Aug/2018:22:02:52.928087622 +0200] - CRIT - list_candidates - Falling back to empty IDL set. This may affect your search results.
Expected results:
Additional info:
Also note that messages lack new line character:
ldap/servers/slapd/back-ldbm/filterindex.c
805 /*
806 * Assert we recieved a valid idl. If it was NULL, it means somewhere we failed
807 * during the dblayer interactions.
808 *
809 * idl_set requires a valid idl structure to generate the linked list of
810 * idls that we insert.
811 */
812 if (tmp == NULL) {
813 slapi_log_err(SLAPI_LOG_CRIT, "list_candidates", "NULL idl was recieved from filter_candidates_ext.");
814 slapi_log_err(SLAPI_LOG_CRIT, "list_candidates", "Falling back to empty IDL set. This may affect your search results.");
815 PR_ASSERT(tmp);
816 tmp = idl_alloc(0);
817 }
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.
https://access.redhat.com/errata/RHBA-2019:2152
Description of problem: Critical errors are logged after performing a simple search with a matching rule. Version-Release number of selected component (if applicable): 389-ds-base-1.3.8.4-10.el7.x86_64 How reproducible: always Steps to Reproduce: 1. ldapsearch -xLLL -b dc=example,dc=com "(sn:de:=test)" 2. Check the error logs Actual results: [12/Aug/2018:22:02:52.915166781 +0200] - CRIT - list_candidates - NULL idl was recieved from filter_candidates_ext.[12/Aug/2018:22:02:52.928087622 +0200] - CRIT - list_candidates - Falling back to empty IDL set. This may affect your search results. Expected results: Additional info: Also note that messages lack new line character: ldap/servers/slapd/back-ldbm/filterindex.c 805 /* 806 * Assert we recieved a valid idl. If it was NULL, it means somewhere we failed 807 * during the dblayer interactions. 808 * 809 * idl_set requires a valid idl structure to generate the linked list of 810 * idls that we insert. 811 */ 812 if (tmp == NULL) { 813 slapi_log_err(SLAPI_LOG_CRIT, "list_candidates", "NULL idl was recieved from filter_candidates_ext."); 814 slapi_log_err(SLAPI_LOG_CRIT, "list_candidates", "Falling back to empty IDL set. This may affect your search results."); 815 PR_ASSERT(tmp); 816 tmp = idl_alloc(0); 817 }