openldap-bugs May 2015

openldap-bugs@openldap.org

26 participants
101 discussions

(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 27 May '15

27 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

Re: (ITS#8156) triggering MDB_PAGE_FULL
by h.b.furuseth＠usit.uio.no 27 May '15

27 May '15

On 27/05/15 10:33, h.b.furuseth(a)usit.uio.no wrote: > (blah...) > So I don't see much need to support maxkeysize > safe max. Sorry, I should I said there's no need to recommend changing MDB_MAXKEYSIZE as anything else than 0, except if you need to make sure old liblmdb versions can use the database. I don't want to restart the discussion about which errors to catch yet again.

1 0

Re: (ITS#8156) triggering MDB_PAGE_FULL
by h.b.furuseth＠usit.uio.no 27 May '15

27 May '15

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.

1 0

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

27 May '15

Full_Name: Sergej Jurecko Version: lmdb latest OS: osx 10.9.5 URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (193.189.172.218) Using a dupsort and writing a large value (which is still bellow maxkeysize) will result in MDB_PAGE_FULL. Program here: http://pastebin.com/Mu6bp1DR Compiling with: gcc pagefull.c mdb.c midl.c -g -DMDB_MAXKEYSIZE=10000 -o pagefull Running ./pagefull maxkeysize=10000 writing keysize=12, datasize=4063 Cursor put eror=-30786

1 0

(ITS#8155) add support for cacertdir with gnutls
by ryan＠openldap.org 26 May '15

26 May '15

Full_Name: Ryan Tandy Version: OS: URL: Submission from: (NULL) (142.31.146.2) Submitted by: ryan GnuTLS recently (3.3.6) finally added an API for adding a directory of CA files: http://gnutls.org/manual/html_node/Core-TLS-API.html#gnutls_005fcertificate… https://www.happyassassin.net/2015/01/12/a-note-about-ssltls-trusted-certif… Haven't actually tried it yet, but I think it should allow us to implement cacertdir. Just filing this for tracking right now, patch to come later.

1 0

(ITS#8154) sizeLimit/timeLimit are described as Multi-value in slapd-config man page
by elecharny＠apache.org 26 May '15

26 May '15

Full_Name: Emmanuel Lecharny Version: 2.4.40 OS: URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (109.190.108.22) The slapd-config man page says that we can store the sizeLimit and timeLimit values as multiple values, when they are single value attributes (at least they should be...) : olcTimeLimit: time[.{soft|hard}]=<integer> [...] Specify the maximum number of seconds (in real time) slapd will spend answering a search request. The default time limit is 3600. Use unlimited to specify no limits. The second format allows a fine grain setting of the time limits. Extra args can be added ***in the same value or as additional values***. See olcLimits for an explanation of the different flags.

1 0

(ITS#8153) olcTimeLimit should be Single Value
by elecharny＠apache.org 26 May '15

26 May '15

Full_Name: Emmanuel L.charny Version: 2.4.40 OS: URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (109.190.108.22) The olcTimeLimit is not declared as Single Value : { "timelimit", "limit", 2, 0, 0, ARG_MAY_DB|ARG_MAGIC, &config_timelimit, "( OLcfgGlAt:67 NAME 'olcTimeLimit' " "SYNTAX OMsDirectoryString ) when we have olcSizeLimit declared as : { "sizelimit", "limit", 2, 0, 0, ARG_MAY_DB|ARG_MAGIC, &config_sizelimit, "( OLcfgGlAt:60 NAME 'olcSizeLimit' " "SYNTAX OMsDirectoryString SINGLE-VALUE ) There is a missing "SINGLE-VALUE" in file bconfig.c, on line 660.

1 0

ITS#8088 slapd man pages
by hyc＠symas.com 21 May '15

21 May '15

Closing this as a dup of #7548. -- -- 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

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

openldap-bugs May 2015