openldap-bugs

openldap-bugs@openldap.org

1 participants
20961 discussions

(ITS#7648) undefined symbol: ldap_x_utf8s_to_wcs
by msquaredm＠yahoo.com 25 Jul '13

25 Jul '13

Full_Name: Mike Version: 2.4.35 OS: Cent0s v6.4 URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (65.51.198.154) Hi, I've compiled v2.4.35 with the smbk5pwd overlay. When I change my password the openldap terminates with the message: /usr/sbin/slapd: symbol lookup error: /usr/lib64/openldap/smbk5pwd-2.4.so.2: undefined symbol: ldap_x_utf8s_to_wcs Thanks for any help. Mike

1 0

(ITS#7645) various TLSProtocolMin issues
by mgaupp＠googlemail.com 24 Jul '13

24 Jul '13

Full_Name: Manuel Gaupp Version: 2.4.35 OS: CentOS 6.3 URL: Submission from: (NULL) (79.234.218.31) This topic was originally discussed in http://www.openldap.org/lists/openldap-technical/201307/msg00133.html 1.) the TLSProtocolMin parameter is not documented, but it should be - at least in slapd.conf/slapd-config and ldap.conf (there is an example in the original ITS #5655) 2.) the TLSProtocolMin functionality should be extended for TLS 1.1 and TLS 1.2 (see http://www.openldap.org/lists/openldap-technical/201307/msg00138.html) 3.) ldap.conf already accepts correctly formatted TLSProtocolMin values (e.g. "3.1") whereas slapd.conf doesn't (has to be given as an integer, e.g. "769"); I think servers/slapd/bconfig.c should be changed to use ldap_int_tls_config for this option (as mentioned in the FIXME comment of config_tls_config).

1 0

Re: (ITS#7643) MDB_cmp_func not properly documented
by hyc＠symas.com 24 Jul '13

24 Jul '13

vissermc(a)gmail.com wrote: > Full_Name: Michiel Visser > Version: 2.4.35 > OS: Linux > URL: ftp://ftp.openldap.org/incoming/ > Submission from: (NULL) (88.159.211.22) > > > The MDB documentation must specify what is expected of MDB_cmp_func. > I assume it must return -1,0,1 depending on the order, similar to ansi compare > functions, but it is not trivial, nor all will know. The mdb_cmp() description already describes the return values. Users of the library are expected to be able to associate related concepts. -- -- 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#7644) inverted MDB_SET_RANGE desired
by hyc＠symas.com 24 Jul '13

24 Jul '13

vissermc(a)gmail.com wrote: > Full_Name: Michiel Visser > Version: 2.4.35 > OS: Linux > URL: ftp://ftp.openldap.org/incoming/ > Submission from: (NULL) (88.159.211.22) > > > Feature request: > MDB_SET_RANGE is an important option for me (I'm implementing a generic triple > store on top of MDB). But I also desire some additions: > 1) let's call it MDB_SET_RANGE_INV: find key equal of smaller. In theory I could > also apply an inverted compare function, but this makes it counter-intuitive > ('bigger' actually implying 'smaller'). And I understand I can also use > SET_RANGE, followed by a cursor-previous-traversal, but it would require extra > logic to check whether the key is already equal, which brings me to my second > point: Extra logic will be required anyway, whether inside liblmdb or in your application. In this case I don't see value in making the library bigger to handle this. > 2) a way to see whether the returned key is equal (to the supplied key), to > avoid another call to get/cursor_get, or avoid a manual key compare. The mdb_cursor_get() function signature is what it is, there's nowhere to return any other parameters. How would you propose to indicate this to the caller? -- -- 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#7644) inverted MDB_SET_RANGE desired
by vissermc＠gmail.com 23 Jul '13

23 Jul '13

Full_Name: Michiel Visser Version: 2.4.35 OS: Linux URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (88.159.211.22) Feature request: MDB_SET_RANGE is an important option for me (I'm implementing a generic triple store on top of MDB). But I also desire some additions: 1) let's call it MDB_SET_RANGE_INV: find key equal of smaller. In theory I could also apply an inverted compare function, but this makes it counter-intuitive ('bigger' actually implying 'smaller'). And I understand I can also use SET_RANGE, followed by a cursor-previous-traversal, but it would require extra logic to check whether the key is already equal, which brings me to my second point: 2) a way to see whether the returned key is equal (to the supplied key), to avoid another call to get/cursor_get, or avoid a manual key compare.

1 0

(ITS#7643) MDB_cmp_func not properly documented
by vissermc＠gmail.com 23 Jul '13

23 Jul '13

Full_Name: Michiel Visser Version: 2.4.35 OS: Linux URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (88.159.211.22) The MDB documentation must specify what is expected of MDB_cmp_func. I assume it must return -1,0,1 depending on the order, similar to ansi compare functions, but it is not trivial, nor all will know.

1 0

(ITS#7642) make test for AIX fails on test060-mt-hot
by mamfelt＠gmail.com 22 Jul '13

22 Jul '13

Full_Name: Michael Felt Version: 2.4.32 OS: AIX 6.1 TL7 URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (81.253.45.94) built bdb 6.0.20 built openLDAP 2.4.32 using xlC v11 make test runs fine, then stops abruptly at test060 extract of failing test... >>>>> Starting test060-mt-hot for bdb... running defines.sh Running slapadd to build slapd database... Running slapindex to index slapd database... Starting slapd on TCP/IP port 9011... /data/prj/openldap-2.4.32/tests/../servers/slapd/slapd -s0 -f /data/prj/openldap-2.4.32/tests/testrun/slapd.1.conf -h ldap://localhost:9011/ -d stats Testing basic monitor search... Monitor searches Testing basic mt-hot search: 1 threads (1 x 50000) loops... ./progs/slapd-mtread -H ldap://localhost:9011/ -D cn=Manager,dc=example,dc=com -w secret -e cn=Monitor -m 1 -L 1 -l 50000 Testing basic mt-hot search: 5 threads (1 x 10000) loops... ./progs/slapd-mtread -H ldap://localhost:9011/ -D cn=Manager,dc=example,dc=com -w secret -e cn=Monitor -m 5 -L 1 -l 10000 Testing basic mt-hot search: 100 threads (5 x 100) loops... ./progs/slapd-mtread -H ldap://localhost:9011/ -D cn=Manager,dc=example,dc=com -w secret -e cn=Monitor -m 100 -L 5 -l 100 slapd-mtread failed (1)! >>>>> test060-mt-hot failed for bdb (exit 1) make: 1254-004 The error code from the last command is 1. Stop. make: 1254-004 The error code from the last command is 2. Stop. make: 1254-004 The error code from the last command is 2. Stop. AIX Level Info: root@x094:[/data/prj/openldap-2.4.32]oslevel -s 6100-07-06-1241 ############ Please excuse that I have no clue what this test means, or if it will stand in the way of some basic setup of openLDAP as a server. However, since I am asking, I am also promising to dig deeper with some assistance. p.s. if I should have used a bug submission elsewhere, please forgive my blindness. I did not find it first go around. Michael

1 0

Re: (ITS#7641) slapd crashes in slapd_free_controls when syncrepl enabled and plugins in use
by quanah＠zimbra.com 18 Jul '13

18 Jul '13

--On Thursday, July 18, 2013 9:15 PM +0000 kb9vqf(a)pearsoncomputing.net wrote: >> --On Thursday, July 18, 2013 4:47 PM +0000 kb9vqf(a)pearsoncomputing.net > wrote: >> >>> Full_Name: Timothy Pearson >>> Version: 2.4.35 >>> OS: Debian Wheezy >>> URL: ftp://ftp.openldap.org/incoming/ >>> Submission from: (NULL) (131.156.2.26) >>> >>> >>> slapd sporadically crashes in slapd_free_controls when syncrepl enabled > and plugins are in use. The crash is caused by an invalid free in the > slapi overlay; it only occurs on the provider in a syncrepl setup. > This is the backtrace: >> >> Didn't you already report this in ITS#7636? Why are you opening an new > ITS? >> >> --Quanah > > This is a different crash with a different cause and completely different > backtrace. As far as I can tell there were two separate crashes related > to syncrepl with slapi plugins enabled. The one I reported in ITS#7636 > was constant and easily reproducible, therefore it somewhat masked the > crash I have reported in this bug report. > > Should the two reports be merged even though the causes and backtraces are > different? Nope, I just wanted to confirm it wasn't a duplicate. Thanks! --Quanah -- Quanah Gibson-Mount Lead Engineer Zimbra, Inc -------------------- Zimbra :: the leader in open source messaging and collaboration

1 0

Re: (ITS#7641) slapd crashes in slapd_free_controls when syncrepl enabled and plugins in use
by kb9vqf＠pearsoncomputing.net 18 Jul '13

18 Jul '13

> --On Thursday, July 18, 2013 4:47 PM +0000 kb9vqf(a)pearsoncomputing.net wrote: > >> Full_Name: Timothy Pearson >> Version: 2.4.35 >> OS: Debian Wheezy >> URL: ftp://ftp.openldap.org/incoming/ >> Submission from: (NULL) (131.156.2.26) >> >> >> slapd sporadically crashes in slapd_free_controls when syncrepl enabled and plugins are in use. The crash is caused by an invalid free in the slapi overlay; it only occurs on the provider in a syncrepl setup. This is the backtrace: > > Didn't you already report this in ITS#7636? Why are you opening an new ITS? > > --Quanah This is a different crash with a different cause and completely different backtrace. As far as I can tell there were two separate crashes related to syncrepl with slapi plugins enabled. The one I reported in ITS#7636 was constant and easily reproducible, therefore it somewhat masked the crash I have reported in this bug report. Should the two reports be merged even though the causes and backtraces are different?

1 0

Re: (ITS#7641) slapd crashes in slapd_free_controls when syncrepl enabled and plugins in use
by quanah＠zimbra.com 18 Jul '13

18 Jul '13

--On Thursday, July 18, 2013 4:47 PM +0000 kb9vqf(a)pearsoncomputing.net wrote: > Full_Name: Timothy Pearson > Version: 2.4.35 > OS: Debian Wheezy > URL: ftp://ftp.openldap.org/incoming/ > Submission from: (NULL) (131.156.2.26) > > > slapd sporadically crashes in slapd_free_controls when syncrepl enabled > and plugins are in use. The crash is caused by an invalid free in the > slapi overlay; it only occurs on the provider in a syncrepl setup. This > is the backtrace: Didn't you already report this in ITS#7636? Why are you opening an new ITS? --Quanah -- Quanah Gibson-Mount Lead Engineer Zimbra, Inc -------------------- Zimbra :: the leader in open source messaging and collaboration

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