- openldap-bugs - openldap.org

Re: (ITS#5073) Syncrepl spinlock
by ando＠sys-net.it 08 Aug '07

08 Aug '07

> Okay, I figured it out -- This is definitely a misconfiguration type > scenario... > > The database is something like: > > database bdb > base "dc=example,dc=com" > > ... > > Then the syncrepl config has: > searchbase="" > > I'm not sure this is something that should be allowed -- where the search > base is broader than the database. I'm not sure either, but in any case this is triggering a bug: an internal search is performed with base "" and scope "sub"; even though the database is configured to serve "dc=example,dc=com", it answers "success" with no data, since it erroneously treats itself as if handling the empty suffix. I think the bug here is that an internal search should never be invoked without making sure whether the base is within the naming context of the database. If the above configuration does not make sense, the check can be done at configuration; otherwise, it needs to be dealt with from within syncrepl_entry(). I vote for the first. p. Ing. Pierangelo Masarati OpenLDAP Core Team SysNet s.r.l. via Dossi, 8 - 27100 Pavia - ITALIA http://www.sys-net.it --------------------------------------- Office: +39 02 23998309 Mobile: +39 333 4963172 Email: pierangelo.masarati(a)sys-net.it ---------------------------------------

1 0

Re: (ITS#5078) slapd high cpu usage
by marg＠rz.tu-clausthal.de 08 Aug '07

08 Aug '07

Hello, Babu.Suresh(a)pacificlife.com wrote: > bdb_db_open: Warning - No DB_CONFIG file found in directory=20 > Expect poor performance for suffix o=3Dpacificlife.com. Well, slapd even gives you hints for better performance... > <=3D bdb_equality_candidates: (uid) index_param failed (18) > <=3D bdb_equality_candidates: (cn) index_param failed (18) > <=3D bdb_equality_candidates: (uniqueMember) index_param failed (18) Obviously there are some indices missing in the Database. First add configuration for indices cn, uniquemember then re-index/rebuild database. bye Christian -- Christian Marg mail : mailto:marg@rz.tu-clausthal.de Dezernat 2 TU Clausthal web : http://www.tu-clausthal.de D-38678 Clausthal-Zellerfeld fon : 05323/72-2107 Germany jabber: ifcma(a)jabber.tu-clausthal.de

1 0

Re: (ITS#5078) slapd high cpu usage
by ando＠sys-net.it 08 Aug '07

08 Aug '07

Please do not post in HTML. p. Babu.Suresh(a)pacificlife.com wrote: > This is a multi-part message in MIME format. <snip> Ing. Pierangelo Masarati OpenLDAP Core Team SysNet s.r.l. via Dossi, 8 - 27100 Pavia - ITALIA http://www.sys-net.it --------------------------------------- Office: +39 02 23998309 Mobile: +39 333 4963172 Email: pierangelo.masarati(a)sys-net.it ---------------------------------------

1 0

RE: Re: (ITS#5078) slapd high cpu usage
by Babu.Suresh＠pacificlife.com 08 Aug '07

08 Aug '07

This is a multi-part message in MIME format. ------_=_NextPart_001_01C7D93E.7410BF9A Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable OpenLDAP version we are using is - 2.3.32=20 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3DHere is the debug log of one = login=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D bdb_db_open: Warning - No DB_CONFIG file found in directory=20 Expect poor performance for suffix o=3Dpacificlife.com. slapd starting conn=3D0 fd=3D10 ACCEPT from IP=3Dxxxxxxxxx) conn=3D0 op=3D0 BIND dn=3D"uid=3Dxxxxxx,ou=3Dxxxxxxx,ou=3Dxxxx,o=3Dxxxxx" = method=3D128 conn=3D0 op=3D0 BIND dn=3D"uid=3Dxxxxxx,ou=3Dxxxxxxx,ou=3Dxxxx,o=3Dxxxxx" = mech=3DSIMPLE ssf=3D0 conn=3D0 op=3D0 RESULT tag=3D97 err=3D0 text=3D conn=3D0 op=3D1 SRCH base=3D"uid=3Dxxxxxx,ou=3Dxxxxxxx,ou=3Dxxxx,o=3Dxxxxxm= "= scope=3D1 deref=3D0 filter=3D"(&(uid=3Dxxxxxxx)(objectClass=3Dperson))" conn=3D0 op=3D1 SRCH attr=3D1.1 <=3D bdb_equality_candidates: (uid) index_param failed (18) conn=3D0 op=3D2 BIND anonymous mech=3Dimplicit ssf=3D0 conn=3D0 op=3D2 BIND dn=3D"uid=3Dxxxxxx,ou=3Dxxxxxxx,ou=3Dxxxx,o=3Dxxxxx" = method=3D128 conn=3D0 op=3D2 BIND dn=3D"uid=3Dxxxxxx,ou=3Dxxxxxxx,ou=3Dxxxx,o=3Dxxxxx" = mech=3DSIMPLE ssf=3D0 conn=3D0 op=3D2 RESULT tag=3D97 err=3D0 text=3D conn=3D0 op=3D3 BIND anonymous mech=3Dimplicit ssf=3D0 conn=3D0 op=3D3 BIND dn=3D"uid=3Dxxxxxx,ou=3Dxxxxxxx,ou=3Dxxxx,o=3Dxxxxx" = method=3D128 conn=3D0 op=3D3 BIND dn=3D"uid=3Dxxxxxx,ou=3Dxxxxxxx,ou=3Dxxxx,o=3Dxxxxx" = mech=3DSIMPLE ssf=3D0 conn=3D0 op=3D3 RESULT tag=3D97 err=3D0 text=3D conn=3D1 fd=3D12 ACCEPT from IP=3D12.12.1.11:40660 = (IP=3D10.141.1.217:121212) conn=3D1 op=3D0 BIND dn=3D"uid=3Dxxxxxx,ou=3Dxxxxxxx,ou=3Dxxxx,o=3Dxxxxx" = method=3D128 conn=3D1 op=3D0 BIND dn=3D"uid=3Dxxxxxx,ou=3Dxxxxxxx,ou=3Dxxxx,o=3Dxxxxx" = mech=3DSIMPLE ssf=3D0 conn=3D1 op=3D0 RESULT tag=3D97 err=3D0 text=3D conn=3D1 op=3D1 SRCH base=3D"ou=3DPeople,ou=3DInternet,o=3Dpacificlife.com"= = scope=3D1 deref=3D0 filter=3D"(&(uid=3Dplevone)(objectClass=3Dperson))" conn=3D1 op=3D1 SRCH attr=3D1.1 <=3D bdb_equality_candidates: (uid) index_param failed (18) conn=3D1 op=3D2 SRCH base=3D"ou=3Dxxxxxxx,ou=3Dxxxx,o=3Dxxxxx" scope=3D1 = deref=3D0 =66ilter=3D"(&(uniqueMember=3Duid=3Dplevone,ou=3Dpeople,ou=3Dinternet,o=3Dp= acificlife. com)(objectClass=3DgroupOfUniqueNames))" conn=3D1 op=3D2 SRCH attr=3Dcn <=3D bdb_equality_candidates: (uniqueMember) index_param failed (18) conn=3D0 op=3D4 SRCH base=3D"ou=3Dxxxxxxx,ou=3Dxxxx,o=3Dxxxxx" scope=3D1 = deref=3D0 =66ilter=3D"(|(&(cn=3Dpresenters)(objectClass=3DgroupOfUniqueNames))(&(cn= =3Dpresen ters)(objectClass=3DgroupOfURLs)))" conn=3D0 op=3D4 SRCH attr=3D1.1 <=3D bdb_equality_candidates: (cn) index_param failed (18) <=3D bdb_equality_candidates: (cn) index_param failed (18) conn=3D0 op=3D5 SRCH base=3D"ou=3Dxxxxxxx,ou=3Dxxxx,o=3Dxxxxx" scope=3D1 = deref=3D0 =66ilter=3D"(&(uniqueMember=3Dcn=3Dpresenters,ou=3Dxxxxxxx,ou=3Dxxxx,o=3Dxx= xxx)(object Class=3DgroupOfUniqueNames))" conn=3D0 op=3D5 SRCH attr=3Dcn <=3D bdb_equality_candidates: (uniqueMember) index_param failed (18) conn=3D1 op=3D2 SEARCH RESULT tag=3D101 err=3D0 nentries=3D1 text=3D conn=3D0 op=3D4 SEARCH RESULT tag=3D101 err=3D0 nentries=3D1 text=3D conn=3D0 op=3D5 SEARCH RESULT tag=3D101 err=3D0 nentries=3D0 text=3D conn=3D1 op=3D3 SRCH base=3D"ou=3Dxxxxxxx,ou=3Dxxxx,o=3Dxxxxx" scope=3D1 = deref=3D0 =66ilter=3D"(objectClass=3DgroupOfURLs)" conn=3D1 op=3D3 SRCH attr=3Dcn memberURL conn=3D1 op=3D3 SEARCH RESULT tag=3D101 err=3D0 nentries=3D0 text=3D conn=3D1 op=3D1 SEARCH RESULT tag=3D101 err=3D0 nentries=3D1 text=3D =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D ---------------------------------------------------------------------------= --- The information in this e-mail and any attachments are for the sole use of = the intended recipient and may contain privileged and confidential = information. If you are not the intended recipient, any use, disclosure, = copying or distribution of this message or attachment is strictly = prohibited. If you believe that you have received this e-mail in error, = please contact the sender immediately and delete the e-mail and all of its = attachments. =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D ------_=_NextPart_001_01C7D93E.7410BF9A Content-Type: text/html; charset=us-ascii Content-Transfer-Encoding: quoted-printable <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> <HTML> <HEAD> <META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; charset=3Dus-ascii"> <META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version 6.5.7651.59"> <TITLE>RE: Re: (ITS#5078) slapd high cpu usage</TITLE> </HEAD> <BODY>  OpenLDAP version we are = using is - 2.3.32 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3DHere is the debug log of = one login=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D bdb_db_open: Warning - = No DB_CONFIG file found in directory Expect poor performance= = =66or suffix o=3Dpacificlife.com. slapd starting conn=3D0 fd=3D10 ACCEPT= = =66rom IP=3Dxxxxxxxxx) conn=3D0 op=3D0 BIND = dn=3D"uid=3Dxxxxxx,ou=3Dxxxxxxx,ou=3Dxxxx,o=3Dxxxxx" = method=3D128 conn=3D0 op=3D0 BIND = dn=3D"uid=3Dxxxxxx,ou=3Dxxxxxxx,ou=3Dxxxx,o=3Dxxxxx" mech=3DSIMPL= E= ssf=3D0 conn=3D0 op=3D0 RESULT = tag=3D97 err=3D0 text=3D conn=3D0 op=3D1 SRCH = base=3D"uid=3Dxxxxxx,ou=3Dxxxxxxx,ou=3Dxxxx,o=3Dxxxxxm" scope=3D1= = deref=3D0 = =66ilter=3D"(&(uid=3Dxxxxxxx)(objectClass=3Dperson))"<= /P> conn=3D0 op=3D1 SRCH = attr=3D1.1 <=3D = bdb_equality_candidates: (uid) index_param failed (18) conn=3D0 op=3D2 BIND = anonymous mech=3Dimplicit ssf=3D0 conn=3D0 op=3D2 BIND = dn=3D"uid=3Dxxxxxx,ou=3Dxxxxxxx,ou=3Dxxxx,o=3Dxxxxx" = method=3D128 conn=3D0 op=3D2 BIND = dn=3D"uid=3Dxxxxxx,ou=3Dxxxxxxx,ou=3Dxxxx,o=3Dxxxxx" mech=3DSIMPL= E= ssf=3D0 conn=3D0 op=3D2 RESULT = tag=3D97 err=3D0 text=3D conn=3D0 op=3D3 BIND = anonymous mech=3Dimplicit ssf=3D0 conn=3D0 op=3D3 BIND = dn=3D"uid=3Dxxxxxx,ou=3Dxxxxxxx,ou=3Dxxxx,o=3Dxxxxx" = method=3D128 conn=3D0 op=3D3 BIND = dn=3D"uid=3Dxxxxxx,ou=3Dxxxxxxx,ou=3Dxxxx,o=3Dxxxxx" mech=3DSIMPL= E= ssf=3D0 conn=3D0 op=3D3 RESULT = tag=3D97 err=3D0 text=3D conn=3D1 fd=3D12 ACCEPT= = =66rom IP=3D12.12.1.11:40660 (IP=3D10.141.1.217:121212) conn=3D1 op=3D0 BIND = dn=3D"uid=3Dxxxxxx,ou=3Dxxxxxxx,ou=3Dxxxx,o=3Dxxxxx" = method=3D128 conn=3D1 op=3D0 BIND = dn=3D"uid=3Dxxxxxx,ou=3Dxxxxxxx,ou=3Dxxxx,o=3Dxxxxx" mech=3DSIMPL= E= ssf=3D0 conn=3D1 op=3D0 RESULT = tag=3D97 err=3D0 text=3D conn=3D1 op=3D1 SRCH = base=3D"ou=3DPeople,ou=3DInternet,o=3Dpacificlife.com" scope=3D1 = deref=3D0 = =66ilter=3D"(&(uid=3Dplevone)(objectClass=3Dperson))"<= /P> conn=3D1 op=3D1 SRCH = attr=3D1.1 <=3D = bdb_equality_candidates: (uid) index_param failed (18) conn=3D1 op=3D2 SRCH = base=3D"ou=3Dxxxxxxx,ou=3Dxxxx,o=3Dxxxxx" scope=3D1 deref=3D0 = =66ilter=3D"(&(uniqueMember=3Duid=3Dplevone,ou=3Dpeople,ou=3Dinter= net,o=3Dpacificlife.com)(objectClass=3DgroupOfUniqueNames))" conn=3D1 op=3D2 SRCH = attr=3Dcn <=3D = bdb_equality_candidates: (uniqueMember) index_param failed (18) conn=3D0 op=3D4 SRCH = base=3D"ou=3Dxxxxxxx,ou=3Dxxxx,o=3Dxxxxx" scope=3D1 deref=3D0 = =66ilter=3D"(|(&(cn=3Dpresenters)(objectClass=3DgroupOfUniqueNames= ))(&(cn=3Dpresenters)(objectClass=3DgroupOfURLs)))" conn=3D0 op=3D4 SRCH = attr=3D1.1 <=3D = bdb_equality_candidates: (cn) index_param failed (18) <=3D = bdb_equality_candidates: (cn) index_param failed (18) conn=3D0 op=3D5 SRCH = base=3D"ou=3Dxxxxxxx,ou=3Dxxxx,o=3Dxxxxx" scope=3D1 deref=3D0 = =66ilter=3D"(&(uniqueMember=3Dcn=3Dpresenters,ou=3Dxxxxxxx,ou=3Dxx= xx,o=3Dxxxxx)(objectClass=3DgroupOfUniqueNames))" conn=3D0 op=3D5 SRCH = attr=3Dcn <=3D = bdb_equality_candidates: (uniqueMember) index_param failed (18) conn=3D1 op=3D2 SEARCH = RESULT tag=3D101 err=3D0 nentries=3D1 text=3D conn=3D0 op=3D4 SEARCH = RESULT tag=3D101 err=3D0 nentries=3D1 text=3D conn=3D0 op=3D5 SEARCH = RESULT tag=3D101 err=3D0 nentries=3D0 text=3D conn=3D1 op=3D3 SRCH = base=3D"ou=3Dxxxxxxx,ou=3Dxxxx,o=3Dxxxxx" scope=3D1 deref=3D0 = =66ilter=3D"(objectClass=3DgroupOfURLs)" conn=3D1 op=3D3 SRCH = attr=3Dcn memberURL conn=3D1 op=3D3 SEARCH = RESULT tag=3D101 err=3D0 nentries=3D0 text=3D conn=3D1 op=3D1 SEARCH = RESULT tag=3D101 err=3D0 nentries=3D1 text=3D =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D <pre = wrap>----------------------------------------------------------------------= -------- The information in this e-mail and any attachments are for the sole use of = the intended recipient and may contain privileged and confidential = information. If you are not the intended recipient, any use, disclosure, = copying or distribution of this message or attachment is strictly = prohibited. If you believe that you have received this e-mail in error, = please contact the sender immediately and delete the e-mail and all of its = attachments. =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D </pre></BODY> </HTML> ------_=_NextPart_001_01C7D93E.7410BF9A--

1 0

Re: (ITS#5078) slapd high cpu usage
by Babu.Suresh＠pacificlife.com 07 Aug '07

07 Aug '07

This is a multi-part message in MIME format. ------_=_NextPart_001_01C7D93C.273C1782 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable thank you Quanah for your quick response. see bellow.. What version of OpenLDAP 2.3=3F -->V2.3.4 Have you configured the DB_CONFIG file=3F -->NO You can still use cachesize whether or not it is restarted nightly. -->will do Have you examined the logs at loglevel 256 to see what kind of searches are being performed, so you can optimize your indices=3F -->yes, we did but I didn't put much attention to this. I will perform again and post the output. thank you ---------------------------------------------------------------------------= --- The information in this e-mail and any attachments are for the sole use of = the intended recipient and may contain privileged and confidential = information. If you are not the intended recipient, any use, disclosure, = copying or distribution of this message or attachment is strictly = prohibited. If you believe that you have received this e-mail in error, = please contact the sender immediately and delete the e-mail and all of its = attachments. =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D ------_=_NextPart_001_01C7D93C.273C1782 Content-Type: text/html; charset=us-ascii Content-Transfer-Encoding: quoted-printable <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> <HTML> <HEAD> <META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; charset=3Dus-ascii"> <META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version 6.5.7651.59"> <TITLE>Re: (ITS#5078) slapd high cpu usage</TITLE> </HEAD> <BODY>  thank you Quanah for your quick = response. see bellow.. What version of OpenLDAP = 2.3=3F -->V2.3.4 Have you configured the DB_CONFIG = =66ile=3F -->NO You can still use cachesize whether= = or not it is restarted nightly. -->will do Have you examined the logs at = loglevel 256 to see what kind of searches are being performed, so you can = optimize your indices=3F -->yes, we did but I didn't put = much attention to this. I will perform again and post the output. thank you <pre = wrap>----------------------------------------------------------------------= -------- The information in this e-mail and any attachments are for the sole use of = the intended recipient and may contain privileged and confidential = information. If you are not the intended recipient, any use, disclosure, = copying or distribution of this message or attachment is strictly = prohibited. If you believe that you have received this e-mail in error, = please contact the sender immediately and delete the e-mail and all of its = attachments. =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D </pre></BODY> </HTML> ------_=_NextPart_001_01C7D93C.273C1782--

1 0

Re: (ITS#5078) slapd high cpu usage
by quanah＠zimbra.com 07 Aug '07

07 Aug '07

--On Tuesday, August 07, 2007 6:25 PM +0000 babu.suresh(a)pacificlife.com wrote: > Full_Name: Babu > Version: 2.3 > OS: RedHAT3 > URL: ftp://ftp.openldap.org/incoming/ > Submission from: (NULL) (198.181.11.27) > > > Hello, > > > We are using openldap2.3, BDB 4.5.20 and Rehat3..seeing having high cpu > usage of the slapd process. What version of OpenLDAP 2.3? Have you configured the DB_CONFIG file? You can still use cachesize whether or not it is restarted nightly. Have you examined the logs at loglevel 256 to see what kind of searches are being performed, so you can optimize your indices? In any case, I see no bug here. Please redirect further questions and response to openldap-software(a)openldap.org --Quanah -- Quanah Gibson-Mount Principal Software Engineer Zimbra, Inc -------------------- Zimbra :: the leader in open source messaging and collaboration

1 0

(ITS#5078) slapd high cpu usage
by babu.suresh＠pacificlife.com 07 Aug '07

07 Aug '07

Full_Name: Babu Version: 2.3 OS: RedHAT3 URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (198.181.11.27) Hello, We are using openldap2.3, BDB 4.5.20 and Rehat3..seeing having high cpu usage of the slapd process. Tried with bellow indexes, we can't use "cachesize" as we have nightly restart of the process and cache go away (let me know there is way to save cache and it will be available even after restart of slapd); also we have yearly onetime users in our system. Please let me know what are can be done to solve slapd high cpu utilization problem. ====indexes in slapd.conf==== index objectClass eq index uid pres, eq ========= =========CPU usage with 3/4 users concurrent login========= 321 processes: 319 sleeping, 2 running, 0 zombie, 0 stopped CPU states: cpu user nice system irq softirq iowait idle total 28.0% 0.0% 7.8% 0.0% 0.0% 7.9% 56.0% cpu00 47.6% 0.0% 8.9% 0.0% 0.3% 2.3% 40.6% cpu01 32.8% 0.0% 7.7% 0.0% 0.0% 0.7% 58.6% cpu02 19.4% 0.0% 8.1% 0.0% 0.0% 14.1% 58.2% cpu03 12.1% 0.0% 6.5% 0.0% 0.0% 14.5% 66.7% PID USER PRI NI SIZE RSS SHARE STAT %CPU %MEM TIME CPU COMMAND 30973 xxxxx 19 0 148M 148M 2224 R 15.4 3.1 4:44 0 slapd 30975 xxxxx 18 0 148M 148M 2224 S 9.5 3.1 3:51 3 slapd 32030 xxxxxx 19 0 148M 148M 2224 S 7.9 3.1 3:59 1 slapd

1 0

Coredump on ACLs for nonexistent Attributes. Is it a bug?
by Christian Marg 07 Aug '07

07 Aug '07

Hello, I didn't find an ITS concerning what I encountered yesterday: I had ACLs defined for undefined attributes (e.g. a schema file was missing some entries) and slaptest etc. crashed with dumped core. The message I got was: slaptest in free(): error: junk pointer, too high to make sense Abort (core dumped) I'm using v 2.3.34 on FreeBSD 6.2-RELEASE-p3. bye Christian -- Christian Marg mail : mailto:marg@rz.tu-clausthal.de Dezernat 2 TU Clausthal web : http://www.tu-clausthal.de D-38678 Clausthal-Zellerfeld fon : 05323/72-2107 Germany jabber: ifcma(a)jabber.tu-clausthal.de

2 2

Re: Contribution: Active Directory Password Cache (ITS#5042)
by ando＠sys-net.it 07 Aug '07

07 Aug '07

ando(a)sys-net.it wrote: > At this point, it sounds like that your contribution could be > __entirely__ reworked into simply adding caching capabilities into the > current {SASL} password scheme (implemented in servers/slapd/sasl.c), > preserving the logics you're using right now. You'd probably need to > define your own "cachedUserPassword" attribute to temporarily store the > cached credentials, unless something like this: > > userPassword: {SASL}user > userPassword: {<hash>}<hashed password> > > allows the {SASL} module to fetch the next value of the userPassowrd and > treat it as the cached value. The rest would be adding some TTL mech, > configurable via back-config, and that should be it. > > Yet another option would be to allow per-entry caching, by defining a > new {CACHED-SASL} scheme. This way, one could fine-grain decide whose > credentials can be cached and whose can't, letting the two cases share > most of the code. I'd allow {SASL} to be cached as well, in case the > administrator just wants to allow all {SASL} auths to be cached. For this purpose, it might be necessary to change the API of password scheme handling, so that it gets passed a pointer to the entire entry, read-only locked, so that attributes like the "cachedPwd" and the "cachedPwdTimestamp" can be fetched and used. With respect to updating them, we might need to add some means to schedule internal modifications to be performed as soon as the entry lock is released. Thoughts? p. Ing. Pierangelo Masarati OpenLDAP Core Team SysNet s.r.l. via Dossi, 8 - 27100 Pavia - ITALIA http://www.sys-net.it --------------------------------------- Office: +39 02 23998309 Mobile: +39 333 4963172 Email: pierangelo.masarati(a)sys-net.it ---------------------------------------

1 0

Re: Contribution: Active Directory Password Cache (ITS#5042)
by ando＠sys-net.it 07 Aug '07

07 Aug '07

s.hetze(a)linux-ag.de wrote: > Renaming the variables is no problem. What would you say extpwc stands > for? EXT ernal P ass W ord C ache? > I can imagine to call the module krb5pwc and head the README > "Kerberos V/Active Directory Password Cache" Right; but, this would limit yourself to Kerberos V; see my other posting about rather delegating auth to SASL. >> Well, that could be a parameter that is provided through the >> configuration (caching TTL, optional negative caching TTL, and so). It >> doesn't need to be stored in the entry, or in a subentry, since dynamic >> configuration would allow to modify it run-time anyway. >> > > If I understand it correct, you suggest to let the cached password > expire after some configurable time. To achieve this, I would need to > keep a timestamp when the password was cached. > Is there any other way than to add an attribute holding this timestamp? > ... > Actually, I could make this feature depend on the {ad|krb5}pw-cache-mode=any > and use the sambaPwdLastSet attribute. Right; I think a specific operational attribute would be better. p. Ing. Pierangelo Masarati OpenLDAP Core Team SysNet s.r.l. via Dossi, 8 - 27100 Pavia - ITALIA http://www.sys-net.it --------------------------------------- Office: +39 02 23998309 Mobile: +39 333 4963172 Email: pierangelo.masarati(a)sys-net.it ---------------------------------------

1 0

Re: Contribution: Active Directory Password Cache (ITS#5042)
by s.hetze＠linux-ag.de 07 Aug '07

07 Aug '07

Hi Pierangelo, On Tue, Aug 07, 2007 at 11:41:58AM +0200, Pierangelo Masarati wrote: > s.hetze(a)linux-ag.de wrote: > > >>2) you could try to rework the overlay to avoid any specific reference > >>to Active Directory, since your cache should apply to any remote system > >>implementing Kerberos V. It could be abstracted even more, to act as a > >>replacement of saslauthd, by allowing it to auth via LDAP, pam and more, > >>not just Kerberos. > > > >Actually, the software was built and tested agains MIT and Heimdal > >Kerberos V in the first place, so there is no dependency on AD > >whatsoever. The reference to AD is more a marketing issue. I assume > >more users looking for an AD password cache than for an Kerberos V > >password cache. So I would perfer to keep it. > > I understand this, and I think it's just fine to advertise it like that, > but in the code I'd prefer to avoid, for example, naming all variables > after "ad" something. Perhaps s/adpwc/extpwc/ would be a little bit better? Renaming the variables is no problem. What would you say extpwc stands for? I can imagine to call the module krb5pwc and head the README "Kerberos V/Active Directory Password Cache" > > >>3) you should add a (configurable) TTL, so that the cache could > >>eventually be notified of an account lockout at the remote server's side. > > > >I tried to avoid introduction of new attributes for the module. Do you > >have any suggestions how this TTL should be stored? Adding pwdPolicy > >from ppolicy seems a bit like an overkill to me. > > Well, that could be a parameter that is provided through the > configuration (caching TTL, optional negative caching TTL, and so). It > doesn't need to be stored in the entry, or in a subentry, since dynamic > configuration would allow to modify it run-time anyway. > If I understand it correct, you suggest to let the cached password expire after some configurable time. To achieve this, I would need to keep a timestamp when the password was cached. Is there any other way than to add an attribute holding this timestamp? ... Actually, I could make this feature depend on the {ad|krb5}pw-cache-mode=any and use the sambaPwdLastSet attribute. > >>4) you should add support for dynamic configuration, so that the module > >>can fit into the new configuration paradigm for possible release with 2.4. > > > >I'll look into that. > > If you need help, please holler. However, I see that for such a simple > (from a configuration point of view) module, looking into smbk5pwd > should suffice. Thanx for your offer, and I agree to look into the existing overlays (again ;-) That's the fun with free software! Regards, Sebastian

1 0

Re: Contribution: Active Directory Password Cache (ITS#5042)
by ando＠sys-net.it 07 Aug '07

07 Aug '07

s.hetze(a)linux-ag.de wrote: > I don't see the benefit of delegating the password cache mechanism to > saslauthd or a possible replacement. Wouldn't I have to implement each > possible password store anyway? > If I understand it correct, the {SASL} userPassword mechanism delegates > authentication to saslauthd. > saslauthd can easily authenticate against Kerberos and AD and it is > possible let it cache the password for its own authentication purposes. > If I want the sambaNTPassword attribute to be available (to be able to > run samba as a NT4 PDC independent of AD ) or if I want to have the > password additionally cached as MIT Kerberos credential, I would need > to implement both individually one way or another. > So why not going the short way and let the overlay module do this? The {SASL} userPassword delegates authentication to SASL; then, by configuring SASL to use saslauthd, SASL delegates authentication to saslauthd, but it can be delegated to anything else. I think the point is: you should isolate what your piece of software is originally contributing, and what it's "reinventing". The original contribution, as far as I understand, is the capability to cache athentication rather than always propagating it. This capability is not currently present in OpenLDAP. What is already present is the SASL, which is an abstraction layer for authentication; think of it as a superset of Kerberos, which is the only authentication method you're considering in your piece of software. At this point, it sounds like that your contribution could be __entirely__ reworked into simply adding caching capabilities into the current {SASL} password scheme (implemented in servers/slapd/sasl.c), preserving the logics you're using right now. You'd probably need to define your own "cachedUserPassword" attribute to temporarily store the cached credentials, unless something like this: userPassword: {SASL}user userPassword: {<hash>}<hashed password> allows the {SASL} module to fetch the next value of the userPassowrd and treat it as the cached value. The rest would be adding some TTL mech, configurable via back-config, and that should be it. Yet another option would be to allow per-entry caching, by defining a new {CACHED-SASL} scheme. This way, one could fine-grain decide whose credentials can be cached and whose can't, letting the two cases share most of the code. I'd allow {SASL} to be cached as well, in case the administrator just wants to allow all {SASL} auths to be cached. p. Ing. Pierangelo Masarati OpenLDAP Core Team SysNet s.r.l. via Dossi, 8 - 27100 Pavia - ITALIA http://www.sys-net.it --------------------------------------- Office: +39 02 23998309 Mobile: +39 333 4963172 Email: pierangelo.masarati(a)sys-net.it ---------------------------------------

1 0

Re: Contribution: Active Directory Password Cache (ITS#5042)
by s.hetze＠linux-ag.de 07 Aug '07

07 Aug '07

Hi Kurt, On Mon, Aug 06, 2007 at 12:55:11PM -0700, Kurt Zeilenga wrote: > >2) you could try to rework the overlay to avoid any specific reference > >to Active Directory, since your cache should apply to any remote > >system > >implementing Kerberos V. It could be abstracted even more, to act > >as a > >replacement of saslauthd, by allowing it to auth via LDAP, pam and > >more, > >not just Kerberos. > > s/to act as a replacement/to defer external authentication to saslauthd > or the like/ > > In slapd(8), we deferred verification against external password > stores to saslauthd > via the {SASL} userPassword mechanism, thus avoiding needing to > implement > and support each possible external password store (such as a KDC). > This module > should likewise avoid supporting (some subset of) external passwords > stores. > saslauthd(8) can easily be extended (or replaced) to support additional > password stores as needed. As provided in Cyrus SASL today, it > supports both > LDAP and Kerberos as external password stores. > I don't see the benefit of delegating the password cache mechanism to saslauthd or a possible replacement. Wouldn't I have to implement each possible password store anyway? If I understand it correct, the {SASL} userPassword mechanism delegates authentication to saslauthd. saslauthd can easily authenticate against Kerberos and AD and it is possible let it cache the password for its own authentication purposes. If I want the sambaNTPassword attribute to be available (to be able to run samba as a NT4 PDC independent of AD ) or if I want to have the password additionally cached as MIT Kerberos credential, I would need to implement both individually one way or another. So why not going the short way and let the overlay module do this? Regards, Sebastian

1 0

Re: Contribution: Active Directory Password Cache (ITS#5042)
by ando＠sys-net.it 07 Aug '07

07 Aug '07

s.hetze(a)linux-ag.de wrote: >> 2) you could try to rework the overlay to avoid any specific reference >> to Active Directory, since your cache should apply to any remote system >> implementing Kerberos V. It could be abstracted even more, to act as a >> replacement of saslauthd, by allowing it to auth via LDAP, pam and more, >> not just Kerberos. > > Actually, the software was built and tested agains MIT and Heimdal > Kerberos V in the first place, so there is no dependency on AD > whatsoever. The reference to AD is more a marketing issue. I assume > more users looking for an AD password cache than for an Kerberos V > password cache. So I would perfer to keep it. I understand this, and I think it's just fine to advertise it like that, but in the code I'd prefer to avoid, for example, naming all variables after "ad" something. Perhaps s/adpwc/extpwc/ would be a little bit better? >> 3) you should add a (configurable) TTL, so that the cache could >> eventually be notified of an account lockout at the remote server's side. > > I tried to avoid introduction of new attributes for the module. Do you > have any suggestions how this TTL should be stored? Adding pwdPolicy > from ppolicy seems a bit like an overkill to me. Well, that could be a parameter that is provided through the configuration (caching TTL, optional negative caching TTL, and so). It doesn't need to be stored in the entry, or in a subentry, since dynamic configuration would allow to modify it run-time anyway. >> 4) you should add support for dynamic configuration, so that the module >> can fit into the new configuration paradigm for possible release with 2.4. > > I'll look into that. If you need help, please holler. However, I see that for such a simple (from a configuration point of view) module, looking into smbk5pwd should suffice. >> 5) you should follow coding guidelines (indentation and so) as in most >> of the code. > > I did not find any guidelines other than "Adapt your style to match that > of the block, file, directory, or package that you are working in." > Can you point me to a more detailed explanation of the required > indentation? There isn't actually, but looking into any "recent" piece of code would suffice; things like: use tabs for indent, leave spaces in brackets and so... not a big deal, though. Cheers, p. Ing. Pierangelo Masarati OpenLDAP Core Team SysNet s.r.l. via Dossi, 8 - 27100 Pavia - ITALIA http://www.sys-net.it --------------------------------------- Office: +39 02 23998309 Mobile: +39 333 4963172 Email: pierangelo.masarati(a)sys-net.it ---------------------------------------

1 0

Re: Contribution: Active Directory Password Cache (ITS#5042)
by s.hetze＠linux-ag.de 07 Aug '07

07 Aug '07

Hi Pierangelo, thanx for your comments. On Mon, Aug 06, 2007 at 09:32:27PM +0200, Pierangelo Masarati wrote: > Sebastian, > > Thanks for the contribution. > > I have a few comments (also gathered from others): > > 1) you should provide patches against HEAD code; there has been some > limited changes in the API related to overlay initialization and so. No problem, I will look into that shortly. > > 2) you could try to rework the overlay to avoid any specific reference > to Active Directory, since your cache should apply to any remote system > implementing Kerberos V. It could be abstracted even more, to act as a > replacement of saslauthd, by allowing it to auth via LDAP, pam and more, > not just Kerberos. Actually, the software was built and tested agains MIT and Heimdal Kerberos V in the first place, so there is no dependency on AD whatsoever. The reference to AD is more a marketing issue. I assume more users looking for an AD password cache than for an Kerberos V password cache. So I would perfer to keep it. > > 3) you should add a (configurable) TTL, so that the cache could > eventually be notified of an account lockout at the remote server's side. I tried to avoid introduction of new attributes for the module. Do you have any suggestions how this TTL should be stored? Adding pwdPolicy from ppolicy seems a bit like an overkill to me. > > 4) you should add support for dynamic configuration, so that the module > can fit into the new configuration paradigm for possible release with 2.4. I'll look into that. > > 5) you should follow coding guidelines (indentation and so) as in most > of the code. I did not find any guidelines other than "Adapt your style to match that of the block, file, directory, or package that you are working in." Can you point me to a more detailed explanation of the required indentation? Regards, Sebastian

1 0

(ITS#5077) syncrepl.add_cmp() infinite loop on swapped values
by donn＠u.washington.edu 06 Aug '07

06 Aug '07

Full_Name: Donn Cave Version: 2.4.4 OS: Red Hat Linux URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (128.95.135.150) In "while" loop at 2656, I find old->a_vals are like [..., a, b, ...] and new->a_vals are like [..., b, a, ...]. Matches are found at old [i] == new [k = j+1] and old [k = i+1] == new [j], but this just shows that neither an add nor a delete is called for, and the loop end is reached without having incremented i or j. Actual attribute values I'm looking at right now in the debugger are eduPersonAffiliation: old [ member, alum, employee, faculty ], new [ member, alum, faculty, employee ]. I built the replica from a slapcat dump on the idle master, started the slapd syncrepl client and applied a lot of normal modifications to the master, until it hit the infinite loop. It has been a recurrent problem.

1 0

Re: Contribution: Active Directory Password Cache (ITS#5042)
by kurt＠OpenLDAP.org 06 Aug '07

06 Aug '07

On Aug 6, 2007, at 7:31 PM, ando(a)sys-net.it wrote: > Sebastian, > > Thanks for the contribution. > > I have a few comments (also gathered from others): > > 1) you should provide patches against HEAD code; there has been some > limited changes in the API related to overlay initialization and so. > > 2) you could try to rework the overlay to avoid any specific reference > to Active Directory, since your cache should apply to any remote > system > implementing Kerberos V. It could be abstracted even more, to act > as a > replacement of saslauthd, by allowing it to auth via LDAP, pam and > more, > not just Kerberos. s/to act as a replacement/to defer external authentication to saslauthd or the like/ In slapd(8), we deferred verification against external password stores to saslauthd via the {SASL} userPassword mechanism, thus avoiding needing to implement and support each possible external password store (such as a KDC). This module should likewise avoid supporting (some subset of) external passwords stores. saslauthd(8) can easily be extended (or replaced) to support additional password stores as needed. As provided in Cyrus SASL today, it supports both LDAP and Kerberos as external password stores. > > 3) you should add a (configurable) TTL, so that the cache could > eventually be notified of an account lockout at the remote server's > side. > > 4) you should add support for dynamic configuration, so that the > module > can fit into the new configuration paradigm for possible release > with 2.4. > > 5) you should follow coding guidelines (indentation and so) as in most > of the code. > > p.

1 0

Re: Contribution: Active Directory Password Cache (ITS#5042)
by ando＠sys-net.it 06 Aug '07

06 Aug '07

Sebastian, Thanks for the contribution. I have a few comments (also gathered from others): 1) you should provide patches against HEAD code; there has been some limited changes in the API related to overlay initialization and so. 2) you could try to rework the overlay to avoid any specific reference to Active Directory, since your cache should apply to any remote system implementing Kerberos V. It could be abstracted even more, to act as a replacement of saslauthd, by allowing it to auth via LDAP, pam and more, not just Kerberos. 3) you should add a (configurable) TTL, so that the cache could eventually be notified of an account lockout at the remote server's side. 4) you should add support for dynamic configuration, so that the module can fit into the new configuration paradigm for possible release with 2.4. 5) you should follow coding guidelines (indentation and so) as in most of the code. p. Ing. Pierangelo Masarati OpenLDAP Core Team SysNet s.r.l. via Dossi, 8 - 27100 Pavia - ITALIA http://www.sys-net.it --------------------------------------- Office: +39 02 23998309 Mobile: +39 333 4963172 Email: pierangelo.masarati(a)sys-net.it ---------------------------------------

