Hi
I have a OpenLDAP version 2.2 on ldbm database under unix with 2500 users. I'm aware upgrading is an option but it is not clear whether it would resolve my issue as stated below.
A search query returns a subset of the expected results.
I reindexed the data and there was no change in the results returned.
An update action to a user id not visible in the initial query becomes visible in subsequent queries.
After an export of the data(slapcat) and import (slapadd) to an empty data store,the same query as above returns the expected results.
After a period of time further queries return only a subset of the expected result set.
Please find below the slapd.conf and data base size
# Caches cachesize 100000 dbcachesize 10000000
index objectClass eq index cn eq index uid eq,sub index sn eq index groups eq
#user limitations -1 no limit sizelimit 10000 timelimit 60
Please find my data base files
-rw------- 1 openldap system 143360 Jul 19 21:09 cn.dbb -rw------- 1 openldap system 589824 Jul 19 14:34 dn2id.dbb -rw------- 1 openldap system 61440 Jul 19 21:09 groups.dbb -rw------- 1 openldap system 1368064 Jul 19 21:09 id2entry.dbb -rw------- 1 openldap system 8192 Jul 19 13:57 nextid.dbb -rw------- 1 openldap system 40960 Jul 19 21:09 objectClass.dbb -rw------- 1 openldap system 114688 Jul 19 21:09 sn.dbb -rw------- 1 openldap system 970752 Jul 19 21:09 uid.dbb
Any assistance would be greatly appreciated.
Regards, Kumuthiny
Australia Post is committed to providing our customers with excellent service. If we can assist you in any way please telephone 13 13 18 or visit our website.
The information contained in this e-mail communication may be proprietary, confidential or legally professionally privileged. It is intended exclusively for the individual or entity to which it is addressed. You should only read, disclose, re-transmit, copy, distribute, act in reliance on or commercialise the information if you are authorised to do so. Australia Post does not represent, warrant or guarantee the integrity of this e-mail communication has been maintained nor that the communication is free of errors, virus or interference.
If you are not the addressee or intended recipient please notify us by replying direct to the sender and then destroy any electronic or paper copy of this message. Any views expressed in this e-mail communication are taken to be those of the individual sender, except where the sender specifically attributes those views to Australia Post and is authorised to do so.
On 7/19/07, Srilakshmanan, Kumuthiny Kumuthiny.Srilakshmanan@auspost.com.au wrote:
Hi
I have a OpenLDAP version 2.2 on ldbm database under unix with 2500 users. I'm aware upgrading is an option but it is not clear whether it would resolve my issue as stated below.
A search query returns a subset of the expected results.
I reindexed the data and there was no change in the results returned.
An update action to a user id not visible in the initial query becomes visible in subsequent queries.
After an export of the data(slapcat) and import (slapadd) to an empty data store,the same query as above returns the expected results.
After a period of time further queries return only a subset of the expected result set.
Please find below the slapd.conf and data base size
# Caches cachesize 100000 dbcachesize 10000000
index objectClass eq index cn eq index uid eq,sub index sn eq index groups eq
#user limitations -1 no limit sizelimit 10000 timelimit 60
Well, if your searches are taking longer than sixty seconds, or you expect them to return more than ten thousand records, then things are okay. However, you're probably asking for help because that is not the case. :)
Please try to reproduce this problem with some level of debugging to see if, possibly, you're running into an err=80 (this will show up even in 256 logging), a bug where your database slows way down after some set number of queries (I had this problem with ldbm), or something a little less obvious.
It might be easier for you to ugprade to 2.3.x + bdb and see if that just works. With such a small database, migrating the data is going to be very, very easy.
matthew sporleder wrote:
On 7/19/07, Srilakshmanan, Kumuthiny Kumuthiny.Srilakshmanan@auspost.com.au wrote:
Hi
I have a OpenLDAP version 2.2 on ldbm database under unix with 2500 users. I'm aware upgrading is an option but it is not clear whether it would resolve my issue as stated below.
Well, if your searches are taking longer than sixty seconds, or you expect them to return more than ten thousand records, then things are okay. However, you're probably asking for help because that is not the case. :)
Please try to reproduce this problem with some level of debugging to see if, possibly, you're running into an err=80 (this will show up even in 256 logging), a bug where your database slows way down after some set number of queries (I had this problem with ldbm), or something a little less obvious.
There is no point in trying to reproduce this problem as-is. OpenLDAP 2.2 is obsolete and back-ldbm is known to spontaneously corrupt its indexes. Update to OpenLDAP 2.3/bdb, period.
openldap-software@openldap.org