Marc Patermann wrote:
Hi,
Marc Patermann schrieb am 06.12.2010 16:40 Uhr:
what could the following possibly be?
This looks like something valgrind ought to be able to diagnose.
When I do a # slapadd -q -v -c -l dump.ldif to a SLES 11 SP1 (openldap 2.3.20) I get this after a few 1000 entries:
I have a fresh install of SLES 11 SP1 on a new machine. I installed 2.4.23. When I did the config and tried to put initial data (8(!) objects) into the server, I got glibc errors too.
# slapadd -q -c -v -l init.ldif added: ... ... _#################### 100.00% eta none elapsed none fast! Closing DB... *** glibc detected *** slapadd: free(): invalid pointer: 0x00007f89c0273210 *** ======= Backtrace: ========= /lib64/libc.so.6(+0x75018)[0x7f89bd242018] /lib64/libc.so.6(cfree+0x6c)[0x7f89bd246f6c] /usr/lib64/libdb-4.5.so(__ham_db_close+0x19)[0x7f89bf0d9139] /usr/lib64/libdb-4.5.so(__db_refresh+0x340)[0x7f89bf120a20] /usr/lib64/libdb-4.5.so(__db_close+0x51)[0x7f89bf120f91] /usr/lib64/libdb-4.5.so(__db_close_pp+0xd5)[0x7f89bf135445] slapadd(+0xc15eb)[0x7f89bfd065eb] ...
As I found out, when I deactivate the four index lines, it works. Each of these four lines causes an glibc error.
#index objectclass,uid,mail eq #index sn,cn,givenName sub,eq
#index dhcpHWAddress,dhcpClassData,dhcpOption eq #index entryCSN,entryUUID,zoneName eq
Hm? :(
Marc