1 0

Re: (ITS#5073) Syncrepl spinlock
by quanah＠zimbra.com 06 Aug '07

06 Aug '07

--On August 6, 2007 5:01:08 PM +0000 quanah(a)zimbra.com wrote: > > > --On August 6, 2007 9:17:01 AM +0000 ando(a)sys-net.it wrote: > >> quanah(a)OpenLDAP.org wrote: >>> Full_Name: Quanah Gibson-Mount >>> Version: 2.3.37 >>> OS: Linux >>> URL: >>> Submission from: (NULL) (71.202.148.128) >>> >>> >>> If you create a syncrepl master that serves the "" base, and then set up >>> a syncrepl consumer to pull down "dc=example,dc=com", which does *not* >>> exist on the master, the replica will sit at 100% CPU, endlessly trying >>> to add nothing. >> >> I'm not observing this with either re23 nor HEAD. The initial search >> correctly fails with noSuchObject, and then both slapds sit at 0% CPU. >> Can you give further details? > > I'll look at reproducing it again. > > In this particular case, the master had a database rooted at "", with > some data around "cn=zimbra" contained in it. A replica was configured > as a syncrepl client, but with "dc=example,dc=com" as its base, by > mistake. This resulted in the CPU usage shooting to 100% on the replica, > and the logs showing it trying to add without success. Okay, I figured it out -- This is definitely a misconfiguration type scenario... The database is something like: database bdb base "dc=example,dc=com" ... Then the syncrepl config has: searchbase="" I'm not sure this is something that should be allowed -- where the search base is broader than the database. --Quanah -- Quanah Gibson-Mount Principal Software Engineer Zimbra, Inc -------------------- Zimbra :: the leader in open source messaging and collaboration

1 0

Re: (ITS#5073) Syncrepl spinlock
by quanah＠zimbra.com 06 Aug '07

06 Aug '07

--On August 6, 2007 9:17:01 AM +0000 ando(a)sys-net.it wrote: > quanah(a)OpenLDAP.org wrote: >> Full_Name: Quanah Gibson-Mount >> Version: 2.3.37 >> OS: Linux >> URL: >> Submission from: (NULL) (71.202.148.128) >> >> >> If you create a syncrepl master that serves the "" base, and then set up >> a syncrepl consumer to pull down "dc=example,dc=com", which does *not* >> exist on the master, the replica will sit at 100% CPU, endlessly trying >> to add nothing. > > I'm not observing this with either re23 nor HEAD. The initial search > correctly fails with noSuchObject, and then both slapds sit at 0% CPU. > Can you give further details? I'll look at reproducing it again. In this particular case, the master had a database rooted at "", with some data around "cn=zimbra" contained in it. A replica was configured as a syncrepl client, but with "dc=example,dc=com" as its base, by mistake. This resulted in the CPU usage shooting to 100% on the replica, and the logs showing it trying to add without success. --Quanah -- Quanah Gibson-Mount Principal Software Engineer Zimbra, Inc -------------------- Zimbra :: the leader in open source messaging and collaboration

1 0

(ITS#5076) Spell checking man pages
by ghenry＠OpenLDAP.org 06 Aug '07

06 Aug '07

Full_Name: Gavin Henry Version: HEAD adn RE_23 OS: URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (80.229.93.1) Submitted by: ghenry Dear all, Just creating a ticket for CHANGES, as I'm running: aspell --lang=en_US -c on all our manpages in HEAD and RE_23. Will query if I haev any concerns. Gavin.

1 0

Re: ITS#5075
by ando＠sys-net.it 06 Aug '07

06 Aug '07

ando(a)sys-net.it wrote: > fixed in HEAD; please test. also fixed in re23; please test. p. Ing. Pierangelo Masarati OpenLDAP Core Team SysNet s.r.l. via Dossi, 8 - 27100 Pavia - ITALIA http://www.sys-net.it --------------------------------------- Office: +39 02 23998309 Mobile: +39 333 4963172 Email: pierangelo.masarati(a)sys-net.it ---------------------------------------

1 0

ITS#5075
by ando＠sys-net.it 06 Aug '07

06 Aug '07

fixed in HEAD; please test. p. Ing. Pierangelo Masarati OpenLDAP Core Team SysNet s.r.l. via Dossi, 8 - 27100 Pavia - ITALIA http://www.sys-net.it --------------------------------------- Office: +39 02 23998309 Mobile: +39 333 4963172 Email: pierangelo.masarati(a)sys-net.it ---------------------------------------

1 0

(ITS#5075) openldap is not compilable with newest glibc and -D_FORTIFY_SOURCE=2
by jsafranek＠redhat.com 06 Aug '07

06 Aug '07

Full_Name: Jan Safranek Version: 2.3.37 OS: Linux (Fedora rawhide) URL: http://people.redhat.com/jsafrane/openldap-2.3.37-fortify-open.patch Submission from: (NULL) (62.40.79.66) Recently we have integrated glibc 2.6.90 into Fedora Linux distribution and OpenLDAP is not compilable anymore. We use -D_FORTIFY_SOURCE=2 to check for common errors on compile time and this switch causes that open() in fcntl.h is not a function name but a macro in the new glibc headers. Berkeley DB often uses 'something->open(...)' to open database, which is expanded by the compiler using the macro from fcntl.h -> compilation error. Compilation can be easily fixed by using additional braces around open, like '(something->open)(...)'. I do not like open() being macro, but POSIX allows it and glibc guys seems to be quite strict in this. The new glibc shall be released in fall and all major distributions will use it sooner or later, therefore I would suggest to adapt few OpenLDAP sources to it.

1 0

Re: (ITS#5074) slapo-pcache's proxyattrset does not recognize "1.1" to describe an empty attribute set
by ando＠sys-net.it 06 Aug '07

06 Aug '07

zep-openldap-software(a)ni.enate.org wrote: > For an application which specifies LDAP_NO_ATTRS to the attributes parameter of > ldap_search_st(), it seems not possible to cache its results using > slapo-pcache. > > It would be great to be able to define within "overlay pcache", something like: > > proxyattrset 0 (1.1) > > or, simply > > proxyattrset 0 > > Which would match queries which provide LDAP_NO_ATTRS. This would allow the > ability to cache responses for routines which are interested only in the > presence of a result set, but not in the contents of that set, without the > additional overhead of trasnferring the result. I believe there's something odd in pcache's current behavior. In fact, right now "proxyattrset 0" is already a valid directive, but it implies "proxyattrset 0 *", which means all attributes. Unfortunately, this seems to only work if no attribute is requested, while it fails if a "*" is explicitly requested. I've modified the propxycache code in HEAD so that a "1.1" can only explicitly appear in a list if it's the only string. An empty attribute set is no longer valid, to avoid confusion about the meaning of non-explicit attribute sets. A "*" or a "+" can explicitly appear in a proxyattrset statement, resulting in the expected behavior. Use both to indicate that all attributes are in the set. Please test. p. Ing. Pierangelo Masarati OpenLDAP Core Team SysNet s.r.l. via Dossi, 8 - 27100 Pavia - ITALIA http://www.sys-net.it --------------------------------------- Office: +39 02 23998309 Mobile: +39 333 4963172 Email: pierangelo.masarati(a)sys-net.it ---------------------------------------

1 0

Re: (ITS#5073) Syncrepl spinlock
by ando＠sys-net.it 06 Aug '07

06 Aug '07

quanah(a)OpenLDAP.org wrote: > Full_Name: Quanah Gibson-Mount > Version: 2.3.37 > OS: Linux > URL: > Submission from: (NULL) (71.202.148.128) > > > If you create a syncrepl master that serves the "" base, and then set up a > syncrepl consumer to pull down "dc=example,dc=com", which does *not* exist on > the master, the replica will sit at 100% CPU, endlessly trying to add nothing. I'm not observing this with either re23 nor HEAD. The initial search correctly fails with noSuchObject, and then both slapds sit at 0% CPU. Can you give further details? p. Ing. Pierangelo Masarati OpenLDAP Core Team SysNet s.r.l. via Dossi, 8 - 27100 Pavia - ITALIA http://www.sys-net.it --------------------------------------- Office: +39 02 23998309 Mobile: +39 333 4963172 Email: pierangelo.masarati(a)sys-net.it ---------------------------------------

1 0

(ITS#5074) slapo-pcache's proxyattrset does not recognize "1.1" to describe an empty attribute set
by zep-openldap-software＠ni.enate.org 05 Aug '07

05 Aug '07

Full_Name: Mike Malsman Version: 2.3.33 OS: FreeBSD 6 URL: Submission from: (NULL) (65.12.196.28) For an application which specifies LDAP_NO_ATTRS to the attributes parameter of ldap_search_st(), it seems not possible to cache its results using slapo-pcache. It would be great to be able to define within "overlay pcache", something like: proxyattrset 0 (1.1) or, simply proxyattrset 0 Which would match queries which provide LDAP_NO_ATTRS. This would allow the ability to cache responses for routines which are interested only in the presence of a result set, but not in the contents of that set, without the additional overhead of trasnferring the result.

1 0

(ITS#5073) Syncrepl spinlock
by quanah＠OpenLDAP.org 04 Aug '07

04 Aug '07

Full_Name: Quanah Gibson-Mount Version: 2.3.37 OS: Linux URL: Submission from: (NULL) (71.202.148.128) If you create a syncrepl master that serves the "" base, and then set up a syncrepl consumer to pull down "dc=example,dc=com", which does *not* exist on the master, the replica will sit at 100% CPU, endlessly trying to add nothing. --Quanah

1 0

(ITS#5072) Possibly incorrect certificateExactAssertion()
by ando＠sys-net.it 03 Aug '07

03 Aug '07

Full_Name: Pierangelo Masarati Version: HEAD/re24 OS: irrelevant URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (131.175.154.35) Submitted by: ando A certificate in certificateExactAssertion GSER form should be something like (wrapped for readability) { serialNumber 3, issuer rdnSequence:email=ca@example.com,cn=example ca,o=example,st=xx,c=us } according to RFC4523 & RFC3687, as far as I understand it. However, OpenLDAP HEAD uses the form { serialNumber 3, issuer "email=ca(a)example.com,cn=example ca,o=example,st=xx,c=us" } Note the quotes around the DN and the missing "rdnSequence:" prefix. p.

1 0

Re: (ITS#5069) SyncRepl on request
by bgmilne＠staff.telkomsa.net 03 Aug '07

03 Aug '07

On Wednesday 01 August 2007 23:53:22 hadmut(a)danisch.de wrote: > Full_Name: Hadmut Danisch > Version: 2.3.35 > OS: linux > URL: ftp://ftp.openldap.org/incoming/ > Submission from: (NULL) (85.180.64.215) > > > This is an enhancement request: > > When having a distributed LDAP structure with a master and several SyncRepl > clients, the clients can do the SyncRepl only on fixed refresh intervals > (e.g. type=refreshOnly, > interval=00:00:20:00) > > However, there are many situations where this is inappropriate, e.g. on > dial-on connections, roaming notebooks, and things like that. > > Therefore, slapd should have a client mode where the SyncRepl process is > performed only on request, but then immediately. There should be an > external trigger to pull, e.g. send a signal oder do a special LDAP > request. slapd should then start a SyncRepl. > > E.g. this could be put in scripts run at connect-time (pppd provides that > kind of scripting), or when notebook autoconfiguration detects (e.g. with > tools like guessnet) that it is connected to the home network to update > it's local slapd. While I'm not saying this feature should not be implemented, I note that there are other solutions for doing off-line authentication on (e.g.) laptops that don't expose the whole DIT (but only credentials that have already been used on the client).

1 0

Re: (ITS#5070) Issues in X.509 certificate parsing
by ando＠sys-net.it 03 Aug '07

03 Aug '07

Kurt Zeilenga wrote: > This and other RFC 4511 BER restrictions do not apply to > BER/DER-encoded attribute values, such as certificates. A cleaner and simpler solution is in HEAD for those serials that fit into a long long, when it's available. Otherwise, arbitrary precision support is required (OpenSSL's bignum, GNU's GMP or so). Please test. p. Ing. Pierangelo Masarati OpenLDAP Core Team SysNet s.r.l. via Dossi, 8 - 27100 Pavia - ITALIA http://www.sys-net.it --------------------------------------- Office: +39 02 23998309 Mobile: +39 333 4963172 Email: pierangelo.masarati(a)sys-net.it ---------------------------------------

1 0

Re: (ITS#5071) ;binary issue
by kurt＠OpenLDAP.org 03 Aug '07

03 Aug '07

On Aug 2, 2007, at 11:01 PM, ando(a)sys-net.it wrote: > Full_Name: Pierangelo Masarati > Version: HEAD/re23 > OS: irrelevant > URL: ftp://ftp.openldap.org/incoming/ > Submission from: (NULL) (81.72.89.40) > > > I've noticed an issue related to operating on certificates with/ > without ;binary, > as detailed in the table below > > slapadd filter requested attrs > > | ;binary | no ;binary | ;binary | > no ;binary > -------------+--------------+--------------+-------------- > +--------------- > ;binary | results | results | returned | returned > -------------+--------------+--------------+-------------- > +--------------- > no ;binary | no results | results | not returned | returned > > So it seems that if data is loaded with ;binary then search > operations work > regardless of having specified ;binary in search filters or in > requested > attributes, while if data is loaded without, then search operations > only work if > ;binary is omitted. RFC 4523 states that ;binary MUST be used when > transferring > certificates, so perhaps slapd should be either liberal enough to > allow any > combination, or strict enough to prevent those data types from > working without > ;binary. The bug is in allowing a certificate to be loaded without ;binary. -- Kurt

1 0

(ITS#5071) ;binary issue
by ando＠sys-net.it 03 Aug '07

03 Aug '07

Full_Name: Pierangelo Masarati Version: HEAD/re23 OS: irrelevant URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (81.72.89.40) I've noticed an issue related to operating on certificates with/without ;binary, as detailed in the table below slapadd filter requested attrs | ;binary | no ;binary | ;binary | no ;binary -------------+--------------+--------------+--------------+--------------- ;binary | results | results | returned | returned -------------+--------------+--------------+--------------+--------------- no ;binary | no results | results | not returned | returned So it seems that if data is loaded with ;binary then search operations work regardless of having specified ;binary in search filters or in requested attributes, while if data is loaded without, then search operations only work if ;binary is omitted. RFC 4523 states that ;binary MUST be used when transferring certificates, so perhaps slapd should be either liberal enough to allow any combination, or strict enough to prevent those data types from working without ;binary. p.

1 0

Re: (ITS#5070) Issues in X.509 certificate parsing
by kurt＠OpenLDAP.org 03 Aug '07

03 Aug '07

On Aug 2, 2007, at 10:48 PM, ando(a)sys-net.it wrote: > ando(a)sys-net.it wrote: > >> I've an issue with X.509 certificate parsing in HEAD/re24. The >> certificate, >> according to OpenSSL, has a SerialNumber c8:5b:9a:dd:ea:bf:f9:fa >> and HEAD fails >> to parse it because it is an integer with length equal to 9, which >> is larger >> than sizeof(ber_int_t), as tested in ber_getnint() at decode.c: >> 254. The DER >> encoded value is: 2 9 0 200 91 154 221 234 191 249 250. >> Seems to be time >> to get past the sizeof(ber_int_t) limitation... > > ... which would violate RFC 4511 where it states that INTEGER means > from > 0 up to 2^31-1... This and other RFC 4511 BER restrictions do not apply to BER/DER-encoded attribute values, such as certificates. > I have a simple solution for this problem, at the > cost of partially violating rfc 4523: if an integer is larger than > 2^31-1, it could be represented in the certificateExactMatch > normalization in hexadecimal form, much like OpenSSL does. This would > increase interoperability with OpenSSL and be at least self- > consistent, > since all serialNumbers that large would be consistently expanded that > way. Another solution, preserving the decimal representation, would > probably require some arbitrary precision support from external > libraries. If there's consensus, I'd post my simple patch. > > p. > > > > Ing. Pierangelo Masarati > OpenLDAP Core Team > > SysNet s.r.l. > via Dossi, 8 - 27100 Pavia - ITALIA > http://www.sys-net.it > --------------------------------------- > Office: +39 02 23998309 > Mobile: +39 333 4963172 > Email: pierangelo.masarati(a)sys-net.it > --------------------------------------- > > >

1 0

Re: (ITS#5070) Issues in X.509 certificate parsing
by ando＠sys-net.it 03 Aug '07

03 Aug '07

ando(a)sys-net.it wrote: > I've an issue with X.509 certificate parsing in HEAD/re24. The certificate, > according to OpenSSL, has a SerialNumber c8:5b:9a:dd:ea:bf:f9:fa and HEAD fails > to parse it because it is an integer with length equal to 9, which is larger > than sizeof(ber_int_t), as tested in ber_getnint() at decode.c:254. The DER > encoded value is: 2 9 0 200 91 154 221 234 191 249 250. Seems to be time > to get past the sizeof(ber_int_t) limitation... ... which would violate RFC 4511 where it states that INTEGER means from 0 up to 2^31-1... I have a simple solution for this problem, at the cost of partially violating rfc 4523: if an integer is larger than 2^31-1, it could be represented in the certificateExactMatch normalization in hexadecimal form, much like OpenSSL does. This would increase interoperability with OpenSSL and be at least self-consistent, since all serialNumbers that large would be consistently expanded that way. Another solution, preserving the decimal representation, would probably require some arbitrary precision support from external libraries. If there's consensus, I'd post my simple patch. p. Ing. Pierangelo Masarati OpenLDAP Core Team SysNet s.r.l. via Dossi, 8 - 27100 Pavia - ITALIA http://www.sys-net.it --------------------------------------- Office: +39 02 23998309 Mobile: +39 333 4963172 Email: pierangelo.masarati(a)sys-net.it ---------------------------------------

1 0

(ITS#5070) Issues in X.509 certificate parsing
by ando＠sys-net.it 02 Aug '07

02 Aug '07

Full_Name: Pierangelo Masarati Version: HEAD/re24 OS: irrelevant URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (81.72.89.40) Submitted by: ando I've an issue with X.509 certificate parsing in HEAD/re24. The certificate, according to OpenSSL, has a SerialNumber c8:5b:9a:dd:ea:bf:f9:fa and HEAD fails to parse it because it is an integer with length equal to 9, which is larger than sizeof(ber_int_t), as tested in ber_getnint() at decode.c:254. The DER encoded value is: 2 9 0 200 91 154 221 234 191 249 250. Seems to be time to get past the sizeof(ber_int_t) limitation... p.

1 0

Re: (ITS#5064) Issues with openldap 2.2 (Error 34 Invalid DN syntax )
by bgmilne＠staff.telkomsa.net 02 Aug '07

02 Aug '07

On Friday 27 July 2007 17:19:26 pbrinette(a)cc.in2p3.fr wrote: > > 1) both 2.0 and 2.2 are ancient. OpenLDAP 2.3 is mature, and 2.4 is > > about to exit beta stage. Unless the problem is related to a real > > software bug, and it persists either in HEAD/2.4 or in 2.3 code, this > > ITS will be closed. > > Currently, I've no mean to use an openldap 2.3 unless exists an RPM > update package for RHEL 4 (or CentOS). There is no update from RHEL or CentOS, but there are these (mine): http://staff.telkomsa.net/packages/rhel4/openldap/ Since you can install them in parallel, the upgrade path is quite easy ... (slapcat|slapadd2.3 after configuration). There is also: http://staff.telkomsa.net/packages/rhel3/openldap/ Regards, Buchan

1 0

(ITS#5069) SyncRepl on request
by hadmut＠danisch.de 01 Aug '07

01 Aug '07

Full_Name: Hadmut Danisch Version: 2.3.35 OS: linux URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (85.180.64.215) This is an enhancement request: When having a distributed LDAP structure with a master and several SyncRepl clients, the clients can do the SyncRepl only on fixed refresh intervals (e.g. type=refreshOnly, interval=00:00:20:00) However, there are many situations where this is inappropriate, e.g. on dial-on connections, roaming notebooks, and things like that. Therefore, slapd should have a client mode where the SyncRepl process is performed only on request, but then immediately. There should be an external trigger to pull, e.g. send a signal oder do a special LDAP request. slapd should then start a SyncRepl. E.g. this could be put in scripts run at connect-time (pppd provides that kind of scripting), or when notebook autoconfiguration detects (e.g. with tools like guessnet) that it is connected to the home network to update it's local slapd. regards Hadmut

1 0

Re: (ITS#5067) olcLogLevel value is incorrect
by ando＠sys-net.it 31 Jul '07

31 Jul '07

Quanah Gibson-Mount wrote: > --On Tuesday, July 31, 2007 4:35 AM +0000 ando(a)sys-net.it wrote: > >> quanah(a)zimbra.com wrote: >>> Full_Name: Quanah Gibson-Mount >>> Version: 2.3.37 >>> OS: NA >>> URL: ftp://ftp.openldap.org/incoming/ >>> Submission from: (NULL) (66.92.25.194) >>> >>> >>> When using cn=config with a slapd.conf driven slapd, the value for >>> olcLogLevel is not correct: >>> >>> ldapsearch -LLL -x -h build -b "cn=config" -s base -D "cn=config" -W >>> olcLogLevel >>> Enter LDAP Password: >>> dn: cn=config >>> olcLogLevel: None >>> >>> However: >>> >>> grep loglevel conf/slapd.conf >>> loglevel 32768 >>> >>> And the logging that is happening is actually for level 32768. >>> Modifying the loglevel works, and once that is done, the right loglevel >>> is shown. However, this makes it impossible to know what loglevel is >>> set via a remote query unless it has been changed. >> >>> From slapd.conf(5), loglevel: >> 32768 (0x8000 none) only messages that get logged >> whatever log level is set >> >> Seems to be correct. > > Yet if I modify it to be "256", then olcLogLevel is "256". If I modify > it to be "32768", then it is "32768". That's because in EMIT the loglevel goes through loglevel2bvarray(), which turns the level into an array of pretty values. You're supposed to modify the loglevel by adding multiple values, each with the descriptive name of the level you're using. The use of loglevel with OR'ed integers is stylistically deprecated. > So if the loglevel setting in > slapd.conf is "32768", then that is what it should match. In any case, > "None" has the unfortunate ring of sounding like an unset value. In LDAP, if the value were unset, the attribute would be missing, which is what you get if, for example, you set loglevel to 0. p. Ing. Pierangelo Masarati OpenLDAP Core Team SysNet s.r.l. via Dossi, 8 - 27100 Pavia - ITALIA http://www.sys-net.it --------------------------------------- Office: +39 02 23998309 Mobile: +39 333 4963172 Email: pierangelo.masarati(a)sys-net.it ---------------------------------------

1 0

Re: (ITS#5067) olcLogLevel value is incorrect
by quanah＠zimbra.com 31 Jul '07

31 Jul '07

--On Tuesday, July 31, 2007 4:35 AM +0000 ando(a)sys-net.it wrote: > quanah(a)zimbra.com wrote: >> Full_Name: Quanah Gibson-Mount >> Version: 2.3.37 >> OS: NA >> URL: ftp://ftp.openldap.org/incoming/ >> Submission from: (NULL) (66.92.25.194) >> >> >> When using cn=config with a slapd.conf driven slapd, the value for >> olcLogLevel is not correct: >> >> ldapsearch -LLL -x -h build -b "cn=config" -s base -D "cn=config" -W >> olcLogLevel >> Enter LDAP Password: >> dn: cn=config >> olcLogLevel: None >> >> However: >> >> grep loglevel conf/slapd.conf >> loglevel 32768 >> >> And the logging that is happening is actually for level 32768. >> Modifying the loglevel works, and once that is done, the right loglevel >> is shown. However, this makes it impossible to know what loglevel is >> set via a remote query unless it has been changed. > >> From slapd.conf(5), loglevel: > 32768 (0x8000 none) only messages that get logged > whatever log level is set > > Seems to be correct. Yet if I modify it to be "256", then olcLogLevel is "256". If I modify it to be "32768", then it is "32768". So if the loglevel setting in slapd.conf is "32768", then that is what it should match. In any case, "None" has the unfortunate ring of sounding like an unset value. --Quanah -- Quanah Gibson-Mount Principal Software Engineer Zimbra, Inc -------------------- Zimbra :: the leader in open source messaging and collaboration

1 0

Re: (ITS#5067) olcLogLevel value is incorrect
by ando＠sys-net.it 31 Jul '07

31 Jul '07

quanah(a)zimbra.com wrote: > Full_Name: Quanah Gibson-Mount > Version: 2.3.37 > OS: NA > URL: ftp://ftp.openldap.org/incoming/ > Submission from: (NULL) (66.92.25.194) > > > When using cn=config with a slapd.conf driven slapd, the value for olcLogLevel > is not correct: > > ldapsearch -LLL -x -h build -b "cn=config" -s base -D "cn=config" -W > olcLogLevel > Enter LDAP Password: > dn: cn=config > olcLogLevel: None > > However: > > grep loglevel conf/slapd.conf > loglevel 32768 > > And the logging that is happening is actually for level 32768. Modifying the > loglevel works, and once that is done, the right loglevel is shown. However, > this makes it impossible to know what loglevel is set via a remote query unless > it has been changed. >From slapd.conf(5), loglevel: 32768 (0x8000 none) only messages that get logged whatever log level is set Seems to be correct. p. Ing. Pierangelo Masarati OpenLDAP Core Team SysNet s.r.l. via Dossi, 8 - 27100 Pavia - ITALIA http://www.sys-net.it --------------------------------------- Office: +39 02 23998309 Mobile: +39 333 4963172 Email: pierangelo.masarati(a)sys-net.it ---------------------------------------

1 0

Re: (ITS#5068) buglet in charray.c
by quanah＠zimbra.com 30 Jul '07

30 Jul '07

--On July 30, 2007 9:28:06 PM +0000 mb(a)g10code.com wrote: > Full_Name: Marcus Brinkmann > Version: 2.1.30 > OS: GNU/Linux > URL: ftp://ftp.openldap.org/incoming/ > Submission from: (NULL) (87.123.156.61) OpenLDAP 2.1 is no longer a supported release. The current release branch is OpenLDAP 2.3. Please do not file ITSes on dead releases. Thanks. --Quanah -- Quanah Gibson-Mount Principal Software Engineer Zimbra, Inc -------------------- Zimbra :: the leader in open source messaging and collaboration

1 0

(ITS#5068) buglet in charray.c
by mb＠g10code.com 30 Jul '07

30 Jul '07

Full_Name: Marcus Brinkmann Version: 2.1.30 OS: GNU/Linux URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (87.123.156.61) This fixes a warning and seems locally correct. I did not check the expected semantics of this code. Thanks, Marcus. diff -ru openldap2-2.1.30-orig/libraries/libldap/charray.c openldap2-2.1.30/libraries/libldap/charray.c --- openldap2-2.1.30-orig/libraries/libldap/charray.c 2003-03-03 18:10:04.000000000 +0100 +++ openldap2-2.1.30/libraries/libldap/charray.c 2007-07-30 23:24:30.000000000 +0200 @@ -183,7 +183,7 @@ i = 1; for ( s = str; *s; s++ ) { - if ( ldap_utf8_strchr( brkstr, s ) != NULL ) { + if ( ldap_utf8_strchr( brkstr, *s ) != NULL ) { i++; } }

1 0

(ITS#5067) olcLogLevel value is incorrect
by quanah＠zimbra.com 30 Jul '07

30 Jul '07

Full_Name: Quanah Gibson-Mount Version: 2.3.37 OS: NA URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (66.92.25.194) When using cn=config with a slapd.conf driven slapd, the value for olcLogLevel is not correct: ldapsearch -LLL -x -h build -b "cn=config" -s base -D "cn=config" -W olcLogLevel Enter LDAP Password: dn: cn=config olcLogLevel: None However: grep loglevel conf/slapd.conf loglevel 32768 And the logging that is happening is actually for level 32768. Modifying the loglevel works, and once that is done, the right loglevel is shown. However, this makes it impossible to know what loglevel is set via a remote query unless it has been changed.

1 0

Re: Contribution: Active Directory Password Cache (ITS#5042)
by s.hetze＠linux-ag.de 30 Jul '07

30 Jul '07

Hi Gavin, I just uploaded a patch for my contribution as Sebastian-Hetze-070630.patch (sorry for the wrong date) The adpwc as contributed has a dependency to samba3.schema to be present, which is fixed with this patch. The patch also makes adpwc fold realm names to upper case since AD stores them mixed case and gives tickets upper case. I introduced a new config option adpw-cache-keep-realm-case to keep the old behaviour if needed. It looks like I cannot add this patch to ticket #5042, so I ask you to attach it if possible. Thanx alot, Sebastian On Thu, Jul 19, 2007 at 09:48:58AM +0000, Gavin Henry wrote: > Hi, > > This looks like it is in the correct format for our contrib section. Just > testing is needed. As I don't have access to an Active Directory server I can't > test. > > Anyone else? > > Gavin. -- Sebastian Hetze Mitglied des Vorstands Linux Information Systems AG Ehrenbergstr. 19, D-10245 Berlin Fon: +49 30 726238-0, Fax: +49 30 726238-99 s.hetze(a)linux-ag.com, http://www.linux-ag.com ---------------------------------------------------------- Sitz der Gesellschaft: Stefan-George-Ring 8, 81929 München Amtsgericht München: HRB 128 019 Vorstand: Rudolf Strobl, Sebastian Hetze Aufsichtsrat: Michael Tarabochia (Vorsitzender)

1 0

(ITS#5066) ldap error :server down
by jalali_azam＠yahoo.com 30 Jul '07

30 Jul '07

Full_Name: Azam Jalali Version: 2.2.29 OS: windows URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (213.207.237.38) I installed openldap 2.2.9 and set sldap.conf as following: /////////////////////////////////////////////////////////////////////////// ucdata-path ./ucdata include ./schema/core.schema include ./schema/cosine.schema include ./schema/inetorgperson.schema include ./schema/nis.schema include ./schema/dyngroup.schema # Define global ACLs to disable default read access. # Do not enable referrals until AFTER you have a working directory # service AND an understanding of referrals. #referral ldap:/root.openldap.org pidfile ./run/slapd.pid argsfile ./run/slapd.args # Load dynamic backend modules: # modulepath ./libexec/openldap # moduleload back_bdb.la # moduleload back_ldap.la # moduleload back_ldbm.la # moduleload back_passwd.la # moduleload back_shell.la # Sample security restrictions # Require integrity protection (prevent hijacking) # Require 112-bit (3DES or better) encryption for updates # Require 63-bit encryption for simple bind # security ssf=1 update_ssf=112 simple_bind=64 # Sample access control policy: # Root DSE: allow anyone to read it # Subschema (sub)entry DSE: allow anyone to read it # Other DSEs: # Allow self write access # Allow authenticated users read access # Allow anonymous users to authenticate # Directives needed to implement policy: # access to dn.base="" by * read # access to dn.base="cn=Subschema" by * read # access to * # by self write # by users read # by anonymous auth # # if no access controls are present, the default policy # allows anyone and everyone to read anything but restricts # updates to rootdn. (e.g., "access to * by * read") # # rootdn can always read and write EVERYTHING! ####################################################################### # BDB database definitions ####################################################################### database bdb suffix "dc=my-domain,dc=com" rootdn "cn=Manager,dc=my-domain,dc=com" # Cleartext passwords, especially for the rootdn, should # be avoid. See slappasswd(8) and slapd.conf(5) for details. # Use of strong authentication encouraged. rootpw secret # The database directory MUST exist prior to running slapd AND # should only be accessible by the slapd and slap tools. # Mode 700 recommended. directory ./data # Indices to maintain index objectClass eq access to attr=userpassword by anonymous auth by self write by dn="cn=Manager,dc=my-domain,dc=com" write by * none access to * by dn="cn=Manager,dc=my-domain,dc=com" write by users write by self write by * read by * write /////////////////////////////////////////////////////////////////////////// After running some query on this openldap i got ldap error:server down. This event occurs every time i reinstalled it and ran some query on it? How i fix this error? Thanks in advance Azam Jalali

1 0

Slapd doesn't start after update
by ツ Leandro Sales 28 Jul '07

28 Jul '07

Hello folks... I update the openldap from version 2.2.28-r7 to 2.3.35-r1 using emerge. After update the slapd deamon didn't start. I enabled the log and realized that the problem was the incompatible version of the database. I then downgrade to the 2.2.28 version and when I started slapd I got the message: "/usr/lib64/openldap/slapd: error while loading shared libraries: liblber-2.3.so.0: cannot open shared object file: No such file or directory". I then reinstall and this problem doesn't happen anymore, but slapd still doesn't start and print the following messages in the log file: Jul 27 17:55:11 embedded slapd[2957]: bdb_db_init: Initializing BDB database Jul 27 17:55:11 embedded slapd[2958]: bdb(o=Embedded,c=BR): Program version 4.5 doesn't match environment version 0.22 Jul 27 17:55:11 embedded slapd[2958]: bdb_db_open: dbenv_open failed: DB_VERSION_MISMATCH: Database environment version mismatch (-30972) Jul 27 17:55:11 embedded slapd[2958]: backend_startup: bi_db_open failed! (-30972) Jul 27 17:55:11 embedded slapd[2958]: bdb(o=Embedded,c=BR): DB_ENV->lock_id_free interface requires an environment configured for the locking subsystem Jul 27 17:55:11 embedded slapd[2958]: bdb(o=Embedded,c=BR): txn_checkpoint interface requires an environment configured for the transaction subsystem Jul 27 17:55:11 embedded slapd[2958]: bdb_db_destroy: txn_checkpoint failed: Invalid argument (22) Please, help me on this. []s Leandro.

2 1

Re: (ITS#5064) Issues with openldap 2.2 (Error 34 Invalid DN syntax )
by ando＠sys-net.it 27 Jul '07

27 Jul '07

ando(a)sys-net.it wrote: > What would make things totally different is the persistence of a problem > in 2.3 and 2.4. But the very existence of a problem has to be proven > yet. If you look at my analysis with dntest, you'll see that your DN I confirm that using the schema extracted from <ldap://cclcgtopbdii01.in2p3.fr:2170/>, 2.3/2.4 slapdn can successfully handle the offending DN: $ slapdn \ 'GlueVOViewLocalID=/VO=swetest/GROUP=/swetest/ROLE=swadmin,GlueCEUniqueID=grid001.fc.up.pt:2119/jobmanager-lcgsge-swetest,mds-vo-name=UPorto,mds-vo-name=local,o=grid' DN: <GlueVOViewLocalID=/VO=swetest/GROUP=/swetest/ROLE=swadmin,GlueCEUniqueID=grid001.fc.up.pt:2119/jobmanager-lcgsge-swetest,mds-vo-name=UPorto,mds-vo-name=local,o=grid> check succeeded normalized: <GlueVOViewLocalID=/vo\3Dswetest/group\3D/swetest/role\3Dswadmin,GlueCEUniqueID=grid001.fc.up.pt:2119/jobmanager-lcgsge-swetest,Mds-Vo-name=uporto,Mds-Vo-name=local,o=grid> pretty: <GlueVOViewLocalID=/VO\3Dswetest/GROUP\3D/swetest/ROLE\3Dswadmin,GlueCEUniqueID=grid001.fc.up.pt:2119/jobmanager-lcgsge-swetest,Mds-Vo-name=UPorto,Mds-Vo-name=local,o=grid> I'd consider this ITS closed. p. Ing. Pierangelo Masarati OpenLDAP Core Team SysNet s.r.l. via Dossi, 8 - 27100 Pavia - ITALIA http://www.sys-net.it --------------------------------------- Office: +39 02 23998309 Mobile: +39 333 4963172 Email: pierangelo.masarati(a)sys-net.it ---------------------------------------

1 0

(ITS#5065) out of order ctxcsn from old entryCSN
by donn＠u.washington.edu 27 Jul '07

27 Jul '07

Full_Name: Donn Cave Version: 2.4.4 OS: RH Linux URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (128.95.135.150) Old entryCSN values imported into the data from another server, can crash replicas. In loop at top of syncrepl_updateCookie, replica encounters a syncCookie whose value is less than its matching si_cookieState->cs_val. This breaks out of the inner loop, and the outer loop, without copying anything into `first', so slap_queue_csn crashes on the null csn. Both are element 0 of their respective arrays. I assume it is no surprise that syncCookie takes its value from an entryCSN attribute. To duplicate, add an entry with an explicit entryCSN, with value less than the current contextCSN. In my case, the entryCSN is of the format without the `decimal fraction' field, but I doubt that matters. I don't want to say OpenLDAP needs to support this, but maybe it would be better to catch the problem in the master, than crash the replicas.

1 0

Re: (ITS#5058) LDAP/Egroupware addressbook issue
by ando＠sys-net.it 27 Jul '07

27 Jul '07

chandra(a)sentienthealth.com wrote: > Jul 23 13:39:35 shs slapd[20739]: SRCH "o=sen,dc=domainname,dc=com" 2 0 > Jul 23 13:39:35 shs slapd[20739]: 300 0 0 > Jul 23 13:39:35 shs slapd[20739]: begin get_filter > Jul 23 13:39:35 shs slapd[20739]: OR > Jul 23 13:39:35 shs slapd[20739]: begin get_filter_list > Jul 23 13:39:35 shs slapd[20739]: begin get_filter > Jul 23 13:39:35 shs slapd[20739]: EQUALITY > > Its stop here and hang and we have to restart ldap to make it work. Seems to be related to filter parsing, but we don't get any logging about the filter, and there's too little information to detect what's the issue. You might add "packets" to the log level to see what actually gets sent along with the request (beware that log level will be very verbose, then), and post the output concerning the sole initiation of the search request up to the hang. p. Ing. Pierangelo Masarati OpenLDAP Core Team SysNet s.r.l. via Dossi, 8 - 27100 Pavia - ITALIA http://www.sys-net.it --------------------------------------- Office: +39 02 23998309 Mobile: +39 333 4963172 Email: pierangelo.masarati(a)sys-net.it ---------------------------------------

1 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

openldap-bugs