openldap-bugs November 2010

openldap-bugs@openldap.org

32 participants
103 discussions

(ITS#6727) ./scripts/test047-ldap: line 599: 26709 Segmentation fault
by michael＠stroeder.com 28 Nov '10

28 Nov '10

Full_Name: Michael Ströder Version: HEAD OS: openSUSE Linux URL: Submission from: (NULL) (84.163.34.72) >>>>> Starting test047-ldap for bdb... running defines.sh Starting slapd on TCP/IP port 9011... Using ldapsearch to check that slapd is running... Using ldapadd to populate the database... Starting slapd on TCP/IP port 9012... Using ldapsearch to check that slapd is running... Using ldapadd to populate the database... Starting slapd on TCP/IP port 9013... Using ldapsearch to check that slapd is running... Searching base="o=Example,c=US"... Searching base="ou=Meta,o=Example,c=US"... Modifying database "o=Example,c=US"... Searching base="o=Example,c=US"... base="o=Example,c=US"... Searching filter="(seeAlso=cn=all staff,ou=Groups,o=Example,c=US)" attrs="seeAlso" base="o=Example,c=US"... Searching filter="(uid=example)" attrs="uid" base="o=Example,c=US"... Searching filter="(member=cn=Another Added Group,ou=Groups,o=Example,c=US)" attrs="member" base="o=Example,c=US"... Waiting 10 seconds for cached connections to timeout... Searching with a timed out connection... Checking server-enforced size limit... Checking client-requested size limit... Filtering ldapsearch results... Filtering original ldif used to create database... Comparing filter output... Changing password to database "o=Example,c=US"... Binding with newly changed password to database "o=Example,c=US"... Binding as newly added user to database "o=Example,c=US"... ./scripts/test047-ldap: line 599: 26709 Segmentation fault $SLAPD -f $CONF3 -h $URI3 -d $LVL $TIMING > $LOG3 2>&1 WhoAmI failed (255)! ./scripts/test047-ldap: line 614: kill: (26709) - No such process >>>>> ./scripts/test047-ldap failed for bdb (exit 255) make[2]: *** [bdb-yes] 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

1 0

RE : (ITS#6720) back-ldap core dump
by olivier.chirossel＠sfr.com 26 Nov '10

26 Nov '10

Hi Thank's for you reply, you can get a tar file containing a simple case which reproduce the problem= here ( i don't put rewriting rules in proxy conf, just strip of operation= nal attribut ) wget http://olivier:its6720@84.103.237.12/its6720.tar the lance.sh inititialise the tests=20 (the slapd suppose to be in /usr/local/libexec) and you reproduce it with the command : ldapmodify -D "cn=3Dmanager,dc=3Dneuf,dc=3Dfr" -H "ldap://127.0.0.1:489" -= w secret -f mod i try to explain you my need=20 1) For the moment i have a master in 2.3.x with many replica in 2.3.x with = slurpd replication 2) my goal is to migrate to a mirror mode master infrastructure with syncre= pl replication 3) the first step is to install my mirror mode infrastructure and replicate= with slurpd from my old master. 4) second step re install replica one by one with syncrepl replication to m= y new mirror mode infrastructure 5) third step write directly to my mirror mode infrastructure For the first step i put a proxy ldap between my old master and my mirror m= ode infrastructure to do rewrite rules and strip operationnal attribut (i n= eed, at the end, have a new clean infrastructure with entryCSN contains th= e ServerId of my new master, for checks the replcation status between my ma= ster and between my replica and my mirror mode architcture) =20 The ldapmodify command reproduce the replication operations which highlight= the problem.. PS:=A0before strip attribute with rwm-map directives i try to put "lastmod = off" in proxy ldap configuration without success ... Regards, Olivier ________________________________________ De : openldap-its(a)OpenLDAP.org [openldap-its(a)OpenLDAP.org] Date d'envoi : lundi 22 novembre 2010 17:43 =C0 : CHIROSSEL, Olivier Objet : Re: (ITS#6720) back-ldap core dump *** 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#6720. 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#6720) in the subject will automatically be attached to the issue report. mailto:openldap-its@openldap.org?subject=3D(ITS#6720) 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=3D6720 Please remember to retain your issue tracking number (ITS#6720) 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

Re: (ITS#6724) Feature request: support for PKCS11 pin input callback in public TLS api
by hyc＠symas.com 26 Nov '10

26 Nov '10

silvan(a)kernelconcepts.de wrote: > Full_Name: Silvan Marco Fin > Version: > OS: Ubuntu Linux 10.04 > URL: > Submission from: (NULL) (217.146.132.69) > > > Support for PKCS #11 devices in TLS via MozNSS in OpenLDAP currently lacks the > possibility to "ask" for a PIN via callback. The methods supplied in tls_m.c are > reading a PIN from a file or alternativly reading a PIN from STDIN. > > To add the needed flexibility to the MozNSS part, an additional callback > argument to the init function or alternatively an additional set function for > the callback would be needed. > > http://www.mozilla.org/projects/security/pki/nss/ref/ssl/pkfnc.html#1023128 > > provides the signature for the callback function. > > Since GnuTLS and OpenSSL provide PKCS #11 support by themselves in some way, I > propose to add an additional set function to OpenLDAPs public TLS API to > register a callback with the corresponding security library. > Probably a good idea. Feel free to submit a patch for review. -- -- 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#6725) How to install multiple instances of openldap on different port(389, 390 391)
by rein＠OpenLDAP.org 26 Nov '10

26 Nov '10

On 11/25/10 17:27 , devman1624(a)yahoo.com wrote: > Can some one tell me how to install multiple instances of openldap on different > port(i.e on 389, 390 391). > > Accroding to me there is only one option, that is multiple installation od > openldap. Please direct usage questions to the openldap-technical list, the ITS system is for bugs. And please RTFM before doing so, the answer to your question is clearly stated there. Rein

1 0

(ITS#6726) How to install multiple instances of openldap on different port(389, 390 391)
by devman1624＠yahoo.com 25 Nov '10

25 Nov '10

Full_Name: DevMan Version: 2.4.16 OS: RHEL54. URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (122.177.216.157) Hi All, Can some one tell me how to install multiple instances of openldap on different port(i.e on 389, 390 391). Accroding to me there is only one option, that is multiple installation od openldap. Thx DevMan

1 0

(ITS#6725) How to install multiple instances of openldap on different port(389, 390 391)
by devman1624＠yahoo.com 25 Nov '10

25 Nov '10

1 0

Re: (ITS#6686) VLV overlay fails to handle multiple search operations per LDAP connection
by raphael.ouazana＠linagora.com 25 Nov '10

25 Nov '10

Hi, Here is a new version of the patch: ftp://ftp.openldap.org/incoming/raphael-ouazana-101125-sssvlv-multiple-requ… It fixes some segfaults that the previous patch introduced if you use pagedResults or sss instead of VLV. It also fixes a segfault in the original sssvlv code when making two successive requests on the same connexion (can be triggered by ldapsearch). Finally here is an update of the copyright notice too: Legal notice: This patch file is derived from OpenLDAP Software. All of the modifications to OpenLDAP Software represented in this following patch were developed by Raphael Ouazana raphael.ouazana(a)linagora.com and Sebastien Bahloul sbahloul(a)linagora.com. These modifications are not subject to any license of Linagora. The attached modifications to OpenLDAP Software are subject to the following notice: Copyright 2010 Raphael Ouazana, Linagora Copyright 2010 Sebastien Bahloul, Linagora Redistribution and use in source and binary forms, with or without modification, are permitted only as authorized by the OpenLDAP Public License. Regards, Raphaël Ouazana

1 0

Re: (ITS#6720) back-ldap core dump
by masarati＠aero.polimi.it 24 Nov '10

24 Nov '10

olivier.chirossel(a)sfr.com wrote: > I have to migrate from a openldap 2.3.x to openldap 2.4. During this migration > phase i want my openldap 2.3.x master replicate with slurpd to my new openldap > 2.4.x master mirror mode architecture with some rewriting rules for split my big > directory. > > > I configure a proxy ldap using back-ldap with slapo-rwm overlay, but > operational attributes related to entry creation and modification are > proxied, even when i put « lastmod off » in the conf, contrary of the man of > slapd-ldap > > > > So i put rw-map directives in the conf for strip operationnal attributes but > this kind of operation generate a core dump Your configuration contains a load of custom schema items; can you create a simple configuration, based on standard attributes, that reproduces the problem (I mean: the sigsegv), and describe which operation is causing it? Is it a client operation or replication? In your report you mention the intention to use "master mirror mode" (?), it's not clear what back-ldap has to do with it. p.

1 0

Re: (ITS#6603) EAGAIN, EWOULDBLOCK occasionally used without checking #ifdef
by h.b.furuseth＠usit.uio.no 24 Nov '10

24 Nov '10

> Here's a patch, please inspect. > > <ftp://ftp.openldap.org/incoming/pierangelo.masarati.2010-11-23.1.patch> Looks fine to me. -- Hallvard

1 0

Re: (ITS#6532) Support for common orderingMatching rules in extensible match filters
by h.b.furuseth＠usit.uio.no 24 Nov '10

24 Nov '10

Variant applied to HEAD: schema_init.c 1.473. Correct 'match' code is simpler than yours, now that you've pointed me in the right direction. All ordering rules except CSNOrderingMatch and UUIDOrderingMatch now support extensible match. Someone who knows slapd's use of CSNs and UUIDs can (tell me to) do the same there if it's OK to do so. I didn't want to meddle carelessly, also I don't know what UUIDOrderingMatch's SLAP_MR_MUTATION_NORMALIZER flag means and if it would interfere. -- Hallvard

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

openldap-bugs November 2010