Re: index corruption (1164) still present in 2.0.15 with db 3.1.17 (ITS#1359)

[Kurt@OpenLDAP.org]

At 09:27 AM 2001-10-08, leifj@it.su.se wrote:
>On Fri, Oct 05, 2001 at 09:23:16AM -0700, Kurt D. Zeilenga wrote:
>> At 07:51 AM 2001-10-05, leifj@it.su.se wrote:
>> >On Wed, Oct 03, 2001 at 08:48:01AM -0700, Kurt D. Zeilenga wrote:
>> >> I haven't found anything yet in my digging...  still looking.
>> >
>> >Do you have tools to verify the consistency of the index (apart from
>> >slapindex) and report problems?
>> 
>> Unfornately not.  A simple verification (make sure all index
>> lists contained only unique ids in sorted order) wouldn't be
>> too hard to write (this is what id_check() basically does in
>> slapd).  Verification that the lists were consistent
>> with the entries would be much harder.
>> 
>
>This is getting really strange! Just to be on the safe side wrt clients
>I had my user management scripts produce ldif which I ran through ldapmodify
>instead of letting Net::LDAPS do the modifications directly.

I would obtain hex dumps of each generated request (by using
client-side or server-side debugging mechanisms, or by sniffing
the packets to see how they differ.  One would that if the
server is treating them differently, that they are in fact
significantly different.

Kurt