[389-users] 389-ds and Multi CPU's

Fong, Trevor trevor.fong at ubc.ca
Thu Dec 11 17:20:11 UTC 2014


Last message got embargoed for being over-length.  Trimming this mail.

Trev

From: <Fong>, Trevor Fong <trevor.fong at ubc.ca<mailto:trevor.fong at ubc.ca>>
Date: Thursday, December 11, 2014 at 9:03 AM
To: "mreynolds at redhat.com<mailto:mreynolds at redhat.com>" <mreynolds at redhat.com<mailto:mreynolds at redhat.com>>, "389-users at lists.fedoraproject.org<mailto:389-users at lists.fedoraproject.org>" <389-users at lists.fedoraproject.org<mailto:389-users at lists.fedoraproject.org>>
Subject: Re: [389-users] 389-ds and Multi CPU's

Hi Mark,

Sorry for the lack of response – I was off yesterday.
There were no errors when I made the updates, but when I restated the dirsrv’s, I got the following error:

[10/Dec/2014:23:52:20 -0800] - 389-Directory/1.2.11.15 B2014.300.2010 starting up
[10/Dec/2014:23:52:20 -0800] - attr_index_config: from ldbm instance init: Failed to parse idscanlimit info: 53:attr_index_parse_idlistsize: value inetOrgPerson
 violates syntax for attribute objectClass

Trev

From: Mark Reynolds <mareynol at redhat.com<mailto:mareynol at redhat.com>>
Reply-To: "mreynolds at redhat.com<mailto:mreynolds at redhat.com>" <mreynolds at redhat.com<mailto:mreynolds at redhat.com>>
Date: Tuesday, December 9, 2014 at 3:21 PM
To: Trevor Fong <trevor.fong at ubc.ca<mailto:trevor.fong at ubc.ca>>, "mreynolds at redhat.com<mailto:mreynolds at redhat.com>" <mreynolds at redhat.com<mailto:mreynolds at redhat.com>>, "389-users at lists.fedoraproject.org<mailto:389-users at lists.fedoraproject.org>" <389-users at lists.fedoraproject.org<mailto:389-users at lists.fedoraproject.org>>
Subject: Re: [389-users] 389-ds and Multi CPU's


On 12/09/2014 05:58 PM, Fong, Trevor wrote:
Hi Mark,

I’ve afraid adding nsIndexIDListScanLimit to cn=objectclass,cn=index,cn=userRoot,cn=ldbm database,cn=plugins,cn=config doesn’t seem to have any effect.  Did this:


dn: cn=objectclass,cn=index,cn=userRoot,cn=ldbm database,cn=plugins,cn=config

changetype: modify

add: nsIndexIDListScanLimit

nsIndexIDListScanLimit: limit=-1 type=eq values=inetOrgPerson

Hmm that's very strange, try this:

dn: cn=objectclass,cn=index,cn=userRoot,cn=ldbm database,cn=plugins,cn=config
changetype: modify
replace: nsIndexIDListScanLimit
nsIndexIDListScanLimit: limit=-1 type=eq values=inetOrgPerson
nsIndexIDListScanLimit: limit=-1 type=eq flags=AND values=inetOrgPerson

Also, is userRoot the mapping tree that refers to your "dc=<your dc>"?  I just want to make sure we are updating the correct objectclass index configuration entry.

This should get rid of those unindexed searches.  Is there anything in the 389 DS errors log regarding these settings?

Thanks,
Mark




-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.fedoraproject.org/pipermail/389-users/attachments/20141211/d24a43d3/attachment.html>


More information about the 389-users mailing list