openldap-bugs

openldap-bugs@openldap.org

1 participants
21001 discussions

Re: (ITS#9159) mdb_put failed: MDB_MAP_FULL: Environment mapsize limit reached(-30792)
by quanah＠symas.com 29 Jan '20

29 Jan '20

--On Thursday, January 30, 2020 6:09 AM +0000 pasumarthivijaykumar(a)gmail.com wrote: > --00000000000025b743059d554b79 > Content-Type: text/plain; charset="UTF-8" > Content-Transfer-Encoding: quoted-printable > > Thanks for your reply I do know that info for windows also is it the > same.? I am unable to use stats tool also. As I already stated, the maxsize parameter specifies the maximum size the database can reach. > As I don=E2=80=99t see any reply from our many mails to > openldap-technical(a)openldap.org I have created this case to clarify. The openldap-technical list is only open to subscribers, if you want to post to it you must subscribe first. > Why don=E2=80=99t you forward the query to the concerned team instead > closi= ng. Your query would not be forwarded because you failed to read and/or understand the documentation. This system is for bug reports only. > No reply to us.! I did reply. This is clearly shown in the ITS. > Please let us know answer to solve a issue.! I already provided you the answer in my earlier response. Set an approprate maxsize setting, the default of 10MB is clearly too low. Regards, Quanah -- Quanah Gibson-Mount Product Architect Symas Corporation Packaged, certified, and supported LDAP solutions powered by OpenLDAP: <http://www.symas.com>

1 0

Re: (ITS#9159) mdb_put failed: MDB_MAP_FULL: Environment mapsize limit reached(-30792)
by pasumarthivijaykumar＠gmail.com 29 Jan '20

29 Jan '20

--00000000000025b743059d554b79 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Thanks for your reply I do know that info for windows also is it the same.? I am unable to use stats tool also. As I don=E2=80=99t see any reply from our many mails to openldap-technical(a)openldap.org I have created this case to clarify. Why don=E2=80=99t you forward the query to the concerned team instead closi= ng. No reply to us.! Please let us know answer to solve a issue.! On Wed, Jan 29, 2020 at 4:24 PM <openldap-its(a)openldap.org> wrote: > > *** 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#9159. > > 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#9159) > in the subject will automatically be attached to the issue report. > > mailto:openldap-its@openldap.org?subject=3D(ITS#9159) > > 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=3D9159 > > Please remember to retain your issue tracking number (ITS#9159) > 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. > > --=20 Thanks & Regards, Vijay Kumar *+91-94944 44009* --00000000000025b743059d554b79 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable <div dir=3D"ltr"><pre style=3D"background-image:initial;background-position= :initial;background-size:initial;background-repeat:initial;background-origi= n:initial;background-clip:initial;margin:0in 0in 0.0001pt;font-size:10pt;fo= nt-family:"Courier New""><span style=3D"color:black">Thanks for y= our reply I do know that info for windows also is it the same.? I am unable= to use stats tool also.</span></pre><pre style=3D"background-image:initial= ;background-position:initial;background-size:initial;background-repeat:init= ial;background-origin:initial;background-clip:initial;margin:0in 0in 0.0001= pt;font-size:10pt;font-family:"Courier New"">=C2=A0</pre><pre sty= le=3D"background-image:initial;background-position:initial;background-size:= initial;background-repeat:initial;background-origin:initial;background-clip= :initial;margin:0in 0in 0.0001pt;font-size:10pt;font-family:"Courier N= ew""><span style=3D"color:black">As I don=E2=80=99t see any reply from= our many mails to <a href=3D"mailto:openldap-technical@openldap.org" style= =3D"color:rgb(5,99,193)">openldap-technical(a)openldap.org</a> I have created= this case to clarify.</span></pre><pre style=3D"background-image:initial;b= ackground-position:initial;background-size:initial;background-repeat:initia= l;background-origin:initial;background-clip:initial;margin:0in 0in 0.0001pt= ;font-size:10pt;font-family:"Courier New""><span style=3D"color:b= lack">=C2=A0</span></pre><pre style=3D"background-image:initial;background-= position:initial;background-size:initial;background-repeat:initial;backgrou= nd-origin:initial;background-clip:initial;margin:0in 0in 0.0001pt;font-size= :10pt;font-family:"Courier New""><span style=3D"color:black">Why = don=E2=80=99t you forward the query to the concerned team instead closing.<= /span></pre><pre style=3D"background-image:initial;background-position:init= ial;background-size:initial;background-repeat:initial;background-origin:ini= tial;background-clip:initial;margin:0in 0in 0.0001pt;font-size:10pt;font-fa= mily:"Courier New""><span style=3D"color:black">=C2=A0</span></pr= e><pre style=3D"background-image:initial;background-position:initial;backgr= ound-size:initial;background-repeat:initial;background-origin:initial;backg= round-clip:initial;margin:0in 0in 0.0001pt;font-size:10pt;font-family:&quot= ;Courier New""><span style=3D"color:black">No reply to us.!</span></pr= e><pre style=3D"background-image:initial;background-position:initial;backgr= ound-size:initial;background-repeat:initial;background-origin:initial;backg= round-clip:initial;margin:0in 0in 0.0001pt;font-size:10pt;font-family:&quot= ;Courier New""><span style=3D"color:black">=C2=A0</span></pre><pre sty= le=3D"background-image:initial;background-position:initial;background-size:= initial;background-repeat:initial;background-origin:initial;background-clip= :initial;margin:0in 0in 0.0001pt;font-size:10pt;font-family:"Courier N= ew""><span style=3D"color:black">Please let us know answer to solve a = issue.!</span></pre></div><br><div class=3D"gmail_quote"><div dir=3D"ltr" c= lass=3D"gmail_attr">On Wed, Jan 29, 2020 at 4:24 PM <<a href=3D"mailto:o= penldap-its(a)openldap.org">openldap-its(a)openldap.org</a>> wrote:<br></div= ><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border= -left:1px solid rgb(204,204,204);padding-left:1ex"><br> *** THIS IS AN AUTOMATICALLY GENERATED REPLY ***<br> <br> Thanks for your report to the OpenLDAP Issue Tracking System.=C2=A0 Your<br= > report has been assigned the tracking number ITS#9159.<br> <br> One of our support engineers will look at your report in due course.<br> Note that this may take some time because our support engineers<br> are volunteers.=C2=A0 They only work on OpenLDAP when they have spare<br> time.<br> <br> If you need to provide additional information in regards to your<br> issue report, you may do so by replying to this message.=C2=A0 Note that<br= > any mail sent to <a href=3D"mailto:openldap-its@openldap.org" target=3D"_bl= ank">openldap-its(a)openldap.org</a> with (ITS#9159)<br> in the subject will automatically be attached to the issue report.<br> <br> =C2=A0 =C2=A0 =C2=A0 =C2=A0 mailto:<a href=3D"mailto:openldap-its@openldap.= org" target=3D"_blank">openldap-its(a)openldap.org</a>?subject=3D(ITS#9159)<b= r> <br> You may follow the progress of this report by loading the following<br> URL in a web browser:<br> =C2=A0 =C2=A0 <a href=3D"http://www.OpenLDAP.org/its/index.cgi?findid=3D915= 9" rel=3D"noreferrer" target=3D"_blank">http://www.OpenLDAP.org/its/index.c= gi?findid=3D9159</a><br> <br> Please remember to retain your issue tracking number (ITS#9159)<br> on any further messages you send to us regarding this report.=C2=A0 If<br> you don't then you'll just waste our time and yours because we<br> won't be able to properly track the report.<br> <br> Please note that the Issue Tracking System is not intended to<br> be used to seek help in the proper use of OpenLDAP Software.<br> Such requests will be closed.<br> <br> OpenLDAP Software is user supported.<br> =C2=A0 =C2=A0 =C2=A0 =C2=A0 <a href=3D"http://www.OpenLDAP.org/support/" re= l=3D"noreferrer" target=3D"_blank">http://www.OpenLDAP.org/support/</a><br> <br> --------------<br> Copyright 1998-2007 The OpenLDAP Foundation, All Rights Reserved.<br> <br> </blockquote></div><br clear=3D"all"><div><br></div>-- <br><div dir=3D"ltr"= class=3D"gmail_signature"><div dir=3D"ltr"><div><div><font color=3D"#00006= 6">Thanks & Regards,</font></div> <div>=C2=A0</div> <div><font face=3D"arial black,sans-serif">Vijay Kumar</font></div> <div><strong>+91-94944 44009</strong></div></div></div></div> --00000000000025b743059d554b79--

1 0

Re: (ITS#9159) mdb_put failed: MDB_MAP_FULL: Environment mapsize limit reached(-30792)
by quanah＠symas.com 29 Jan '20

29 Jan '20

--On Wednesday, January 29, 2020 10:54 AM +0000 pasumarthivijaykumar(a)gmail.com wrote: > Full_Name: Vijay Kumar > Version: 2.4.48 > OS: Windows > URL: ftp://ftp.openldap.org/incoming/ > Submission from: (NULL) (103.204.96.6) > > > I am not setting any map size for openldap with mdb configuration in > windows. Hello, Usage questions need to be sent to the openldap-technical(a)openldap.org email discussion list. The ITS system is for bug reports only. However, I would suggest carefully reading the slapd-mdb(5) man page, and consider the fact that the maxsize parameter determines what the allowed maximum size of the database is. If you do not set the parameter, it limits the database to 10MB in size (The default value). Regards, Quanah -- Quanah Gibson-Mount Product Architect Symas Corporation Packaged, certified, and supported LDAP solutions powered by OpenLDAP: <http://www.symas.com>

1 0

Re: (ITS#9160) Out-of-memory handling issues
by ondra＠openldap.org 29 Jan '20

29 Jan '20

On Wed, Jan 29, 2020 at 11:46:23AM +0000, Howard Chu wrote: > ondra(a)openldap.org wrote: >> --- malloc_check.cocci --- >> @@ >> expression E, E1; >> identifier ch_alloc =~ "^(ch|slap)_.*alloc.*"; >> identifier f =~ "(?i).*alloc.*"; >> identifier foo; >> @@ >> >> E = >> ( >> ch_alloc > > ch_malloc always aborts if it fails, therefore failure checks are not used. > >> | >> entry_alloc >> | >> attr_alloc >> | > > These rely on ch_malloc, therefore failure checks are not used. > >> metaconn_alloc >> | >> asyncmeta_conn_alloc >> | >> CompAlloc /* component matching has massively bitrotted */ >> | >> * f Which is why only the last one is actually used - '*'. >> )(...); >> ... when != E = E1 >> when != E == NULL >> when != E != NULL >> ( >> E->foo >> | >> E[...] >> | >> *(E) >> ) >> --- malloc_check.cocci --- -- Ondřej Kuzník Senior Software Engineer Symas Corporation http://www.symas.com Packaged, certified, and supported LDAP solutions powered by OpenLDAP

1 0

Re: (ITS#9160) Out-of-memory handling issues
by hyc＠symas.com 29 Jan '20

29 Jan '20

ondra(a)openldap.org wrote: > Full_Name: Ondrej Kuznik > Version: re24/master > OS: > URL: > Submission from: (NULL) (212.159.69.225) > > > A look at the code highlights a few places where *alloc responses are used > unchecked. > > The following semantic patch is a good starting point. Currently it lists 87 > sites most of which probably need adjusting. > > --- malloc_check.cocci --- > @@ > expression E, E1; > identifier ch_alloc =~ "^(ch|slap)_.*alloc.*"; > identifier f =~ "(?i).*alloc.*"; > identifier foo; > @@ > > E = > ( > ch_alloc ch_malloc always aborts if it fails, therefore failure checks are not used. > | > entry_alloc> | > attr_alloc > | These rely on ch_malloc, therefore failure checks are not used. > metaconn_alloc > | > asyncmeta_conn_alloc > | > CompAlloc /* component matching has massively bitrotted */ > | > * f > )(...); > ... when != E = E1 > when != E == NULL > when != E != NULL > ( > E->foo > | > E[...] > | > *(E) > ) > --- malloc_check.cocci --- > > Patches coming soon. > > -- -- 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#9160) Out-of-memory handling issues
by ondra＠openldap.org 29 Jan '20

29 Jan '20

Full_Name: Ondrej Kuznik Version: re24/master OS: URL: Submission from: (NULL) (212.159.69.225) A look at the code highlights a few places where *alloc responses are used unchecked. The following semantic patch is a good starting point. Currently it lists 87 sites most of which probably need adjusting. --- malloc_check.cocci --- @@ expression E, E1; identifier ch_alloc =~ "^(ch|slap)_.*alloc.*"; identifier f =~ "(?i).*alloc.*"; identifier foo; @@ E = ( ch_alloc | entry_alloc | attr_alloc | metaconn_alloc | asyncmeta_conn_alloc | CompAlloc /* component matching has massively bitrotted */ | * f )(...); ... when != E = E1 when != E == NULL when != E != NULL ( E->foo | E[...] | *(E) ) --- malloc_check.cocci --- Patches coming soon.

1 0

(ITS#9159) mdb_put failed: MDB_MAP_FULL: Environment mapsize limit reached(-30792)
by pasumarthivijaykumar＠gmail.com 29 Jan '20

29 Jan '20

Full_Name: Vijay Kumar Version: 2.4.48 OS: Windows URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (103.204.96.6) I am not setting any map size for openldap with mdb configuration in windows. It throws me an error as mentioned below 5e315f30 mdb_id2entry_put: mdb_put failed: MDB_MAP_FULL: Environment mapsize limit reached(-30792) "cn=azrbasisschema.xsd,cn=nl.ciz.awbz.webservice.awbztransformaties.aanvraag_2_io31_transformatie,cn=method sets,o=system,cn=abc,cn=defaultinst,o=abc.net" 5e315f30 conn=1000 op=8 RESULT tag=105 err=80 text=entry store failed 5e315f30 slap_graduate_commit_csn: removing 0000006519FF99A0 20200129103216.169110Z#000000#000#000000 can you please let me know what could be the issue.? I checked the memory used by customer; file system 30GB available out of 200GB, RAM is 24GB. all the way i see suggestions on linux olxDbMaxsize but for windows we dont set that.

1 0

Re: (ITS#9157) return additional error code information when OPT_X_TLS_NEWCTX fails
by shawn.michael.mckinney＠gmail.com 27 Jan '20

27 Jan '20

In one of our test envs, had the path wrong in replication config for = encryption artifacts: *** Conf excerpt: *** syncrepl =E2=80=A6 tls_key=3D/opt/symas/etc/openldap/file-name.pem *** Which gives generic error: *** Log Trace: *** an 27 17:25:17 sapz1a slapd[6203]: slapd starting =E2=80=A6 TLS context initialization failed (-1) Jan 27 17:25:17 hostname slapd[6203]: do_syncrepl: rid=3D031 rc -1 = retrying (4 retries left) *** Would have been helpful for the message to specify which artifact = wasn=E2=80=99t found, the line number of the config, or some other way = of narrowing the problem. =E2=80=94 Shawn

1 0

(ITS#9157) return additional error code information when OPT_X_TLS_NEWCTX fails
by tagrain＠gmail.com 24 Jan '20

24 Jan '20

Full_Name: Thomas Grainger Version: libldap-2.4-2 OS: Ubuntu URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (62.60.6.23) when setting OPT_X_TLS_NEWCTX after an invalid OPT_X_TLS_CACERTFILE libldap returns a generic error code would it be possible to pass the underlying TLS library's error code instead or in addition? https://github.com/python-ldap/python-ldap/issues/55#issuecomment-577831055

1 0

(ITS#9156) latest ppolicy draft support
by ondra＠openldap.org 23 Jan '20

23 Jan '20

Full_Name: Ondrej Kuznik Version: master OS: URL: https://github.com/mistotebe/openldap/tree/ppolicy10 Submission from: (NULL) (212.159.69.225) There have been a few iterations of the ppolicy behera draft and it would be useful to support (some) of the documented features. The following are coming: - pwdGraceExpiry - pwdMaxLength - pwdStartTime and pwdEndTime - pwdMinDelay and pwdMaxDelay (as a soft-lockout, contingent with other implementations based on an informal survey during latest LDAPCon) - pwdMaxIdle (and moving the relevant parts of lastbind overlay into slapd code as it is a shared dependency of a few things now) - the ability to store per-policy arguments to check_password() - updates/fixes to the draft that should have been identified before some of the above were proposed (mostly typos and ASN.1 schema updates)

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