- openldap-bugs - openldap.org

(ITS#6229) make test blocked on test001-slapadd
by czybear＠qq.com 27 Jul '09

27 Jul '09

Full_Name: John Chen Version: 2.4.16/2.4.17 OS: RHEL AS 5.2 (Tikanga) x86)64 URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (117.88.156.12) [root@as5u2-64]# make test cd tests; make test make[1]: Entering directory `/home/install/ldap-2.4/openldap-2.4.16/tests' make[2]: Entering directory `/home/install/ldap-2.4/openldap-2.4.16/tests' Initiating LDAP tests for BDB... Cleaning up test run directory leftover from previous run. Running ./scripts/all... >>>>> Executing all LDAP tests for bdb >>>>> Starting test000-rootdse ... running defines.sh Starting slapd on TCP/IP port 9011... Using ldapsearch to retrieve the root DSE... Waiting 5 seconds for slapd to start... Using ldapsearch to retrieve the cn=Subschema... Using ldapsearch to retrieve the cn=Monitor... dn: objectClass: top objectClass: OpenLDAProotDSE structuralObjectClass: OpenLDAProotDSE configContext: cn=config namingContexts: o=OpenLDAP Project,l=Internet monitorContext: cn=Monitor supportedControl: 1.3.6.1.4.1.4203.1.9.1.1 supportedControl: 2.16.840.1.113730.3.4.18 supportedControl: 2.16.840.1.113730.3.4.2 supportedControl: 1.3.6.1.4.1.4203.1.10.1 supportedControl: 1.2.840.113556.1.4.319 supportedControl: 1.2.826.0.1.3344810.2.3 supportedControl: 1.3.6.1.1.13.2 supportedControl: 1.3.6.1.1.13.1 supportedControl: 1.3.6.1.1.12 supportedExtension: 1.3.6.1.4.1.4203.1.11.1 supportedExtension: 1.3.6.1.4.1.4203.1.11.3 supportedExtension: 1.3.6.1.1.8 supportedFeatures: 1.3.6.1.1.14 supportedFeatures: 1.3.6.1.4.1.4203.1.5.1 supportedFeatures: 1.3.6.1.4.1.4203.1.5.2 supportedFeatures: 1.3.6.1.4.1.4203.1.5.3 supportedFeatures: 1.3.6.1.4.1.4203.1.5.4 supportedFeatures: 1.3.6.1.4.1.4203.1.5.5 supportedLDAPVersion: 3 vendorName: The OpenLDAP Project <http://www.openldap.org/> entryDN: subschemaSubentry: cn=Subschema dn: cn=Subschema objectClass: top objectClass: subentry objectClass: subschema objectClass: extensibleObject cn: Subschema dn: cn=Monitor objectClass: monitorServer cn: Monitor description: This subtree contains monitoring/managing objects. description: This object contains information about this server. description: Most of the information is held in operational attributes, which must be explicitly requested. monitoredInfo: OpenLDAP: slapd 2.4.16 (Jul 23 2009 13:44:24) >>>>> Test succeeded >>>>> ./scripts/test000-rootdse completed OK. >>>>> Starting test001-slapadd ... running defines.sh Running slapadd to build slapd database... ========================================== Then blocked, and no moving any more ...

1 0

