openldap-bugs

openldap-bugs@openldap.org

1 participants
20959 discussions

Re: (ITS#6202) adding command line option to disable line breaking in ldif output
by michael＠stroeder.com 09 Jul '09

09 Jul '09

openldap.org(a)bloms.de wrote: > Full_Name: Dieter Bloms > Version: all > OS: linux > URL: ftp://ftp.openldap.org/incoming/ > Submission from: (NULL) (193.27.50.90) > > > I want to do an enhancement request for ldapsearch, because it insert a line > break after 78 characters. > Many people like me use the ldapsearch command in shell script and have to > workaround this issue. > Maybe it make sense to add a command line option to deactivate this line breaks. I'd rather recommend to use a decent scripting language with LDAP and/or LDIF modules than using ldapsearch in shell scripts. This gives better control over data and error handling. Ciao, Michael.

1 0

(ITS#6203)
by Andrew.Morgan＠Sun.COM 09 Jul '09

09 Jul '09

wait_until_ready is documented here: http://dev.mysql.com/doc/ndbapi/en/class-ndb-cluster-connection-methods.html #class-ndb-cluster-connection-wait-until-ready -----Original Message----- From: openldap-its(a)OpenLDAP.org [mailto:openldap-its@OpenLDAP.org] Sent: 09 July 2009 14:51 To: Andrew.Morgan(a)Sun.COM Subject: Re: (ITS#6203) Problem & solution for back-ndb issue connecting to Cluster data nodes *** 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#6203. 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#6203) in the subject will automatically be attached to the issue report. mailto:openldap-its@openldap.org?subject=(ITS#6203) 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=6203 Please remember to retain your issue tracking number (ITS#6203) 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#6203) Problem & solution for back-ndb issue connecting to Cluster data nodes
by andrew.morgan＠sun.com 09 Jul '09

09 Jul '09

Full_Name: Andrew Morgan Version: 2.4.16 OS: Ubuntu URL: Submission from: (NULL) (90.193.196.76) I am running MySQL Cluster with data nodes all running on the same host. I configured, built and installed OpenLDAP with back-ndb but when I run "slapd -d 5", it failed with "ndb_db_open: ni_cluster[0]->wait failed (1)". Looking at the code in "back-ndb/init.cpp" this implies that it was able to connect to the Cluster management node but only the first of the data nodes. The cause of this is line 133: "ni->ni_cluster[i]->wait_until_ready( 30, 0 );" - the 30,0 means wait up to 30 seconds for first data node but then no time at all for the others; the fact that the method returned 1 means that the first node was found to be live. The second parameter should be set to a non-zero value to give the other data nodes chance to show as being live. I changed the 0 to 30, recompiled/installed and slapd came up correctly.

1 0

Re: (ITS#6139) slapd: password-hash rejects multiple values
by h.b.furuseth＠usit.uio.no 09 Jul '09

09 Jul '09

It has been fixed in CVS (and in next OpenLDAP release): http://www.openldap.org/devel/cvsweb.cgi/servers/slapd/bconfig.c.diff?r1=1.… -- Hallvard

1 0

(ITS#6202) adding command line option to disable line breaking in ldif output
by openldap.org＠bloms.de 09 Jul '09

09 Jul '09

Full_Name: Dieter Bloms Version: all OS: linux URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (193.27.50.90) I want to do an enhancement request for ldapsearch, because it insert a line break after 78 characters. Many people like me use the ldapsearch command in shell script and have to workaround this issue. Maybe it make sense to add a command line option to deactivate this line breaks.

1 0

RE: (ITS#6201) Double free in syncprov
by Alister.Winfield＠sns.bskyb.com 09 Jul '09

09 Jul '09

I think I have it (bad configuration)... I have the 'accesslogs' at every level which makes sense because I'm replic= ating individual branches separately. I forgot to remove the "overlay glue" line from the configurati= on (previously this configuration had the whole database replicated with just one provider). Now that puts th= e same accesslog entry into two db's which might be where the source of the double free begins. NB: Testing this setup without that extraneous line of config has, so far, = not crashed. After adding it again it crashed almost instantly after I started removing = entries from LDAP. Okay so it might be a configuration 'error' but I guess its worth trying to= avoid the crash. The last crash looks like. syncprov_search_response: cookie=3Drid=3D099,csn=3D20090709104334.923157Z#0= 00000#000#000000 *** glibc detected *** /data/ldap-re24/libexec/slapd: double free or corrup= tion (out): 0x0000000041c406f0 *** =3D=3D=3D=3D=3D=3D=3D Backtrace: =3D=3D=3D=3D=3D=3D=3D=3D=3D /lib/libc.so.6[0x7f5256652948] /lib/libc.so.6(cfree+0x76)[0x7f5256654a56] /data/ldap-re24/libexec/ldap/syncprov-2.4-releng.so.2[0x7f5254260821] /data/ldap-re24/libexec/slapd[0x441c50] /data/ldap-re24/libexec/slapd[0x44478b] /data/ldap-re24/libexec/slapd(slap_send_ldap_result+0x185)[0x4453f5] /data/ldap-re24/libexec/ldap/syncprov-2.4-releng.so.2[0x7f5254263733] /data/ldap-re24/libexec/slapd(overlay_op_walk+0x4a)[0x496bda] /data/ldap-re24/libexec/slapd[0x4976d3] /data/ldap-re24/libexec/slapd[0x49555b] /data/ldap-re24/libexec/slapd(overlay_op_walk+0x4a)[0x496bda] /data/ldap-re24/libexec/slapd[0x4976d3] /data/ldap-re24/libexec/slapd(fe_op_search+0x2c1)[0x434bb1] /data/ldap-re24/libexec/slapd(do_search+0x6fc)[0x4353ac] /data/ldap-re24/libexec/slapd[0x43292f] /data/ldap-re24/lib/libldap_r-2.4-releng.so.2[0x7f5258d0f7e0] /lib/libpthread.so.0[0x7f525831cfc7] /lib/libc.so.6(clone+0x6d)[0x7f52566ae5ad] =3D=3D=3D=3D=3D=3D=3D Memory map: =3D=3D=3D=3D=3D=3D=3D=3D 00400000-00527000 r-xp 00000000 08:06 4841518 /d= ata/ldap-re24/libexec/slapd 00726000-0072e000 rw-p 00126000 08:06 4841518 /d= ata/ldap-re24/libexec/slapd 0072e000-00772000 rw-p 0072e000 00:00 0 01511000-09566000 rw-p 01511000 00:00 0 [h= eap] 4032a000-4032b000 ---p 4032a000 00:00 0 4032b000-40b2b000 rw-p 4032b000 00:00 0 40c41000-40c42000 ---p 40c41000 00:00 0 40c42000-41442000 rw-p 40c42000 00:00 0 41442000-41443000 ---p 41442000 00:00 0 41443000-41c43000 rw-p 41443000 00:00 0 41c43000-41c44000 ---p 41c43000 00:00 0 41c44000-42444000 rw-p 41c44000 00:00 0 42444000-42445000 ---p 42444000 00:00 0 42445000-42c45000 rw-p 42445000 00:00 0 42c45000-42c46000 ---p 42c45000 00:00 0 42c46000-43446000 rw-p 42c46000 00:00 0 43446000-43447000 ---p 43446000 00:00 0 43447000-43c47000 rw-p 43447000 00:00 0 43c47000-43c48000 ---p 43c47000 00:00 0 43c48000-44448000 rw-p 43c48000 00:00 0 44448000-44449000 ---p 44448000 00:00 0 44449000-44c49000 rw-p 44449000 00:00 0 44c49000-44c4a000 ---p 44c49000 00:00 0 44c4a000-4544a000 rw-p 44c4a000 00:00 0 4544a000-4544b000 ---p 4544a000 00:00 0 4544b000-45c4b000 rw-p 4544b000 00:00 0 45c4b000-45c4c000 ---p 45c4b000 00:00 0 45c4c000-4644c000 rw-p 45c4c000 00:00 0 4644c000-4644d000 ---p 4644c000 00:00 0 4644d000-46c4d000 rw-p 4644d000 00:00 0 46c4d000-46c4e000 ---p 46c4d000 00:00 0 46c4e000-4744e00Aborted x4440:~/junk# Information in this email including any attachments may be privileged, conf= idential and is intended exclusively for the addressee. The views expressed= may not be official policy, but the personal views of the originator. If y= ou have received it in error, please notify the sender by return e-mail and= delete it from your system. You should not reproduce, distribute, store, r= etransmit, use or disclose its contents to anyone. Please note we reserve t= he right to monitor all e-mail communication through our internal and exter= nal networks. SKY and the SKY marks are trade marks of British Sky Broadcas= ting Group plc and are used under licence. British Sky Broadcasting Limited= (Registration No. 2906991), Sky Interactive Limited (Registration No. 3554= 332), Sky-In-Home Service Limited (Registration No. 2067075) and Sky Subscr= ibers Services Limited (Registration No. 2340150) are direct or indirect su= bsidiaries of British Sky Broadcasting Group plc (Registration No. 2247735)= . All of the companies mentioned in this paragraph are incorporated in Engl= and and Wales and share the same registered office at Grant Way, Isleworth,= Middlesex TW7 5QD.

1 0

Re: (ITS#5836) hung writers
by jorge.perez＠adaptia.net 09 Jul '09

09 Jul '09

Hi, On Tue, Jul 7, 2009 at 6:40 PM, Quanah Gibson-Mount<quanah(a)zimbra.com> wrote: > > Hi Jorge, > > We're going to need more information from you than you are providing. Please > make sure you: > > (a) build openldap without optimization (-O0) > (b) are gdbing the process, not a core file > (c) Send a full backtrace of everything: thr apply all bt full > > Also, please confirm what BDB version you are using, including if it has all > patches applied and compile options for BDB, and which backend you are > using. The last testing was wrong due to an old slapd.conf without writetimeout keyword, my apologies. We have been testing for 2 days to reproduce this problem and we have not seen the problem again, even though with debug symbols the assert ""assert( SLAP_SOCK_IS_ACTIVE( s ))"" still fails. Reading symbols from /usr/lib64/sasl2/libanonymous.so...done. Loaded symbols for /usr/lib64/sasl2/libanonymous.so Core was generated by `/local/slapd_L5B8_17-7 -f /home/cudb/dataAccess/ldapAccess/ldapFe/config/slapd.'. Program terminated with signal 6, Aborted. #0 0x00002b18e9dd5d45 in raise () from /lib64/libc.so.6 (gdb) bt #0 0x00002b18e9dd5d45 in raise () from /lib64/libc.so.6 #1 0x00002b18e9dd7140 in abort () from /lib64/libc.so.6 #2 0x00002b18e9dcf286 in __assert_fail () from /lib64/libc.so.6 #3 0x00000000004641b0 in slapd_clr_write (s=410, wake=0) at daemon.c:939 #4 0x000000000046db7d in connection_write (s=410) at connection.c:1855 #5 0x00000000004688e0 in slapd_daemon_task (ptr=0x0) at daemon.c:2567 #6 0x00002b18e9264143 in start_thread () from /lib64/libpthread.so.0 #7 0x00002b18e9e66b8d in clone () from /lib64/libc.so.6 #8 0x0000000000000000 in ?? () Best regards.

1 0

Re: (ITS#6139) slapd: password-hash rejects multiple values
by fumiyas＠osstech.jp 09 Jul '09

09 Jul '09

Hi, At Mon, 25 May 2009 13:22:47 GMT, michael(a)stroeder.com wrote: > fumiyas(a)osstech.co.jp wrote: > > My /etc/openldap/slapd.conf has the following line: > > password-hash {CRYPT} {SSHA} > > What exactly do you want to achieve by this? I use 'password-hash {CLEARTEXT} {CRYPT}' in my slapd.conf on OpenLDAP 2.3.43 to maintain the clear text password and the crypt(3)-ed password. The {CLEARTEXT} password can be used for: 1. Generating MD5 has for Digest/CRAM-MD5 authentication. 2. Notifying a user of the user's current password. (This is a rare case, I think.) 3. Migrating users and their passwords to another system in the future. 4. ... and so on. The {CRYPT} password can be used for old NIS clients. -- -- Name: SATOH Fumiyasu (fumiyas @ osstech co jp) -- Business Home: http://www.OSSTech.co.jp/ -- Personal Home: http://www.SFO.jp/blog/

1 0

Re: (ITS#6201) Double free in syncprov
by hyc＠symas.com 08 Jul '09

08 Jul '09

hyc(a)symas.com wrote: > Alister.Winfield(a)sns.bskyb.com wrote: >> Failed in the same way.... > > Can you please provide the full text of the error message that glibc printed? Also, can you reproduce this with a slapd compiled without optimization? The stack trace is missing some information here. >> >> >> (gdb) bt >> #0 0x00007f2b031b1ed5 in *__GI_raise (sig=3D<value optimized out>) at ../n= >> ptl/sysdeps/unix/sysv/linux/raise.c:64 >> #1 0x00007f2b031b33f3 in *__GI_abort () at abort.c:88 >> #2 0x00007f2b031ee3a8 in __libc_message (do_abort=3D2, fmt=3D0x7f2b0329d5f= >> 0 "*** glibc detected *** %s: %s: 0x%s ***\n") at ../sysdeps/unix/sysv/linu= >> x/libc_fatal.c:170 >> #3 0x00007f2b031f3948 in malloc_printerr (action=3D2, str=3D0x7f2b0329d6d8= >> "double free or corruption (out)", ptr=3D<value optimized out>) at malloc.= >> c:5891 >> #4 0x00007f2b031f5a56 in *__GI___libc_free (mem=3D0x7f2b03293fa0) at mallo= >> c.c:3626 >> #5 0x00007f2b00e01821 in syncprov_search_cleanup (op=3D0x7f279a205010, rs= >> =3D0x40efbd30) at ../../../../openldap-re24/servers/slapd/overlays/syncprov= >> .c:2024 >> #6 0x0000000000441c50 in ?? () >> #7 0x000000000044478b in ?? () >> #8 0x00000000004453f5 in slap_send_ldap_result () >> #9 0x00007f2b00e04733 in syncprov_op_search (op=3D0x7f279a205010, rs=3D0x4= >> 0efbd30) at ../../../../openldap-re24/servers/slapd/overlays/syncprov.c:243= >> 7 >> #10 0x0000000000496bda in overlay_op_walk () >> #11 0x00000000004976d3 in ?? () >> #12 0x000000000049555b in ?? () >> #13 0x0000000000496bda in overlay_op_walk () >> #14 0x00000000004976d3 in ?? () >> #15 0x0000000000434bb1 in fe_op_search () >> #16 0x00000000004353ac in do_search () >> #17 0x000000000043292f in ?? () >> #18 0x00007f2b058b07e0 in ldap_int_thread_pool_wrapper (xpool=3D<value opti= >> mized out>) at ../../../openldap-re24/libraries/libldap_r/tpool.c:685 >> #19 0x00007f2b04ebdfc7 in start_thread (arg=3D<value optimized out>) at pth= >> read_create.c:297 >> #20 0x00007f2b0324f5ad in clone () from /usr/lib/debug/libc.so.6 >> #21 0x0000000000000000 in ?? () >> (gdb) -- -- 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#6201) Double free in syncprov
by hyc＠symas.com 08 Jul '09

08 Jul '09

Alister.Winfield(a)sns.bskyb.com wrote: > Failed in the same way.... Can you please provide the full text of the error message that glibc printed? > > > (gdb) bt > #0 0x00007f2b031b1ed5 in *__GI_raise (sig=3D<value optimized out>) at ../n= > ptl/sysdeps/unix/sysv/linux/raise.c:64 > #1 0x00007f2b031b33f3 in *__GI_abort () at abort.c:88 > #2 0x00007f2b031ee3a8 in __libc_message (do_abort=3D2, fmt=3D0x7f2b0329d5f= > 0 "*** glibc detected *** %s: %s: 0x%s ***\n") at ../sysdeps/unix/sysv/linu= > x/libc_fatal.c:170 > #3 0x00007f2b031f3948 in malloc_printerr (action=3D2, str=3D0x7f2b0329d6d8= > "double free or corruption (out)", ptr=3D<value optimized out>) at malloc.= > c:5891 > #4 0x00007f2b031f5a56 in *__GI___libc_free (mem=3D0x7f2b03293fa0) at mallo= > c.c:3626 > #5 0x00007f2b00e01821 in syncprov_search_cleanup (op=3D0x7f279a205010, rs= > =3D0x40efbd30) at ../../../../openldap-re24/servers/slapd/overlays/syncprov= > .c:2024 > #6 0x0000000000441c50 in ?? () > #7 0x000000000044478b in ?? () > #8 0x00000000004453f5 in slap_send_ldap_result () > #9 0x00007f2b00e04733 in syncprov_op_search (op=3D0x7f279a205010, rs=3D0x4= > 0efbd30) at ../../../../openldap-re24/servers/slapd/overlays/syncprov.c:243= > 7 > #10 0x0000000000496bda in overlay_op_walk () > #11 0x00000000004976d3 in ?? () > #12 0x000000000049555b in ?? () > #13 0x0000000000496bda in overlay_op_walk () > #14 0x00000000004976d3 in ?? () > #15 0x0000000000434bb1 in fe_op_search () > #16 0x00000000004353ac in do_search () > #17 0x000000000043292f in ?? () > #18 0x00007f2b058b07e0 in ldap_int_thread_pool_wrapper (xpool=3D<value opti= > mized out>) at ../../../openldap-re24/libraries/libldap_r/tpool.c:685 > #19 0x00007f2b04ebdfc7 in start_thread (arg=3D<value optimized out>) at pth= > read_create.c:297 > #20 0x00007f2b0324f5ad in clone () from /usr/lib/debug/libc.so.6 > #21 0x0000000000000000 in ?? () > (gdb) > > > -----Original Message----- > From: Quanah Gibson-Mount [mailto:quanah@zimbra.com] > Sent: 08 July 2009 19:15 > To: Alister Winfield; openldap-its(a)openldap.org > Subject: Re: (ITS#6201) Double free in syncprov > > --On Wednesday, July 08, 2009 4:59 PM +0000 alister.winfield(a)sns.bskyb.com > wrote: > >> Full_Name: Alister Winfield >> Version: 2.4.16 >> OS: Debian Lenny >> URL: >> Submission from: (NULL) (90.207.245.9) >> >> >> I'm testing 2.4.16 and have stumbled across a problem. > > Please re-test and follow up with current RE24 CVS, as numerous fixes have = > been made since the 2.4.16 release. Thanks! > > --Quanah -- -- 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

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

openldap-bugs