Last message got embargoed for being over-length. Trimming this mail.
Trev
From: <Fong>, Trevor Fong
<trevor.fong@ubc.ca<mailto:trevor.fong@ubc.ca>>
Date: Thursday, December 11, 2014 at 9:03 AM
To: "mreynolds@redhat.com<mailto:mreynolds@redhat.com>"
<mreynolds@redhat.com<mailto:mreynolds@redhat.com>>,
"389-users@lists.fedoraproject.org<mailto:389-users@lists.fedoraproject.org>"
<389-users@lists.fedoraproject.org<mailto:389-users@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@redhat.com<mailto:mareynol@redhat.com>>
Reply-To: "mreynolds@redhat.com<mailto:mreynolds@redhat.com>"
<mreynolds@redhat.com<mailto:mreynolds@redhat.com>>
Date: Tuesday, December 9, 2014 at 3:21 PM
To: Trevor Fong <trevor.fong@ubc.ca<mailto:trevor.fong@ubc.ca>>,
"mreynolds@redhat.com<mailto:mreynolds@redhat.com>"
<mreynolds@redhat.com<mailto:mreynolds@redhat.com>>,
"389-users@lists.fedoraproject.org<mailto:389-users@lists.fedoraproject.org>"
<389-users@lists.fedoraproject.org<mailto:389-users@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