Mailing-List: contact users-help@directory.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@directory.apache.org
Received-SPF: pass (herse.apache.org: domain of akarasulu@gmail.com designates
 66.249.92.170 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=beta;
        h=received:message-id:date:from:sender:to:subject:in-reply-to:mime-version:content-type:references:x-google-sender-auth;
        b=Zll83pxiJLPT1o4elowl21ex0Pla+wBFRDh8l87ruZ2IQX33RggJ3Sx9GUgRvL3alKWw8Ld171DZzkBuyu3HGnrF6dR20XAG9hZpzzs8K1H/2ZbO/40mCwdlM5XUpnF78cqNJeUJSQyCiN5KqXmbzbvUNQmrsJRResigroIVup8=
Message-ID: <a32f6b020705081616x3fdcfd1am697e331cd6a7a5a1@mail.gmail.com>
Date: Wed, 9 May 2007 02:16:40 +0300
From: "Alex Karasulu" <akarasulu@apache.org>
Sender: akarasulu@gmail.com
To: users@directory.apache.org
Subject: Re: Alias Problem "failed on search operation: attributeType w/ OID
 1.3.6.1.4.1.1466.115.121.1.12 not registered!"
In-Reply-To: <db90db6e0705081203n3f40e7e4o1c24758361354c95@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_24512_17317428.1178666200499"
References: <db90db6e0705081203n3f40e7e4o1c24758361354c95@mail.gmail.com>

------=_Part_24512_17317428.1178666200499
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Hi,

On 5/8/07, Martin Marcher <martin.marcher@gmail.com> wrote:
>
> Hello,
>
> freshly installed apacheds 1.5, I started the server with
> ./bin/server.init debug and the output stays empty upon searching with
> the line below so i can't really provide more info - better don't know
> how to provide more info. Using debian stable:


Hmmm does the output say that logging is not enabled?

I tried that search with the indexes from the
> examplePartitionConfiguration and without them (first not having
> indexes then adding them to the server.xml and restarting apacheds,
> still no go). Now am I missing something big here or why is this
> search not working?


Note that an index will need to be rebuilt if you added the index after
adding entries
to the server.  Basically the reason for this is that index entries are
added during add
operations. If the index is not present while adding entries then added then
these
entries will not have index entries for the values that are indexed and
search results
will fail since the server relies on the index which is empty and does not
hit the master
table.

You really need to make sure you add all the entries after creating the
index or use the
index building tool that comes with apacheds tools to populate a new index.

snip ...


> $ ldapsearch -h localhost -p 10389 -D "uid=admin,ou=system" -w secret
> -b "ou=system" -s one -x "(uid=admin)" dn
> # extended LDIF
> #
> # LDAPv3
> # base <ou=system> with scope oneLevel
> # filter: (uid=admin)
> # requesting: dn
> #
>
> # search result
> search: 2
> result: 33 Alias problem
> text: failed on search operation: attributeType w/ OID
> 1.3.6.1.4.1.1466.115.1
> 21.1.12 not registered!
>
> # numResponses: 1


snip ...

Hmmm this is odd because this OID corresponds to a syntax for the
distinguished name syntax and
not to an attributeType.  I guess I need to reproduce your situation and see
if I can hunt this down.

Alex

------=_Part_24512_17317428.1178666200499--