Hi
We're still unfortunately stuck on 2.4.15 pending various changecontrols on our side.
I have a work-around, however for 2.4.15 - in case anyone ever reads this ticket and has further problems.
By dramatically increasing the cachesize and idlcachesize entries in the relevant hdb database section, the cache is walked less often, and cleaned out less often. This reduces the number of times the problem could occur, which seems to have reduced the incidence from around 4* a day down to zero times in the last 20 days.
We are using cachesize of 20000 and idlsize of 60000. This increases memory size, but gives us stability.
Thanks,
Oskar
On 27 Mar 2009, at 09:52, openldap-its@OpenLDAP.org wrote:
*** THIS IS AN AUTOMATICALLY GENERATED REPLY ***
Thanks for your report to the OpenLDAP Issue Tracking System. Your report has been assigned the tracking number ITS#6040.
One of our support engineers will look at your report in due course. Note that this may take some time because our support engineers are volunteers. They only work on OpenLDAP when they have spare time.
If you need to provide additional information in regards to your issue report, you may do so by replying to this message. Note that any mail sent to openldap-its@openldap.org with (ITS#6040) in the subject will automatically be attached to the issue report.
mailto:openldap-its@openldap.org?subject=(ITS#6040)
You may follow the progress of this report by loading the following URL in a web browser: http://www.OpenLDAP.org/its/index.cgi?findid=6040
Please remember to retain your issue tracking number (ITS#6040) on any further messages you send to us regarding this report. If you don't then you'll just waste our time and yours because we won't be able to properly track the report.
Please note that the Issue Tracking System is not intended to be used to seek help in the proper use of OpenLDAP Software. Such requests will be closed.
OpenLDAP Software is user supported. http://www.OpenLDAP.org/support/
Copyright 1998-2007 The OpenLDAP Foundation, All Rights Reserved.