Quanah Gibson-Mount quanah@zimbra.com writes:
--On August 19, 2010 8:21:01 PM +0200 Dieter Kluenter dieter@dkluenter.de wrote:
Quanah Gibson-Mount quanah@zimbra.com writes:
--On August 19, 2010 9:39:58 PM +0530 "Singh, Devender (GE Capital, consultant)" Devender.Singh2@ge.com wrote:
I agree with you. Please suggest me what to do for resolution of this issue.
Unfortunately, Dieter is ignoring potential issues with known problems with BDB, and the fact that a number of serious issues were fixed since OpenLDAP 2.4.16. Please go answer my list of questions I mailed you yesterday.
Quanah, I quite agree with you, there have been problems with early 2.4 versions of OpenLDAP and BDB, and I am quite aware of the fixed issues since 2.4.13. But let's solve hardware problems first, if there are any. If it is assured that hardware and filesystem as the culprid can be excluded, the focus can put on actual OpenLDAP versions.
Except for that fact that I know of people who saw this exact issue with earlier OpenLDAP versions, and we know for a fact there are issues with unpatched BDB 4.7, and there are issues with BDB 4.8 prior to 4.8.30. So it is *extremely* relevant to (a) ensure he is on a current release and (b) that he's using a valid BDB version.
I still quite agree, on the other hand, some of the systems I have installed with OpenLDAP-2.4.12/13 and db-4.2.52 and a few M entries are still running without any problem, even a system with db.4.3.x and a few 10k entries is still running. There are issues with some db versions, and there are issues with OpenLDAP versions, but to my experience, filesystem and hardware related issues should not be neglected.
-Dieter