On 7 April 2015 at 11:36, Saša-Stjepan Bakša ssbaksa@gmail.com wrote:
Hi,
It was long weekend with Easter holiday so...
To answer Mattes, and Ulrich first, I will do as suggested by you.
But something new first. If I have tried to add less data to database and then I have conducted the search. Till some point it works and then fails. It looks like when database is filed with more than some amount of data it stops to send data back.
To be sure that my build is not the culprit I have installed in parallel on similar server Ubuntu 14.04 with their slapd package (I know, it is not good but just for this test...) and this happened when I have tried this:
ldapsearch -h 10.14.252.104 -p 389 -D cn=admin,dc=spr -w password -s sub -a always -b dc=SPR objectClass=*
My build on centos 6.6 chrashed with this message:
----cut----
For test I have cut data from 2 mil lines to 300000 lines and database is now just 841 M in size (was 2,1 G)
root@spr2:/var/log# du -hs /var/lib/ldap/* 841M /var/lib/ldap/data.mdb 4.0K /var/lib/ldap/lock.mdb
And data is accessible:
----cut----- # search result search: 2 result: 0 Success
# numResponses: 22076 # numEntries: 22075
It looks like this is happening again:
http://www.openldap.org/lists/openldap-technical/201304/msg00198.html
Just to add, after deleting big database from centos build openldap server, ldapsearch for all objects works as expected - no crashes.
----cut---- # search result search: 2 result: 0 Success
# numResponses: 22076 # numEntries: 22075
Br
Sasa