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 918704 - db instance cn=monitor showing stats for other db instances
Summary: db instance cn=monitor showing stats for other db instances
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: 389-ds-base
Version: 7.0
Hardware: Unspecified
OS: Unspecified
medium
unspecified
Target Milestone: rc
: ---
Assignee: Rich Megginson
QA Contact: Sankar Ramalingam
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-03-06 18:15 UTC by Nathan Kinder
Modified: 2020-09-13 20:17 UTC (History)
4 users (show)

Fixed In Version: 389-ds-base-1.3.1.2-1.el7
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-06-13 09:25:33 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github 389ds 389-ds-base issues 465 0 None None None 2020-09-13 20:17:52 UTC

Description Nathan Kinder 2013-03-06 18:15:18 UTC 
This bug is created as a clone of upstream ticket:
https://fedorahosted.org/389/ticket/465

db instance foo - dbdir db/foo/
db instance foobar - dbdir db/foobar/

run an ldapsearch to get cn=monitor,cn=foo,cn=ldbm database,cn=plugins,cn=config

You will see entries like this:
dbfilename-14: foo/id2entry.db4
dbfilename-30: foobar/id2entry.db4

The problem is the logic in ldbm_back_monitor_instance_search():172 - it should see if the db filename begins with "instname/" instead of just seeing if it begins with "instname"
Comment 1 Rich Megginson 2013-10-01 23:25:57 UTC 
moving all ON_QA bugs to MODIFIED in order to add them to the errata (can't add bugs in the ON_QA state to an errata).  When the errata is created, the bugs should be automatically moved back to ON_QA.
Comment 5 Noriko Hosoi 2014-02-03 17:18:32 UTC 
Hi Amita,

What Sankar wrote is correct.  You are supposed to have 2 backends: the second one's backend name starts with the first one.  E.g.,
1st: nsslapd-backend: amita
2nd: nsslad-backend: amitasharma

As Sankar suggested, search "cn=monitor,cn=amita,cn=ldbm database,cn=plugins,cn=config".  If it does not return the info for cn=amitasharma, you could mark verified.
Comment 6 Noriko Hosoi 2014-02-03 17:47:12 UTC 
sorry for typo... :p
^2nd: nsslad-backend: amitasharma^2nd: nsslapd-backend: amitasharma^
Comment 7 Amita Sharma 2014-02-04 09:28:39 UTC 
Thanks Noriko and Sankar.

[root@dhcp201-149 ~]# ldapsearch -h localhost -p 389 -D "cn=directory manager" -w Secret123 -b "cn=monitor,cn=example,cn=ldbm database,cn=plugins,cn=config"

# monitor, example, ldbm database, plugins, config
dn: cn=monitor,cn=example,cn=ldbm database,cn=plugins,cn=config
objectClass: top
objectClass: extensibleObject
cn: monitor
database: ldbm database
readonly: 0
entrycachehits: 0
entrycachetries: 6
entrycachehitratio: 0
currententrycachesize: 0
maxentrycachesize: 10485760
currententrycachecount: 0
maxentrycachecount: -1
dncachehits: 0
dncachetries: 0
dncachehitratio: 0
currentdncachesize: 0
maxdncachesize: 10485760
currentdncachecount: 0
maxdncachecount: -1
dbfilename-12: example/id2entry.db
dbfilecachehit-12: 0
dbfilecachemiss-12: 2
dbfilepagein-12: 2
dbfilepageout-12: 0
dbfilename-16: example/entryrdn.db
dbfilecachehit-16: 5
dbfilecachemiss-16: 2
dbfilepagein-16: 2
dbfilepageout-16: 0


[root@dhcp201-149 ~]# ldapsearch -h localhost -p 389 -D "cn=directory manager" -w Secret123 -b "cn=monitor,cn=example2,cn=ldbm database,cn=plugins,cn=config"

# monitor, example2, ldbm database, plugins, config
dn: cn=monitor,cn=example2,cn=ldbm database,cn=plugins,cn=config
objectClass: top
objectClass: extensibleObject
cn: monitor
database: ldbm database
readonly: 0
entrycachehits: 0
entrycachetries: 4
entrycachehitratio: 0
currententrycachesize: 0
maxentrycachesize: 10485760
currententrycachecount: 0
maxentrycachecount: -1
dncachehits: 0
dncachetries: 0
dncachehitratio: 0
currentdncachesize: 0
maxdncachesize: 10485760
currentdncachecount: 0
maxdncachecount: -1
dbfilename-15: example2/id2entry.db
dbfilecachehit-15: 0
dbfilecachemiss-15: 2
dbfilepagein-15: 2
dbfilepageout-15: 0
dbfilename-30: example2/entryrdn.db
dbfilecachehit-30: 3
dbfilecachemiss-30: 2
dbfilepagein-30: 2
dbfilepageout-30: 0

Hence marking bug as VERIFIED
Comment 8 Ludek Smid 2014-06-13 09:25:33 UTC 
This request was resolved in Red Hat Enterprise Linux 7.0.

Contact your manager or support representative in case you have further questions about the request.
Note You need to log in before you can comment on or make changes to this bug.