Re: (ITS#6228) test000-rootdse: slapd fails to start
by hyc＠symas.com 25 Jul '09

25 Jul '09

michael(a)stroeder.com wrote: > Full_Name: Michael Ströder > Version: HEAD > OS: openSUSE Linux 11.1 > URL: ftp://ftp.openldap.org/incoming/ > Submission from: (NULL) (84.163.115.191) > > > HEAD synced right now fails right in test000. Thanks, fixed. > > ----------- console output ----------- > > michael@nb2:/usr/src/michael/openldap/HEAD/openldap> make test > cd tests; make test > make[1]: Entering directory `/usr/src/michael/openldap/HEAD/openldap/tests' > make[2]: Entering directory `/usr/src/michael/openldap/HEAD/openldap/tests' > Initiating LDAP tests for BDB... > Cleaning up test run directory leftover from previous run. > Running ./scripts/all for bdb... >>>>>> Executing all LDAP tests for bdb >>>>>> Starting test000-rootdse for bdb... > running defines.sh > Starting slapd on TCP/IP port 9011... > Using ldapsearch to retrieve the root DSE... > Waiting 5 seconds for slapd to start... > Waiting 5 seconds for slapd to start... > Waiting 5 seconds for slapd to start... > Waiting 5 seconds for slapd to start... > Waiting 5 seconds for slapd to start... > Waiting 5 seconds for slapd to start... > ./scripts/test000-rootdse: line 66: kill: (2749) - No such process > ldap_sasl_bind(SIMPLE): Can't contact LDAP server (-1) >>>>>> Test failed >>>>>> ./scripts/test000-rootdse failed for bdb (exit 255) > make[2]: *** [bdb-mod] Error 255 > make[2]: Leaving directory `/usr/src/michael/openldap/HEAD/openldap/tests' > make[1]: *** [test] Error 2 > make[1]: Leaving directory `/usr/src/michael/openldap/HEAD/openldap/tests' > make: *** [test] Error 2 > > ----------- last lines of tests/testrun/slapd.1.log ----------- > > backend_startup_one: starting "cn=config" > config_back_db_open > config_build_entry: "cn=config" > config_build_entry: "cn=module{0}" > config_build_entry: "cn=module{1}" > config_build_entry: "cn=schema" > config_build_entry: "cn={0}core" > config_build_entry: "cn={1}cosine" > config_build_entry: "cn={2}corba" > config_build_entry: "cn={3}java" > config_build_entry: "cn={4}inetorgperson" > config_build_entry: "cn={5}misc" > config_build_entry: "cn={6}nis" > config_build_entry: "cn={7}openldap" > config_build_entry: "cn={8}duaconf" > config_build_entry: "cn={9}dyngroup" > config_build_entry: "cn={10}ppolicy" > config_build_entry: "olcDatabase={-1}frontend" > config_build_entry: "olcDatabase={0}config" > config_build_entry: "olcDatabase={1}bdb" > config_build_attrs: error 21 on olcDbCacheSize value #0 > config_build_entry: build "1000d" failed: "" > backend_startup_one: bi_db_open failed! (-1) > lt-slapd shutdown: initiated > ====> bdb_cache_release_all > lt-slapd destroy: freeing system resources. > slapd stopped. > > -- -- Howard Chu CTO, Symas Corp. http://www.symas.com Director, Highland Sun http://highlandsun.com/hyc/ Chief Architect, OpenLDAP http://www.openldap.org/project/

1 0

(ITS#6228) test000-rootdse: slapd fails to start
by michael＠stroeder.com 25 Jul '09

25 Jul '09

Full_Name: Michael Ströder Version: HEAD OS: openSUSE Linux 11.1 URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (84.163.115.191) HEAD synced right now fails right in test000. ----------- console output ----------- michael@nb2:/usr/src/michael/openldap/HEAD/openldap> make test cd tests; make test make[1]: Entering directory `/usr/src/michael/openldap/HEAD/openldap/tests' make[2]: Entering directory `/usr/src/michael/openldap/HEAD/openldap/tests' Initiating LDAP tests for BDB... Cleaning up test run directory leftover from previous run. Running ./scripts/all for bdb... >>>>> Executing all LDAP tests for bdb >>>>> Starting test000-rootdse for bdb... running defines.sh Starting slapd on TCP/IP port 9011... Using ldapsearch to retrieve the root DSE... Waiting 5 seconds for slapd to start... Waiting 5 seconds for slapd to start... Waiting 5 seconds for slapd to start... Waiting 5 seconds for slapd to start... Waiting 5 seconds for slapd to start... Waiting 5 seconds for slapd to start... ./scripts/test000-rootdse: line 66: kill: (2749) - No such process ldap_sasl_bind(SIMPLE): Can't contact LDAP server (-1) >>>>> Test failed >>>>> ./scripts/test000-rootdse failed for bdb (exit 255) make[2]: *** [bdb-mod] Error 255 make[2]: Leaving directory `/usr/src/michael/openldap/HEAD/openldap/tests' make[1]: *** [test] Error 2 make[1]: Leaving directory `/usr/src/michael/openldap/HEAD/openldap/tests' make: *** [test] Error 2 ----------- last lines of tests/testrun/slapd.1.log ----------- backend_startup_one: starting "cn=config" config_back_db_open config_build_entry: "cn=config" config_build_entry: "cn=module{0}" config_build_entry: "cn=module{1}" config_build_entry: "cn=schema" config_build_entry: "cn={0}core" config_build_entry: "cn={1}cosine" config_build_entry: "cn={2}corba" config_build_entry: "cn={3}java" config_build_entry: "cn={4}inetorgperson" config_build_entry: "cn={5}misc" config_build_entry: "cn={6}nis" config_build_entry: "cn={7}openldap" config_build_entry: "cn={8}duaconf" config_build_entry: "cn={9}dyngroup" config_build_entry: "cn={10}ppolicy" config_build_entry: "olcDatabase={-1}frontend" config_build_entry: "olcDatabase={0}config" config_build_entry: "olcDatabase={1}bdb" config_build_attrs: error 21 on olcDbCacheSize value #0 config_build_entry: build "1000d" failed: "" backend_startup_one: bi_db_open failed! (-1) lt-slapd shutdown: initiated ====> bdb_cache_release_all lt-slapd destroy: freeing system resources. slapd stopped.

1 0

Re: (ITS#6223) [patch] snprint() fix in guess_service_principal()
by jerry＠plainjoe.org 25 Jul '09

25 Jul '09

This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigB83678E9A284CB48B3D6C2FB Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Howard Chu wrote: > jerry(a)plainjoe.org wrote: >> Correction to the URL. Should be: >> ftp://ftp.openldap.org/incoming/openldap-2.4.16-guess_service_principa= l.diff >> >=20 > That file is zero bytes long. Did we run out of space on > ftp.openldap.org again? Howard, I've got update patches (more bug fixes related to the gssapi bind). I'll try uploading a new patch on Monday. cheers, jerry --------------enigB83678E9A284CB48B3D6C2FB Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFKawDfIR7qMdg1EfYRAt3iAKChKPg7VCwWuqevthDTvlcELJdTPgCg8pNq AIp/ts+OeQ2gfB4AlwehEAY= =RhWQ -----END PGP SIGNATURE----- --------------enigB83678E9A284CB48B3D6C2FB--

1 0

Re: ITS#6226
by test.007＠seznam.cz 25 Jul '09

25 Jul '09

Probably dup, sorry, I should have checked.

1 0

Re: (ITS#6222) Add "unlimited" option for cachesize settings
by hyc＠symas.com 24 Jul '09

24 Jul '09

quanah(a)zimbra.com wrote: > Full_Name: Quanah Gibson-Mount > Version: 2.4.17 > OS: NA > URL: ftp://ftp.openldap.org/incoming/ > Submission from: (NULL) (75.111.29.239) > > > Now that we have multiple cache sizes, it would be extremely useful, > particularly with dncachesize, to be able to specify an "unlimited" setting, so > that the 2.3 behavior can be easily replicated. Also so that people who have > systems with plenty of RAM can just set it once. Yeah, I guess it was kind of a bad idea to make the default 2.4 behavior differ from 2.3 here. Fixed in HEAD. > In particular, I've noticed in 2.3->2.4 upgrades, if dncachesize is particularly > small in relation to the size of the database, slapd is essentially unusable. > I'd rather see dncachesize default to unlimited if it isn't set (2.3 behavior), > and people can tune it down from there if they need to do so. This allows slapd > to remain usable without severely impacting the ability of slapd to function. > It is so bad, that it becomes impossible to modify cn=config via ldap commands, > and you have to stop slapd and manually hack the cn=config text files to return > slapd to a usable state. > -- -- Howard Chu CTO, Symas Corp. http://www.symas.com Director, Highland Sun http://highlandsun.com/hyc/ Chief Architect, OpenLDAP http://www.openldap.org/project/

1 0

Re: (ITS#6225) GSSAPI support for client library (fixes)
by hyc＠symas.com 24 Jul '09

24 Jul '09

mimir(a)samba.org wrote: > Full_Name: Rafal Szczesniak > Version: Stable (2.4.16) > OS: GNU/Linux > URL: http://www.samba.org/~mimir/gssapi-bugfix.diff > Submission from: (NULL) (67.51.54.234) > > > This is a bugfix patch for OpenLDAP's gssapi support. > One of these patches appears to duplicate ITS#6092. As the original author of this code, could you also take a look at #6091 and #6093? -- -- Howard Chu CTO, Symas Corp. http://www.symas.com Director, Highland Sun http://highlandsun.com/hyc/ Chief Architect, OpenLDAP http://www.openldap.org/project/

1 0

Re: (ITS#6223) [patch] snprint() fix in guess_service_principal()
by hyc＠symas.com 24 Jul '09

24 Jul '09

jerry(a)plainjoe.org wrote: > Correction to the URL. Should be: > ftp://ftp.openldap.org/incoming/openldap-2.4.16-guess_service_principal.diff That file is zero bytes long. Did we run out of space on ftp.openldap.org again? -- -- Howard Chu CTO, Symas Corp. http://www.symas.com Director, Highland Sun http://highlandsun.com/hyc/ Chief Architect, OpenLDAP http://www.openldap.org/project/

1 0

Re: (ITS#6221) slapd segfault in SSL_CTX_set_info_callback
by steve＠falchion.com 24 Jul '09

24 Jul '09

Thanks for the encouragement Michael :) For those who find this in searches to come, I compiled OpenSSL (0.9.8k) myself and the problem is resolved. Not sure if this is a bug fixed between 0.9.8h and 0.9.8k or something weird that IBM did when building the package, but all is well now. Steve=20 On Fri, 2009-07-24 at 13:24 +0200, Michael Str=C3=B6der wrote: > steve(a)falchion.com wrote: > > Now you might tell me (as you've already implied) to compile my own SSL > > libraries, >=20 > Being in your situation I'd try that. >=20 > > which I may try, but doing so opens me up to a world of > > interop issues as IBM tends to compile their tools with links to > > specific versions of shared libraries (I've been there and done that in > > AIX this year once already). >=20 > You could build all the necessary libs (Berkeley DB, OpenSSL, > cyrus-sasl, heimdal etc.) and install them in a separate prefix without > conflicting with any pre-installed libs. I'd go that route and did that > on e.g. old Solaris platforms. And I think it would be feasible for me > even though I'm not an C programmer. >=20 > > Do I sound frustrated yet? Cause I am... >=20 > Sometimes things are hard. But just don't give up! >=20 > Ciao, Michael.

1 0

Re: (ITS#6227) autogroup overlay breaks all searches
by hyc＠symas.com 24 Jul '09

24 Jul '09

Fixed now in CVS HEAD. mbuschman(a)cashnetusa.com wrote: > Full_Name: Marshall Buschman > Version: 2.4.17 > OS: Debian Etch > URL: ftp://ftp.openldap.org/incoming/ > Submission from: (NULL) (38.98.177.132) > > I'm using OpenLDAP 2.4.17 with bdb 4.7 Debian Lenny. I've enabled the > autogroup overlay, and I get the following error when I do an ldapsearch: > > $ ldapsearch -x -H "ldap://ldapserver" -b dc=cashnetusa,dc=com > # extended LDIF > ... > # search result > search: 2 > result: 53 Server is unwilling to perform > text: operation not supported within namingContext > > Relevant config: > ---------------------------------------------- > moduleload autogroup > > database bdb > suffix "dc=cashnetusa,dc=com" > > overlay autogroup > autogroup-attrset groupOfURLs memberURL member > ---------------------------------------------- > > OpenLDAP does start normally without the overlay. > -- -- Howard Chu CTO, Symas Corp. http://www.symas.com Director, Highland Sun http://highlandsun.com/hyc/ Chief Architect, OpenLDAP http://www.openldap.org/project/

1 0

Re: (ITS#6227) autogroup overlay breaks all searches
by mbuschman＠cashnetusa.com 24 Jul '09

24 Jul '09

OS is Debian Lenny, not Debian Etch. Apologies. openldap-its(a)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#6227. > > 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(a)openldap.org with (ITS#6227) > in the subject will automatically be attached to the issue report. > > mailto:openldap-its@openldap.org?subject=(ITS#6227) > > 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=6227 > > Please remember to retain your issue tracking number (ITS#6227) > 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. > >

1 0

(ITS#6227) autogroup overlay breaks all searches
by mbuschman＠cashnetusa.com 24 Jul '09

24 Jul '09

Full_Name: Marshall Buschman Version: 2.4.17 OS: Debian Etch URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (38.98.177.132) I'm using OpenLDAP 2.4.17 with bdb 4.7 Debian Lenny. I've enabled the autogroup overlay, and I get the following error when I do an ldapsearch: $ ldapsearch -x -H "ldap://ldapserver" -b dc=cashnetusa,dc=com # extended LDIF ... # search result search: 2 result: 53 Server is unwilling to perform text: operation not supported within namingContext Relevant config: ---------------------------------------------- moduleload autogroup database bdb suffix "dc=cashnetusa,dc=com" overlay autogroup autogroup-attrset groupOfURLs memberURL member ---------------------------------------------- OpenLDAP does start normally without the overlay.

1 0

Re: (ITS#6221) slapd segfault in SSL_CTX_set_info_callback
by michael＠stroeder.com 24 Jul '09

24 Jul '09

steve(a)falchion.com wrote: > Now you might tell me (as you've already implied) to compile my own SSL > libraries, Being in your situation I'd try that. > which I may try, but doing so opens me up to a world of > interop issues as IBM tends to compile their tools with links to > specific versions of shared libraries (I've been there and done that in > AIX this year once already). You could build all the necessary libs (Berkeley DB, OpenSSL, cyrus-sasl, heimdal etc.) and install them in a separate prefix without conflicting with any pre-installed libs. I'd go that route and did that on e.g. old Solaris platforms. And I think it would be feasible for me even though I'm not an C programmer. > Do I sound frustrated yet? Cause I am... Sometimes things are hard. But just don't give up! Ciao, Michael.

1 0

Re: (ITS#6221) slapd segfault in SSL_CTX_set_info_callback
by steve＠falchion.com 23 Jul '09

23 Jul '09

Thank-you, that is much more helpful. I apologize for my rant. I'll join that mailing list and post my issue there. Thanks, Steve On Thu, 2009-07-23 at 15:23 -0700, Howard Chu wrote: > Steve Paras-Charlton wrote: > > Thanks, that was sooo helpful. > > > > What I'm trying to do is port your software package to a platform where > > it obviously fails to work properly using the vendor's supplied SSL > > libraries, and you're giving me a PFO. > > The ITS is for tracking problems in the actual OpenLDAP code base. Since > you're not reporting an actual issue in OpenLDAP code, this is the wrong forum > for this discussion. > > You can get help on interoperability issues elsewhere, e.g. the > openldap-technical mailing list. > > > So now I get to go to IBM and say "your library is broken but I can't > > tell you how/why" (gee... I wonder how that call will go) or abandon > > open source and install their LDAP server package (which is what they'll > > tell me to do anyhow). > > > > Now you might tell me (as you've already implied) to compile my own SSL > > libraries, which I may try, but doing so opens me up to a world of > > interop issues as IBM tends to compile their tools with links to > > specific versions of shared libraries (I've been there and done that in > > AIX this year once already). > > > Do I sound frustrated yet? Cause I am... > > > > Sorry to anyone else who reads this rant. > > You obviously have to ask the right questions to the right people who can > actually help you. We can't fix your OpenSSL build for you. > > > > Steve > > > > On Thu, 2009-07-23 at 14:15 -0700, Howard Chu wrote: > >> Steve Paras-Charlton wrote: > >>> > >>> I tried re-compiling with CC="gcc -g" and got the following backtrace > >>> from gdb: > >>> > >>> Program received signal SIGSEGV, Segmentation fault. > >>> [Switching to Thread 1] > >>> 0xd26d07d0 in SSL_CTX_set_info_callback () > >>> > >>> from /LDAP/build/openldap-2.4.16/libraries/libldap_r/.libs/libldap_r.a(libldap_r-2.4.so.2) > >>> (gdb) bt > >>> #0 0xd26d07d0 in SSL_CTX_set_info_callback () > >>> > >>> from /LDAP/build/openldap-2.4.16/libraries/libldap_r/.libs/libldap_r.a(libldap_r-2.4.so.2) > >>> #1 0xd26cdedc in tlso_ctx_init (lo=0x200c087c, lt=0x2ff22970, > >>> is_server=1) at tls_o.c:320 > >>> #2 0xd26ca50c in ldap_int_tls_init_ctx (lo=0x200c087c, is_server=1) at > >>> tls2.c:245 > >>> #3 0xd26cc1cc in ldap_pvt_tls_set_option (ld=0x200c0878, option=24591, > >>> arg=0x2ff22ae8) at tls2.c:800 > >>> #4 0x10001f90 in main (argc=9, argv=0x2ff22b94) at main.c:826 > >>> > >>> This one seems much more useful from a debugging perspective. > >>> > >>> I noticed that the configure program has some options along the lines of > >>> "--with-PIC" which defaults to "both PIC and non-PIC". Could I use this > >>> to help debug the issue perhaps? How would I use it (not sure what > >>> options it takes). > >> > >> This trace is the kind that we would normally look for, yes. But the crash is > >> in an OpenSSL function, and you haven't got debug symbols for that since you > >> haven't recompiled that yet. Anyway, it still has nothing to do with OpenLDAP, > >> your OpenSSL library is broken. Since this is not an OpenLDAP bug this ITS > >> will be closed. > >> > > > > > >

1 0

2.4.17 - autogroup overlay breaks searches
by Marshall Buschman 23 Jul '09

23 Jul '09

Hello All: I'm running OpenLDAP 2.4.17+bdb 4.7 on Debian Lenny. I've enabled the autogroup overlay, and I get the following when I do an ldapsearch. Disabling the overlay does fix the issue, but I do need the functionality the overlay provides. $ ldapsearch -x -H "ldap://ldapserver" -b dc=cashnetusa,dc=com # extended LDIF ... # search result search: 2 result: 53 Server is unwilling to perform text: operation not supported within namingContext Relevant config: ---------------------------------------------- moduleload autogroup database bdb suffix "dc=cashnetusa,dc=com" overlay autogroup autogroup-attrset posixGroup memberURL member ---------------------------------------------- Help? -Marshall Buschman

2 1

Re: (ITS#6200)
by hyc＠symas.com 23 Jul '09

23 Jul '09

imf(a)u.washington.edu wrote: > The changes made to 2.4.17 seem to have fixed the crashes in the caching > module. Thanks for that. > > We still are able to crash 2.4.17, however. It only happens after a heavy > load is placed on the producer for>24 hours continuous. Unfortunately, > we've not been able to get good tracebacks. They all look like this, > > (gdb) where > #0 0x00869410 in __kernel_vsyscall () > #1 0x00390d80 in raise () from /lib/libc.so.6 > #2 0x00392691 in abort () from /lib/libc.so.6 > #3 0x0038a1fb in __assert_fail () from /lib/libc.so.6 > #4 0x0808d532 in malloc () > #5 0x0822c93f in ?? () > #6 0x0822c933 in ?? () > #7 0x00000039 in ?? () > #8 0x0822c908 in ?? () > #9 0x00000000 in ?? () > > The producer slowly grows its memory footprint. I can't tell if it's from > just normal operations or memory leaks. I suspect it's a little of both. > The end result, as you can see from the core above, is that there's likely > some corrupted (or unfreed) memory somewhere. Sorry I can't nail it down > further. There's not enough information here. An assert is always accompanied by an error message on stderr; we need to see the actual error message. There are no symbols in the stack trace pertaining to slapd itself. You seem to be running a stripped binary. Please provide a trace using a non-stripped binary that was compiled with -g (debug symbols enabled). > > The load profile that we placed on the server is documented in my prior > report. See above. -- -- Howard Chu CTO, Symas Corp. http://www.symas.com Director, Highland Sun http://highlandsun.com/hyc/ Chief Architect, OpenLDAP http://www.openldap.org/project/

1 0

Re: (ITS#6221) slapd segfault in SSL_CTX_set_info_callback
by hyc＠symas.com 23 Jul '09

23 Jul '09

Steve Paras-Charlton wrote: > Thanks, that was sooo helpful. > > What I'm trying to do is port your software package to a platform where > it obviously fails to work properly using the vendor's supplied SSL > libraries, and you're giving me a PFO. The ITS is for tracking problems in the actual OpenLDAP code base. Since you're not reporting an actual issue in OpenLDAP code, this is the wrong forum for this discussion. You can get help on interoperability issues elsewhere, e.g. the openldap-technical mailing list. > So now I get to go to IBM and say "your library is broken but I can't > tell you how/why" (gee... I wonder how that call will go) or abandon > open source and install their LDAP server package (which is what they'll > tell me to do anyhow). > > Now you might tell me (as you've already implied) to compile my own SSL > libraries, which I may try, but doing so opens me up to a world of > interop issues as IBM tends to compile their tools with links to > specific versions of shared libraries (I've been there and done that in > AIX this year once already). > Do I sound frustrated yet? Cause I am... > > Sorry to anyone else who reads this rant. You obviously have to ask the right questions to the right people who can actually help you. We can't fix your OpenSSL build for you. > > Steve > > On Thu, 2009-07-23 at 14:15 -0700, Howard Chu wrote: >> Steve Paras-Charlton wrote: >>> >>> I tried re-compiling with CC="gcc -g" and got the following backtrace >>> from gdb: >>> >>> Program received signal SIGSEGV, Segmentation fault. >>> [Switching to Thread 1] >>> 0xd26d07d0 in SSL_CTX_set_info_callback () >>> >>> from /LDAP/build/openldap-2.4.16/libraries/libldap_r/.libs/libldap_r.a(libldap_r-2.4.so.2) >>> (gdb) bt >>> #0 0xd26d07d0 in SSL_CTX_set_info_callback () >>> >>> from /LDAP/build/openldap-2.4.16/libraries/libldap_r/.libs/libldap_r.a(libldap_r-2.4.so.2) >>> #1 0xd26cdedc in tlso_ctx_init (lo=0x200c087c, lt=0x2ff22970, >>> is_server=1) at tls_o.c:320 >>> #2 0xd26ca50c in ldap_int_tls_init_ctx (lo=0x200c087c, is_server=1) at >>> tls2.c:245 >>> #3 0xd26cc1cc in ldap_pvt_tls_set_option (ld=0x200c0878, option=24591, >>> arg=0x2ff22ae8) at tls2.c:800 >>> #4 0x10001f90 in main (argc=9, argv=0x2ff22b94) at main.c:826 >>> >>> This one seems much more useful from a debugging perspective. >>> >>> I noticed that the configure program has some options along the lines of >>> "--with-PIC" which defaults to "both PIC and non-PIC". Could I use this >>> to help debug the issue perhaps? How would I use it (not sure what >>> options it takes). >> >> This trace is the kind that we would normally look for, yes. But the crash is >> in an OpenSSL function, and you haven't got debug symbols for that since you >> haven't recompiled that yet. Anyway, it still has nothing to do with OpenLDAP, >> your OpenSSL library is broken. Since this is not an OpenLDAP bug this ITS >> will be closed. >> > > -- -- Howard Chu CTO, Symas Corp. http://www.symas.com Director, Highland Sun http://highlandsun.com/hyc/ Chief Architect, OpenLDAP http://www.openldap.org/project/

1 0

Re: (ITS#6221) slapd segfault in SSL_CTX_set_info_callback
by steve＠falchion.com 23 Jul '09

23 Jul '09

Thanks, that was sooo helpful. What I'm trying to do is port your software package to a platform where it obviously fails to work properly using the vendor's supplied SSL libraries, and you're giving me a PFO. So now I get to go to IBM and say "your library is broken but I can't tell you how/why" (gee... I wonder how that call will go) or abandon open source and install their LDAP server package (which is what they'll tell me to do anyhow). Now you might tell me (as you've already implied) to compile my own SSL libraries, which I may try, but doing so opens me up to a world of interop issues as IBM tends to compile their tools with links to specific versions of shared libraries (I've been there and done that in AIX this year once already). Do I sound frustrated yet? Cause I am... Sorry to anyone else who reads this rant. Steve On Thu, 2009-07-23 at 14:15 -0700, Howard Chu wrote: > Steve Paras-Charlton wrote: > > > > I tried re-compiling with CC="gcc -g" and got the following backtrace > > from gdb: > > > > Program received signal SIGSEGV, Segmentation fault. > > [Switching to Thread 1] > > 0xd26d07d0 in SSL_CTX_set_info_callback () > > > > from /LDAP/build/openldap-2.4.16/libraries/libldap_r/.libs/libldap_r.a(libldap_r-2.4.so.2) > > (gdb) bt > > #0 0xd26d07d0 in SSL_CTX_set_info_callback () > > > > from /LDAP/build/openldap-2.4.16/libraries/libldap_r/.libs/libldap_r.a(libldap_r-2.4.so.2) > > #1 0xd26cdedc in tlso_ctx_init (lo=0x200c087c, lt=0x2ff22970, > > is_server=1) at tls_o.c:320 > > #2 0xd26ca50c in ldap_int_tls_init_ctx (lo=0x200c087c, is_server=1) at > > tls2.c:245 > > #3 0xd26cc1cc in ldap_pvt_tls_set_option (ld=0x200c0878, option=24591, > > arg=0x2ff22ae8) at tls2.c:800 > > #4 0x10001f90 in main (argc=9, argv=0x2ff22b94) at main.c:826 > > > > This one seems much more useful from a debugging perspective. > > > > I noticed that the configure program has some options along the lines of > > "--with-PIC" which defaults to "both PIC and non-PIC". Could I use this > > to help debug the issue perhaps? How would I use it (not sure what > > options it takes). > > This trace is the kind that we would normally look for, yes. But the crash is > in an OpenSSL function, and you haven't got debug symbols for that since you > haven't recompiled that yet. Anyway, it still has nothing to do with OpenLDAP, > your OpenSSL library is broken. Since this is not an OpenLDAP bug this ITS > will be closed. >

1 0

Re: (ITS#6221) slapd segfault in SSL_CTX_set_info_callback
by hyc＠symas.com 23 Jul '09

23 Jul '09

Steve Paras-Charlton wrote: > > I tried re-compiling with CC="gcc -g" and got the following backtrace > from gdb: > > Program received signal SIGSEGV, Segmentation fault. > [Switching to Thread 1] > 0xd26d07d0 in SSL_CTX_set_info_callback () > > from /LDAP/build/openldap-2.4.16/libraries/libldap_r/.libs/libldap_r.a(libldap_r-2.4.so.2) > (gdb) bt > #0 0xd26d07d0 in SSL_CTX_set_info_callback () > > from /LDAP/build/openldap-2.4.16/libraries/libldap_r/.libs/libldap_r.a(libldap_r-2.4.so.2) > #1 0xd26cdedc in tlso_ctx_init (lo=0x200c087c, lt=0x2ff22970, > is_server=1) at tls_o.c:320 > #2 0xd26ca50c in ldap_int_tls_init_ctx (lo=0x200c087c, is_server=1) at > tls2.c:245 > #3 0xd26cc1cc in ldap_pvt_tls_set_option (ld=0x200c0878, option=24591, > arg=0x2ff22ae8) at tls2.c:800 > #4 0x10001f90 in main (argc=9, argv=0x2ff22b94) at main.c:826 > > This one seems much more useful from a debugging perspective. > > I noticed that the configure program has some options along the lines of > "--with-PIC" which defaults to "both PIC and non-PIC". Could I use this > to help debug the issue perhaps? How would I use it (not sure what > options it takes). This trace is the kind that we would normally look for, yes. But the crash is in an OpenSSL function, and you haven't got debug symbols for that since you haven't recompiled that yet. Anyway, it still has nothing to do with OpenLDAP, your OpenSSL library is broken. Since this is not an OpenLDAP bug this ITS will be closed. -- -- Howard Chu CTO, Symas Corp. http://www.symas.com Director, Highland Sun http://highlandsun.com/hyc/ Chief Architect, OpenLDAP http://www.openldap.org/project/

1 0

ITS#6226
by masarati＠aero.polimi.it 23 Jul '09

23 Jul '09

Duplicate of ITS#5941? p.

1 0

Re: (ITS#6221) slapd segfault in SSL_CTX_set_info_callback
by steve＠falchion.com 23 Jul '09

23 Jul '09

I tried re-compiling with CC="gcc -g" and got the following backtrace from gdb: Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 1] 0xd26d07d0 in SSL_CTX_set_info_callback () from /LDAP/build/openldap-2.4.16/libraries/libldap_r/.libs/libldap_r.a(libldap_r-2.4.so.2) (gdb) bt #0 0xd26d07d0 in SSL_CTX_set_info_callback () from /LDAP/build/openldap-2.4.16/libraries/libldap_r/.libs/libldap_r.a(libldap_r-2.4.so.2) #1 0xd26cdedc in tlso_ctx_init (lo=0x200c087c, lt=0x2ff22970, is_server=1) at tls_o.c:320 #2 0xd26ca50c in ldap_int_tls_init_ctx (lo=0x200c087c, is_server=1) at tls2.c:245 #3 0xd26cc1cc in ldap_pvt_tls_set_option (ld=0x200c0878, option=24591, arg=0x2ff22ae8) at tls2.c:800 #4 0x10001f90 in main (argc=9, argv=0x2ff22b94) at main.c:826 This one seems much more useful from a debugging perspective. I noticed that the configure program has some options along the lines of "--with-PIC" which defaults to "both PIC and non-PIC". Could I use this to help debug the issue perhaps? How would I use it (not sure what options it takes). Thanks, Steve

1 0

(ITS#6200)
by imf＠u.washington.edu 23 Jul '09

23 Jul '09

The changes made to 2.4.17 seem to have fixed the crashes in the caching module. Thanks for that. We still are able to crash 2.4.17, however. It only happens after a heavy load is placed on the producer for >24 hours continuous. Unfortunately, we've not been able to get good tracebacks. They all look like this, (gdb) where #0 0x00869410 in __kernel_vsyscall () #1 0x00390d80 in raise () from /lib/libc.so.6 #2 0x00392691 in abort () from /lib/libc.so.6 #3 0x0038a1fb in __assert_fail () from /lib/libc.so.6 #4 0x0808d532 in malloc () #5 0x0822c93f in ?? () #6 0x0822c933 in ?? () #7 0x00000039 in ?? () #8 0x0822c908 in ?? () #9 0x00000000 in ?? () The producer slowly grows its memory footprint. I can't tell if it's from just normal operations or memory leaks. I suspect it's a little of both. The end result, as you can see from the core above, is that there's likely some corrupted (or unfreed) memory somewhere. Sorry I can't nail it down further. The load profile that we placed on the server is documented in my prior report. See above. --- Tracy Stenvik University Computing Services 354843. University of Washington email: imf(a)u.washington.edu voice: (206) 685-3344

1 0

(ITS#6226) Double free() with translucent+rwm
by test.007＠seznam.cz 23 Jul '09

23 Jul '09

Full_Name: Test Seven Version: 2.4.17 OS: Linux/Windows URL: Submission from: (NULL) (195.113.184.10) Have sample setup with bdb database, add the following to the bottom of slapd.conf: overlay translucent overlay rwm uri "ldap://127.6.6.6/" # (the server 127.6.6.6 must not exist) Run any search query against the server (with correct credentials). Slapd tries to contact the remote server, then it properly returns an error (32, or 52...) to the client, but then it aborts. Variations: a) Change .conf: uri "ldap://something.that.resolves.but.doesnt.respond" b) Add to the bottom of .conf: idassert-bind binddn="cn=doesnt,ou=matter" credentials=secret The variations return different errors to the client, and may crash elsewhere. Problem in the code (for Variation a): ldap_back_dobind_int() calls send_ldap_result(op,rs), which eventually free-s ((*op).o_request).oq_search.rs_filterstr.bv_val; the same string is later free-d after return to translucent_search() after being retrieved from local variable "fbv".

1 0

(ITS#6225) GSSAPI support for client library (fixes)
by mimir＠samba.org 22 Jul '09

22 Jul '09

Full_Name: Rafal Szczesniak Version: Stable (2.4.16) OS: GNU/Linux URL: http://www.samba.org/~mimir/gssapi-bugfix.diff Submission from: (NULL) (67.51.54.234) This is a bugfix patch for OpenLDAP's gssapi support.

1 0

(ITS#6224) [patch] snprint() fix in guess_service_principal()
by jerry＠plainjoe.org 22 Jul '09

22 Jul '09

Full_Name: Gerald Carter Version: 2.4.16 OS: Linux URL: ftp://ftp.openldap.org/incoming/openldap-2.4.6-guess_service_principal.diff Submission from: (NULL) (71.12.192.77) There's an off by one error in guess_service_principal() when copying and checking the return value from snprintf(). Trivial patch is included.

1 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

openldap-bugs