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 1044181 - report unindexed internal searches
Summary: report unindexed internal searches
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: 389-ds-base
Version: 7.0
Hardware: Unspecified
OS: Unspecified
low
unspecified
Target Milestone: rc
: ---
Assignee: Rich Megginson
QA Contact: Viktor Ashirov
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-12-17 21:44 UTC by Nathan Kinder
Modified: 2020-09-13 20:36 UTC (History)
3 users (show)

Fixed In Version: 389-ds-base-1.3.3.1-1.el7
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-03-05 09:32:31 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github 389ds 389-ds-base issues 738 0 None None None 2020-09-13 20:36:48 UTC
Red Hat Product Errata RHSA-2015:0416 0 normal SHIPPED_LIVE Important: 389-ds-base security, bug fix, and enhancement update 2015-03-05 14:26:33 UTC

Description Nathan Kinder 2013-12-17 21:44:47 UTC 
This bug is created as a clone of upstream ticket:
https://fedorahosted.org/389/ticket/47401

We need to have a way to report unindexed internal searches, even if the user has not enabled access logging of internal searches.  For example, misconfiguration of the attribute uniqueness plugin or referential integrity could cause very expensive unindexed internal searches which would not be reported.  Perhaps some way to periodically log a warning in the errors log?
Comment 4 Amita Sharma 2014-12-30 07:53:14 UTC 
[root@dhcp201-126 export]# ldapmodify -x -D "cn=directory manager" -w Secret123 -p 389 -h localhost << EOF
dn: cn=config
> replace: nsslapd-plugin-logging
> nsslapd-plugin-logging: on
> -
> replace: nsslapd-accesslog-level
> nsslapd-accesslog-level: 4
> EOF
modifying entry "cn=config"

[root@dhcp201-126 export]# ldapmodify -x -D "cn=directory manager" -w Secret123 -p 389 -h localhost << EOF
> dn: cn=attribute uniqueness,cn=plugins,cn=config
> changetype: modify
> replace: nsslapd-pluginEnabled
> nsslapd-pluginEnabled: on
> -
> replace: uniqueness-attribute-name
> uniqueness-attribute-name: description
> EOF
modifying entry "cn=attribute uniqueness,cn=plugins,cn=config"


[root@dhcp201-126 export]# ldapmodify -a -D "cn=directory manager" -w Secret123 -p 389 -h localhost << EOF
> dn: cn=group,dc=example,dc=com
> objectclass: top
> objectclass: groupofuniquenames
> cn: group
> description: 0
> EOF
adding new entry "cn=group,dc=example,dc=com"

[root@dhcp201-126 export]# grep -i "Unindexed search" /var/log/dirsrv/slapd-dhcp201-126/errors

[root@dhcp201-126 export]# tail -f /var/log/dirsrv/slapd-dhcp201-126/errors
[30/Dec/2014:13:20:40 +051800] - slapd shutting down - waiting for 27 threads to terminate
[30/Dec/2014:13:20:40 +051800] - slapd shutting down - closing down internal subsystems and plugins
[30/Dec/2014:13:20:40 +051800] - Waiting for 4 database threads to stop
[30/Dec/2014:13:20:40 +051800] - All database threads now stopped
[30/Dec/2014:13:20:40 +051800] - slapd shutting down - freed 1 work q stack objects - freed 1 op stack objects
[30/Dec/2014:13:20:40 +051800] - slapd stopped.
[30/Dec/2014:13:20:41 +051800] - 389-Directory/1.3.3.1 B2014.351.2355 starting up
[30/Dec/2014:13:20:42 +051800] - I'm resizing my cache now...cache was 5120000 and is now 4096000
[30/Dec/2014:13:20:42 +051800] - slapd started.  Listening on All Interfaces port 389 for LDAP requests

Hence VERIFIED.
Comment 6 errata-xmlrpc 2015-03-05 09:32:31 UTC 
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://rhn.redhat.com/errata/RHSA-2015-0416.html
Note You need to log in before you can comment on or make changes to this bug.