Re: ldif2index: id 1023 already in next block (ITS#280)

[michael@roka.net]

Hello,

I can reproduce the problem:

Oct 26 15:18:57 nostromo ldif2index: id 1023 already in next block 
Oct 26 15:18:57 nostromo ldif2index: id 1025 already in next block 
Oct 26 15:19:11 nostromo ldif2index: id 2045 already in next block 
Oct 26 15:19:11 nostromo ldif2index: id 2050 already in next block 
Oct 26 15:19:11 nostromo ldif2index: id 2050 already in next block 
Oct 26 15:19:11 nostromo ldif2index: id 2051 already in next block 
Oct 26 15:19:26 nostromo ldif2index: id 3067 already in next block 
Oct 26 15:19:26 nostromo ldif2index: id 3068 already in next block 
Oct 26 15:19:26 nostromo ldif2index: id 3074 already in next block 
Oct 26 15:19:26 nostromo ldif2index: id 3074 already in next block 
Oct 26 15:19:26 nostromo ldif2index: id 3078 already in next block 
Oct 26 15:29:06 nostromo ldif2index: id 51921 already in next block 

My configuration: Linux 2.2.10, OpenLDAP 1.2.7, DB2 2.7.7, glibc 2.1.1.
It worked fine in 1.2.3 with DB2 2.7.4 and glibc 2.1.1, which is what
I use in production.  I was looking for an upgrade because 1.2.3 slapd
sometimes dies for me, but found I could no longer rebuild a dumped data
base with 1.2.7 because of the above problem.  The index file kept growing
for hours until I aborted the process.  This is with >280.000 entries.

Michael