Dear list members,
i am running openlda 2.4.23 and i am facing memory usage problems (ITS 6660). I am not given the option to change to 2.4.23. Is there a patch to fix this problem?
Thanks once more.
--On Friday, July 29, 2011 12:51 PM -0300 Friedrich Locke friedrich.locke@gmail.com wrote:
Dear list members,
i am running openlda 2.4.23 and i am facing memory usage problems (ITS 6660). I am not given the option to change to 2.4.23. Is there a patch to fix this problem?
Given your stated database size, I sincerely doubt you are hitting the issue in ITS6660. You also fail to note any of your configuration settings. I personally don't see a slapd size of 63MB particularly large. Does it continually grow, or does it stay steady at 63MB?
--Quanah
--
Quanah Gibson-Mount Sr. Member of Technical Staff Zimbra, Inc A Division of VMware, Inc. -------------------- Zimbra :: the leader in open source messaging and collaboration
Hi all,
I have built OpenLDAP 2.4.26 linked against Cyrus SASL 2.1.24rc1. I'm conducting some tests now and if I use 'sasl-auxprops sasldb' I get a runtime exception (see attachment). I have tried everything and nothing seems to fix it. I'm using DB 4.8.30 and OpenLDAP and Cyrus SASL are both compiled against the same DB library. Is there any bug / patch / fix etc I could try/apply?
Thanks in advance.
Sergio.
On 30/07/11 21:01 +0100, Sergio NNX wrote:
Hi all,
I have built OpenLDAP 2.4.26 linked against Cyrus SASL 2.1.24rc1. I'm conducting some tests now and if I use 'sasl-auxprops sasldb' I get a runtime exception (see attachment). I have tried everything and nothing seems to fix it. I'm using DB 4.8.30 and OpenLDAP and Cyrus SASL are both compiled against the same DB library. Is there any bug / patch / fix etc I could try/apply?
Sergio,
Is this problem reproduceable with Cyrus SASL 2.1.23?
Is there some feature you are looking to use in 2.1.24rc1? I personally no longer consider it to be a release candidate, since there has been nearly two years of development since it was distributed.
Hi Dan,
Thanks for your answer. I haven't tried with Cyrus SASL 2.1.13. I'll do that tonight. Are you aware of any issue/problem/etc integrating Berkeley DB, SASL and OpenLDAP when authenticating against SASLDB?
Cheers.
Sergio.
---- Parliamentary ICT Houses of Parliament
Date: Mon, 1 Aug 2011 09:12:32 -0500 From: dwhite@olp.net To: sfhacker@hotmail.com CC: openldap-technical@openldap.org Subject: Re: OpenLDAP / Cyrus SASL - Runtime Exception
On 30/07/11 21:01 +0100, Sergio NNX wrote:
Hi all,
I have built OpenLDAP 2.4.26 linked against Cyrus SASL 2.1.24rc1. I'm conducting some tests now and if I use 'sasl-auxprops sasldb' I get a runtime exception (see attachment). I have tried everything and nothing seems to fix it. I'm using DB 4.8.30 and OpenLDAP and Cyrus SASL are both compiled against the same DB library. Is there any bug / patch / fix etc I could try/apply?
Sergio,
Is this problem reproduceable with Cyrus SASL 2.1.23?
Is there some feature you are looking to use in 2.1.24rc1? I personally no longer consider it to be a release candidate, since there has been nearly two years of development since it was distributed.
-- Dan White
Date: Mon, 1 Aug 2011 09:12:32 -0500 From: dwhite@olp.net To: sfhacker@hotmail.com CC: openldap-technical@openldap.org Subject: Re: OpenLDAP / Cyrus SASL - Runtime Exception
On 30/07/11 21:01 +0100, Sergio NNX wrote:
Hi all,
I have built OpenLDAP 2.4.26 linked against Cyrus SASL 2.1.24rc1. I'm conducting some tests now and if I use 'sasl-auxprops sasldb' I get a runtime exception (see attachment). I have tried everything and nothing seems to fix it. I'm using DB 4.8.30 and OpenLDAP and Cyrus SASL are both compiled against the same DB library. Is there any bug / patch / fix etc I could try/apply?
Sergio,
Is this problem reproduceable with Cyrus SASL 2.1.23?
Is there some feature you are looking to use in 2.1.24rc1? I personally no longer consider it to be a release candidate, since there has been nearly two years of development since it was distributed.
On 01/08/11 15:22 +0100, Sergio NNX wrote:
Hi Dan,
Thanks for your answer. I haven't tried with Cyrus SASL 2.1.13. I'll do that tonight. Are you aware of any issue/problem/etc integrating Berkeley DB, SASL and OpenLDAP when authenticating against SASLDB?
I have not personally used any on Windows. You may want to ask on the cyrus-sasl list. There has been some recent discussion of the Windows port.
Other than setting sasl-auxprops in your slapd.conf, you may also need to specify a sasldb_path setting in your *sasl* slapd.conf, where ever that may reside.
I also did what you suggest: sasldb_path in /etc/slapd.conf and still the same issue. Apparently, i'm not alone with this problem:
http://www.openldap.org/lists/openldap-technical/201008/msg00094.html
Any pointers/etc?
Thanks again.
Sergio.
---- Parliamentary ICT Houses of Parliament
Date: Mon, 1 Aug 2011 09:30:34 -0500 From: dwhite@olp.net To: sfhacker@hotmail.com Subject: Re: OpenLDAP / Cyrus SASL - Runtime Exception CC: openldap-technical@openldap.org
Date: Mon, 1 Aug 2011 09:12:32 -0500 From: dwhite@olp.net To: sfhacker@hotmail.com CC: openldap-technical@openldap.org Subject: Re: OpenLDAP / Cyrus SASL - Runtime Exception
On 30/07/11 21:01 +0100, Sergio NNX wrote:
Hi all,
I have built OpenLDAP 2.4.26 linked against Cyrus SASL 2.1.24rc1. I'm conducting some tests now and if I use 'sasl-auxprops sasldb' I get a runtime exception (see attachment). I have tried everything and nothing seems to fix it. I'm using DB 4.8.30 and OpenLDAP and Cyrus SASL are both compiled against the same DB library. Is there any bug / patch / fix etc I could try/apply?
Sergio,
Is this problem reproduceable with Cyrus SASL 2.1.23?
Is there some feature you are looking to use in 2.1.24rc1? I personally no longer consider it to be a release candidate, since there has been nearly two years of development since it was distributed.
On 01/08/11 15:22 +0100, Sergio NNX wrote:
Hi Dan,
Thanks for your answer. I haven't tried with Cyrus SASL 2.1.13. I'll do that tonight. Are you aware of any issue/problem/etc integrating Berkeley DB, SASL and OpenLDAP when authenticating against SASLDB?
I have not personally used any on Windows. You may want to ask on the cyrus-sasl list. There has been some recent discussion of the Windows port.
Other than setting sasl-auxprops in your slapd.conf, you may also need to specify a sasldb_path setting in your *sasl* slapd.conf, where ever that may reside.
-- Dan White
On 01/08/11 15:50 +0100, Sergio NNX wrote:
I also did what you suggest: sasldb_path in /etc/slapd.conf and still the same issue. Apparently, i'm not alone with this problem:
http://www.openldap.org/lists/openldap-technical/201008/msg00094.html
That problem was resolved, in my test environment, by specifying a sasl-auxprops setting in slapd.conf, which you seem to have already done. In theory it should work. The two wild cards in your scenario (from my perspective) are Windows, and 2.1.24rc1.
However, I'll defer to Howard's opinion on possible thread re-entrancy problems.
Ok. I cannot do anything about Windows (sorry for that). Then, you suggest that I should try Cyrus SASL 2.1.23 and see if it works fine?
Cheers.
Event Log Extract ---------------------
Description: Faulting application slapd.exe, version 0.0.0.0, time stamp 0x4e21b21f, faulting module ntdll.dll, version 6.0.6002.18005, time stamp 0x49e03821, exception code 0xc0000005, fault offset 0x00066796, process id 0x12a0, application start time 0x01cc4ab48e961035. Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Application Error" /> <EventID Qualifiers="0">1000</EventID> <Level>2</Level> <Task>100</Task> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2011-07-25T10:29:22.000Z" /> <EventRecordID>47013</EventRecordID> <Channel>Application</Channel> <Security /> </System> <EventData> <Data>slapd.exe</Data> <Data>0.0.0.0</Data> <Data>4e21b21f</Data> <Data>ntdll.dll</Data> <Data>6.0.6002.18005</Data> <Data>49e03821</Data> <Data>c0000005</Data> <Data>00066796</Data> <Data>12a0</Data> <Data>01cc4ab48e961035</Data> </EventData> </Event>
Date: Mon, 1 Aug 2011 10:05:07 -0500 From: dwhite@olp.net To: sfhacker@hotmail.com CC: openldap-technical@openldap.org Subject: Re: OpenLDAP / Cyrus SASL - Runtime Exception
On 01/08/11 15:50 +0100, Sergio NNX wrote:
I also did what you suggest: sasldb_path in /etc/slapd.conf and still the same issue. Apparently, i'm not alone with this problem:
http://www.openldap.org/lists/openldap-technical/201008/msg00094.htmlThat problem was resolved, in my test environment, by specifying a sasl-auxprops setting in slapd.conf, which you seem to have already done. In theory it should work. The two wild cards in your scenario (from my perspective) are Windows, and 2.1.24rc1.
However, I'll defer to Howard's opinion on possible thread re-entrancy problems.
-- Dan White
On 01/08/11 16:16 +0100, Sergio NNX wrote:
Ok. I cannot do anything about Windows (sorry for that). Then, you suggest that I should try Cyrus SASL 2.1.23 and see if it works fine?
My recommendation would be to try to do further trouble shooting to determine if this a cyrus sasl issue or not, and to take the issue to the cyrus sasl list if so. Alexy seems to have experience with the Windows port, and others may as well.
The error you've provided appears to be generated by slapd. Can you get a more extensive backtrace of the call stack? It would be helpful to know if it works with 2.1.23 or not.
--On Monday, August 01, 2011 9:12 AM -0500 Dan White dwhite@olp.net wrote:
Is there some feature you are looking to use in 2.1.24rc1? I personally no longer consider it to be a release candidate, since there has been nearly two years of development since it was distributed.
You should consider it a release candidate. It was buggy as can be. There has been constant development on it since it was released, but they have yet to release any new RC because of all the reworking they've been doing.
--Quanah
--
Quanah Gibson-Mount Sr. Member of Technical Staff Zimbra, Inc A Division of VMware, Inc. -------------------- Zimbra :: the leader in open source messaging and collaboration
It's still not working guys! I tried with Cyrus SASL 2.1.23 last night and the same issue. Does anyone have a working combination of DB, SASL and OpenLDAP i could download and test now?
thanks again.
Sergio.
---- Parliamentary ICT Houses of Parliament
Date: Mon, 1 Aug 2011 09:14:54 -0700 From: quanah@zimbra.com To: dwhite@olp.net; sfhacker@hotmail.com Subject: Re: OpenLDAP / Cyrus SASL - Runtime Exception CC: openldap-technical@openldap.org
--On Monday, August 01, 2011 9:12 AM -0500 Dan White dwhite@olp.net wrote:
Is there some feature you are looking to use in 2.1.24rc1? I personally no longer consider it to be a release candidate, since there has been nearly two years of development since it was distributed.
You should consider it a release candidate. It was buggy as can be. There has been constant development on it since it was released, but they have yet to release any new RC because of all the reworking they've been doing.
--Quanah
--
Quanah Gibson-Mount Sr. Member of Technical Staff Zimbra, Inc A Division of VMware, Inc.
Zimbra :: the leader in open source messaging and collaboration
On 02/08/11 15:14 +0100, Sergio NNX wrote:
It's still not working guys! I tried with Cyrus SASL 2.1.23 last night and the same issue. Does anyone have a working combination of DB, SASL and OpenLDAP i could download and test now?
thanks again.
Sergio.
Did you download binaries of these packages, and where from? If you built them, please provide build options and a description of your build environment.
openldap-technical@openldap.org
-
Dan White -
Friedrich Locke -
Quanah Gibson-Mount -
Sergio NNX