openldap-bugs

openldap-bugs@openldap.org

1 participants
20961 discussions

Re: (ITS#8162) Problème parsing bad LDAP URI in slapo-unique uniqueURI parameter
by h.b.furuseth＠usit.uio.no 03 Jun '15

03 Jun '15

On 02/06/15 23:11, bdauvergne(a)entrouvert.com wrote: > I had configured an mdb backend with a unique overlay configured like this: > > add olcOverlay={4}unique,olcDatabase={2}mdb,cn=config > objectClass: olcOverlayConfig > objectClass: olcUniqueConfig > olcOverlay: {4}unique > olcUniqueURI: ldap://?supannAutreMail?sub > > When trying to add the first non root-entry of new DB openldap freeze and takes > 100% CPU. After activating loglevel 255 I saw that it was looping inside > mdb_search() logging 'scope not okay' with an increasing integer value in > front. Looks like a duplicate of ITS#8146, fixed in the OPENLDAP_REL_ENG_2_4 branch. Please test. Tarball: <http://www.openldap.org/devel/gitweb.cgi?p=openldap.git;a=snapshot;h=refs/h…> We might need a more general description of ITS#8146 in CHANGES.

1 0

(ITS#8162) Probl�me parsing bad LDAP URI in slapo-unique uniqueURI parameter
by bdauvergne＠entrouvert.com 02 Jun '15

02 Jun '15

Full_Name: Benjamin Dauvergne Version: 2.4.40 OS: Debian URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (82.242.47.212) I had configured an mdb backend with a unique overlay configured like this: add olcOverlay={4}unique,olcDatabase={2}mdb,cn=config objectClass: olcOverlayConfig objectClass: olcUniqueConfig olcOverlay: {4}unique olcUniqueURI: ldap://?supannAutreMail?sub When trying to add the first non root-entry of new DB openldap freeze and takes 100% CPU. After activating loglevel 255 I saw that it was looping inside mdb_search() logging 'scope not okay' with an increasing integer value in front. The problem here is that le LDAP URI is missing a third 'slash' which should separate the missing hostname part from the base DN parameter. The RFC 2255 grammar seem to imply that the third slash is mandatory if there are other parameters after it. I think OpenLDAP should have complained about the malformed olcUniqueURI value, not accept it blindly and fail by entering an infinite loop. Overlay configuration that is working: add olcOverlay={4}unique,olcDatabase={2}mdb,cn=config objectClass: olcOverlayConfig objectClass: olcUniqueConfig olcOverlay: {4}unique olcUniqueURI: ldap:///?supannAutreMail?sub

1 0

Re: (ITS#8161) index approx not working
by h.b.furuseth＠usit.uio.no 02 Jun '15

02 Jun '15

On 02/06/15 11:10, bernhard.pfeiffer(a)brz.gv.at wrote: > I configured this index: > > index cn eq,sub,approx > (...) > <= mdb_approx_candidates: (cn) not indexed Does it help to stop slapd, run sbin/slapindex, restart slapd? After inserting an index in slapd.conf, you must do that to index your existing values (if any). If you instead use cn=config and add an index over the LDAP protocol, slapd will index the values automatically.

1 0

(ITS#8161) index approx not working
by bernhard.pfeiffer＠brz.gv.at 02 Jun '15

02 Jun '15

Full_Name: Bernhard Pfeiffer Version: 2.4.40 OS: SUSE Linux 11 URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (85.158.227.32) Hey! I configured this index: index cn eq,sub,approx sn~=Bern But my search doesn't find anything: If i configure: index cn eq,sub and searching for: sn~=Bern I get some results. But in the logfile is written: <= mdb_approx_candidates: (cn) not indexed Is this a bug?

1 0

Re: (ITS#8160) phonetic searches
by h.b.furuseth＠usit.uio.no 02 Jun '15

02 Jun '15

On 02/06/15 10:00, bernhard.pfeiffer(a)brz.gv.at wrote: > Is there any possibility to configure phontic search specially for Austria? ITS is for bug reports/enhancements. Use the openldap-technical mailinglist for help reqests. Anyway: No, soundex/metaphone is hardcoded in slapd approx match. See <openldap source>/servers/slapd/phonetic.c. Clients can do a little of this "by hand" by inserting many variants of a name (e.g. o instead of ö) as invisible attribute values in the directory, see the x-hidden examples in man slapd.conf. Closing this ITS. Hallvard

1 0

(ITS#8160) phonetic searches
by bernhard.pfeiffer＠brz.gv.at 02 Jun '15

02 Jun '15

Full_Name: Bernhard Pfeiffer Version: 2.4.40 OS: Linux URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (85.158.227.32) Hey! Is there any possibility to configure phontic search specially for Austria? fe.: cn=Jörg Mössmer How i have to configure that to openLDAP, is there anywhere a documentation about this? Greets, Bernhard

1 0

(ITS#8159) Missing parameter in the Configuration man page
by elecharny＠apache.org 01 Jun '15

01 Jun '15

Full_Name: Emmanuel Lecharny Version: 2.4.40 OS: URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (212.195.127.200) There is a missing parameter description in the slapd-config man page, on the olcSizeLimit parameter. The doc says : "The syntax size.prtotal={<integer>|unlimited|disabled}..." when the code is also checking for an 'hard' value : } else if ( STRSTART( arg, "prtotal=" ) ) { arg += STRLENOF( "prtotal=" ); ... } else if ( strcasecmp( arg, "hard" ) == 0 ) { limit->lms_s_pr_total = 0;

1 0

(ITS#8158) cldap broken for aix and solaris
by goran.hammarback＠foxt.com 29 May '15

29 May '15

Full_Name: G.ran Hammarb.ck Version: 2.4.40 OS: Solaris 11, aix 7.1 URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (192.71.43.2) In the routine libraries/liblber/sockbuf.s:sb_dgram_write(), the last argument to the sendto() call is sizeof( struct sockaddr_storage ). While this works on Linux, on Solaris 11 and AIX 7.1 (and likely other versions of these OSes) the call returns EINVAL. This causes attempts to use connectionless ldap to fail. Here is a suggestion to a patch that has been tested on Solaris 11, AIX 7.1 and RedHat 6: *** libraries/liblber/sockbuf.c..org 2015-05-27 09:55:14.001639041 +0200 --- libraries/liblber/sockbuf.c

1 0

Re: (ITS#8156) triggering MDB_PAGE_FULL
by sergej.jurecko＠gmail.com 28 May '15

28 May '15

--089e0160aab816893f05171d9e22 Content-Type: text/plain; charset=UTF-8 Thank you for the explanation. Sergej On Wed, May 27, 2015 at 10:32 AM, Hallvard Breien Furuseth < h.b.furuseth(a)usit.uio.no> wrote: > On 27/05/15 09:00, sergej.jurecko(a)gmail.com wrote: > >> Using a dupsort and writing a large value (which is still bellow >> maxkeysize) >> will result in MDB_PAGE_FULL. >> (...) >> maxkeysize=10000 >> > > Too big MDB_MAXKEYSIZE. Its doc says: > "Keys and MDB_DUPSORT data items must fit on a node in a regular page." > > But the doc should clarify that MDB_MAXKEYSIZE can be set big enough > to break lmdb. > > Or mdb_env_open() can fail if the computed me_maxkey would be smaller. > > Or compute a safe MIN_PAGESIZE from MDB_MAXKEYSIZE and use that, > and then fail if the page size would be unsupported. (MIN_PAGESIZE > can be computed at compile time, with some ugly macros.) > > lmdb sets the max safe maxkeysize if you define MDB_MAXKEYSIZE=0. > Some time ago, that was 1/3 of the size you could reasonably use > (to allow 1 key + sub-page with 2 dupsort values), so it could make > sense to define MDB_MAXKEYSIZE above the safe max. Today lmdb > uses a sub-DB at once if a sub-page would be too small, though. > So I don't see much need to support maxkeysize > safe max. > --089e0160aab816893f05171d9e22 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable <div dir=3D"ltr"><div>Thank you for the explanation. <br><br><br></div>Serg= ej<br></div><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">On We= d, May 27, 2015 at 10:32 AM, Hallvard Breien Furuseth <span dir=3D"ltr">&lt= ;<a href=3D"mailto:h.b.furuseth@usit.uio.no" target=3D"_blank">h.b.furuseth= @usit.uio.no</a>></span> wrote:<br><blockquote class=3D"gmail_quote" sty= le=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On 27/= 05/15 09:00, <a href=3D"mailto:sergej.jurecko@gmail.com" target=3D"_blank">= sergej.jurecko(a)gmail.com</a> wrote:<br> <blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p= x #ccc solid;padding-left:1ex"> Using a dupsort and writing a large value (which is still bellow=C2=A0 maxk= eysize)<br> will result in MDB_PAGE_FULL.<br> (...)<br> maxkeysize=3D10000<br> </blockquote> <br> Too big MDB_MAXKEYSIZE.=C2=A0 Its doc says:<br> "Keys and MDB_DUPSORT data items must fit on a node in a regular page.= "<br> <br> But the doc should clarify that MDB_MAXKEYSIZE can be set big enough<br> to break lmdb.<br> <br> Or mdb_env_open() can fail if the computed me_maxkey would be smaller.<br> <br> Or compute a safe MIN_PAGESIZE from MDB_MAXKEYSIZE and use that,<br> and then fail if the page size would be unsupported.=C2=A0 (MIN_PAGESIZE<br= > can be computed at compile time, with some ugly macros.)<br> <br> lmdb sets the max safe maxkeysize if you define MDB_MAXKEYSIZE=3D0.<br> Some time ago, that was 1/3 of the size you could reasonably use<br> (to allow 1 key + sub-page with 2 dupsort values), so it could make<br> sense to define MDB_MAXKEYSIZE above the safe max.=C2=A0 Today lmdb<br> uses a sub-DB at once if a sub-page would be too small, though.<br> So I don't see much need to support maxkeysize > safe max.<br> </blockquote></div><br></div> --089e0160aab816893f05171d9e22--

1 0

(ITS#8157) txn can be useless after mdb_txn_renew()
by h.b.furuseth＠usit.uio.no 27 May '15

27 May '15

Full_Name: Hallvard B Furuseth Version: LMDB 0.9.14 OS: URL: Submission from: (NULL) (81.191.45.5) Submitted by: hallvard mdb_txn_renew() may initialize txn halfway and then fail. After that, it refuses to work even when it should have succeeded, since the txn looks active (mt_dbxs != NULL). Fixing.

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