openldap-bugs

openldap-bugs@openldap.org

1 participants
20963 discussions

Re: (ITS#7501) added TCP keepalive support to back_ldap
by hyc＠symas.com 24 Jan '13

24 Jan '13

tedcheng(a)symas.com wrote: > Full_Name: Ted C. Cheng > Version: master > OS: Linux/Solaris > URL: https://dl.dropbox.com/u/94235048/back_ldap_tcp_keepalive.patch > Submission from: (NULL) (76.174.253.197) > > > > Please find in the URL a patch that adds TCP keepalive support to back_ldap. > > Please review and apply the patch. Note - constructs like "#if 0" are only used for tentative/experimental changes. For patches intended to be released to the public, just delete the blocked out lines. -- -- Howard Chu CTO, Symas Corp. http://www.symas.com Director, Highland Sun http://highlandsun.com/hyc/ Chief Architect, OpenLDAP http://www.openldap.org/project/

1 0

Re: (ITS#7496) Segemtation fault in mdb_entry_decode
by meike.stone＠googlemail.com 24 Jan '13

24 Jan '13

>> Thread 1 (Thread 0x7f738b21c700 (LWP 19394)): > > >> #1 0x0000000000501d30 in mdb_search (op=0xc3a020, rs=0x7f738b21ba30) at >> search.c:720 >> scopeok = 1 >> edata = {mv_size = 0, mv_data = 0x7f74bbb99728} > > > This indicates that the entry being debugged is actually zero bytes, i.e. > it's not a valid entry at all. Nodes like this get stored in the database > during slapadd when a child entry gets added before its parent; a zero-byte > stub is stored as a placeholder for the missing parent. > When you ran slapadd > you should have seen warning messages about missing entries, telling you > that your LDIF is incomplete. Yes you are right, I repeated the import via slapcat to test and got this error message: ~ # slapadd -w -q -f /etc/openldap/slapd.conf -l /backup.ldif 50f98421 mdb_monitor_db_open: monitoring disabled; configure monitor database to enable -#################### 100.00% eta none elapsed 09m18s spd 4.6 M/s Closing DB...Error, entries missing! entry 1156449: cn=1356155776-83002,ou=... ,... ,ou=root (I shortened the entry DN in output with "...") I recognized this message before, but thought the entry was not imported ... > > We can prevent the SEGV but your database is still invalid because your LDIF > is invalid. Yes, will ask in the mailing list for additional information not directly releated to this SEGV. Thanks Kindly regards Maike

1 0

Re: (ITS#7499)
by hyc＠symas.com 24 Jan '13

24 Jan '13

Benin Technologies wrote: > Yes the fix worked (I downloaded the latest openldap.tar.gz on your > gitweb and installed it). Now slapd starts after having converted to > cn=config > > But after the conversion my ldapsearch returns an 80 error (with > slapd.conf it worked, the data from PostgreSQL where returned) > Thus my question : are there other steps to be taken after the > conversion (all I did was : slaptest -f slapd.conf -F slapd.d) Ah. In that case the fix must still be wrong. (Sorry, I'm patching this blind as I don't have any current SQL installation to test with.) > I don't think this has something to do with that 7499 bug, so I'll post > the question on the technical mailing list (but if nobody bumped into > that 7499 bug before, it logically means that nobody is using back-sql > with cn=config yet) Agreed, I think it's unlikely that anyone else has used this yet. > > ldapsearch -x -h localhost -b "dc=example,dc=com" "(objectClass=*)" > # extended LDIF > # > # LDAPv3 > # base <dc=example,dc=com> with scope subtree > # filter: (objectClass=*) > # requesting: ALL > # > > # search result > search: 2 > result: 80 Other (e.g., implementation specific) error > > # numResponses: 1 > > > Le 24/01/2013 04:46, Howard Chu a écrit : >> Benin Technologies wrote: >>>>>>> Yes, it's a bug. The conversion should have used double-quotes on >>> these >>>>>>> parameters. Will be fixed shortly. >>> >>> >>> ok thanks, I added manually the double-quotes on olcSqlInsEntryStmt in >>> the file olcDatabase={1}sql.ldif, like this : >>> >>> olcSqlInsEntryStmt: "insert into ldap_entries >>> (id,dn,oc_map_id,parent,keyval) values ((select max(id)+1 from >>> ldap_entries),?,?,?,?)" >>> >>> >>> Now slapd starts, but ldapsearch returns "80 Other (e.g., implementation >>> specific error)". With the old "slapd.conf", ldapsearch works fine. Is >>> there anything else to do when converting slapd.conf to cn=config on a >>> back-sql implementation ? >> >> Yes, actually the quotes are optional, but you must get the fix from git. >> Commit 56a0d9004f0fba943028041ea5af62338b6dfccd >>> >>> >>> >>> >>> Le 24/01/2013 02:44, hyc(a)symas.com a écrit : >>>> benintechnologies(a)yahoo.fr wrote: >>>>> Hi, >>>>> >>>>> thank you for your reply >>>>> >>>>> I simply took the slapd.conf file adapted to PostgreSQL in the source >>>>> (/openldap-2.4.33/servers/slapd/back-sql/rdbms_depend/pgsql) >>>>> >>>>> In that file, we have : >>>>> olcSqlInsEntryStmt: insert into ldap_entries >>>>> (id,dn,oc_map_id,parent,keyval) values ((select max(id)+1 from >>>>> ldap_entries),?,?,?,?) >>>>> >>>>> it works with static configuration (slapd.conf) : I successfully >>>>> managed >>>>> to insert some data into the postgresql tables >>>>> >>>>> But after having converted it to cn=config (slaptest -f slapd.conf -F >>>>> slapd.d) slapd doesn't start anymore : >>>>> 0ff3f0a<<< dnPrettyNormal:<cn=root,dc=example,dc=com>, >>>>> <cn=root,dc=example,dc=com> >>>>> 50ff3f0a olcSqlInsEntryStmt: value #0:<olcSqlInsEntryStmt> extra >>>>> cruft >>>>> after<SQL expression>. >>>>> 50ff3f0a config error processing olcDatabase={1}sql,cn=config: >>>>> <olcSqlInsEntryStmt> *extra cruft after<SQL expression>* >>>>> 50ff3f0a send_ldap_result: conn=-1 op=0 p=0 >>>>> 50ff3f0a send_ldap_result: err=19 matched="" text="" >>>>> 50ff3f0a slapd destroy: freeing system resources. >>>>> 50ff3f0a slapd stopped. >>>>> 50ff3f0a connections_destroy: nothing to destroy. >>>>> >>>>> I believe it's a bug, no ? >>> >>> >> >> > > -- -- Howard Chu CTO, Symas Corp. http://www.symas.com Director, Highland Sun http://highlandsun.com/hyc/ Chief Architect, OpenLDAP http://www.openldap.org/project/

1 0

Re: (ITS#7499)
by benintechnologies＠yahoo.fr 24 Jan '13

24 Jan '13

Yes the fix worked (I downloaded the latest openldap.tar.gz on your gitweb and installed it). Now slapd starts after having converted to cn=config But after the conversion my ldapsearch returns an 80 error (with slapd.conf it worked, the data from PostgreSQL where returned) Thus my question : are there other steps to be taken after the conversion (all I did was : slaptest -f slapd.conf -F slapd.d) I don't think this has something to do with that 7499 bug, so I'll post the question on the technical mailing list (but if nobody bumped into that 7499 bug before, it logically means that nobody is using back-sql with cn=config yet) ldapsearch -x -h localhost -b "dc=example,dc=com" "(objectClass=*)" # extended LDIF # # LDAPv3 # base <dc=example,dc=com> with scope subtree # filter: (objectClass=*) # requesting: ALL # # search result search: 2 result: 80 Other (e.g., implementation specific) error # numResponses: 1 Le 24/01/2013 04:46, Howard Chu a écrit : > Benin Technologies wrote: >> >>>>Yes, it's a bug. The conversion should have used double-quotes on >> these >> >>>>parameters. Will be fixed shortly. >> >> >> ok thanks, I added manually the double-quotes on olcSqlInsEntryStmt in >> the file olcDatabase={1}sql.ldif, like this : >> >> olcSqlInsEntryStmt: "insert into ldap_entries >> (id,dn,oc_map_id,parent,keyval) values ((select max(id)+1 from >> ldap_entries),?,?,?,?)" >> >> >> Now slapd starts, but ldapsearch returns "80 Other (e.g., implementation >> specific error)". With the old "slapd.conf", ldapsearch works fine. Is >> there anything else to do when converting slapd.conf to cn=config on a >> back-sql implementation ? > > Yes, actually the quotes are optional, but you must get the fix from git. > Commit 56a0d9004f0fba943028041ea5af62338b6dfccd >> >> >> >> >> Le 24/01/2013 02:44, hyc(a)symas.com a écrit : >>> benintechnologies(a)yahoo.fr wrote: >>>> Hi, >>>> >>>> thank you for your reply >>>> >>>> I simply took the slapd.conf file adapted to PostgreSQL in the source >>>> (/openldap-2.4.33/servers/slapd/back-sql/rdbms_depend/pgsql) >>>> >>>> In that file, we have : >>>> olcSqlInsEntryStmt: insert into ldap_entries >>>> (id,dn,oc_map_id,parent,keyval) values ((select max(id)+1 from >>>> ldap_entries),?,?,?,?) >>>> >>>> it works with static configuration (slapd.conf) : I successfully >>>> managed >>>> to insert some data into the postgresql tables >>>> >>>> But after having converted it to cn=config (slaptest -f slapd.conf -F >>>> slapd.d) slapd doesn't start anymore : >>>> 0ff3f0a<<< dnPrettyNormal:<cn=root,dc=example,dc=com>, >>>> <cn=root,dc=example,dc=com> >>>> 50ff3f0a olcSqlInsEntryStmt: value #0:<olcSqlInsEntryStmt> extra >>>> cruft >>>> after<SQL expression>. >>>> 50ff3f0a config error processing olcDatabase={1}sql,cn=config: >>>> <olcSqlInsEntryStmt> *extra cruft after<SQL expression>* >>>> 50ff3f0a send_ldap_result: conn=-1 op=0 p=0 >>>> 50ff3f0a send_ldap_result: err=19 matched="" text="" >>>> 50ff3f0a slapd destroy: freeing system resources. >>>> 50ff3f0a slapd stopped. >>>> 50ff3f0a connections_destroy: nothing to destroy. >>>> >>>> I believe it's a bug, no ? >> >> > >

1 0

Re: (ITS#7498) Openldap syncrepl issue
by arunkumar_1123＠yahoo.com 23 Jan '13

23 Jan '13

> MMR has supported delta-syncrepl since 2.4.27. You should use it. I did consider delta-syncrepl, but given the high write load expected, I was not sure if it was the right decision. I am expecting an average load of 50-100 writes per second, and with 1 backup provider, and 10 consumers, it might get heavy on the provider which is serving the writes, given that OpenLDAP would be maintaining another DB for the access log. But with this syncrepl issue, it looks like I need to change the replication mode to refreshAndPersist anyway. As such it looks like delta syncrepl is also refreshAndPersist too. Is there any recommendation between simple refreshAndPersist and delta-syncrepl with refreshAndPersist for high write loads? Thanks PS: I see that delta syncrepl is compatible with MMR which I presume to be MultiMaster. I hope it works with Mirror Mode too. I did not find any documents supporting this.

1 0

(ITS#7501) added TCP keepalive support to back_ldap
by tedcheng＠symas.com 23 Jan '13

23 Jan '13

Full_Name: Ted C. Cheng Version: master OS: Linux/Solaris URL: https://dl.dropbox.com/u/94235048/back_ldap_tcp_keepalive.patch Submission from: (NULL) (76.174.253.197) Please find in the URL a patch that adds TCP keepalive support to back_ldap. Please review and apply the patch. Thanks, Ted C. Cheng Symas Corporation

1 0

Re: (ITS#7499)
by hyc＠symas.com 23 Jan '13

23 Jan '13

Benin Technologies wrote: > >>>>Yes, it's a bug. The conversion should have used double-quotes on these > >>>>parameters. Will be fixed shortly. > > > ok thanks, I added manually the double-quotes on olcSqlInsEntryStmt in > the file olcDatabase={1}sql.ldif, like this : > > olcSqlInsEntryStmt: "insert into ldap_entries (id,dn,oc_map_id,parent,keyval) values ((select max(id)+1 from ldap_entries),?,?,?,?)" > > > Now slapd starts, but ldapsearch returns "80 Other (e.g., implementation > specific error)". With the old "slapd.conf", ldapsearch works fine. Is > there anything else to do when converting slapd.conf to cn=config on a > back-sql implementation ? Yes, actually the quotes are optional, but you must get the fix from git. Commit 56a0d9004f0fba943028041ea5af62338b6dfccd > > > > > Le 24/01/2013 02:44, hyc(a)symas.com a écrit : >> benintechnologies(a)yahoo.fr wrote: >>> Hi, >>> >>> thank you for your reply >>> >>> I simply took the slapd.conf file adapted to PostgreSQL in the source >>> (/openldap-2.4.33/servers/slapd/back-sql/rdbms_depend/pgsql) >>> >>> In that file, we have : >>> olcSqlInsEntryStmt: insert into ldap_entries >>> (id,dn,oc_map_id,parent,keyval) values ((select max(id)+1 from >>> ldap_entries),?,?,?,?) >>> >>> it works with static configuration (slapd.conf) : I successfully managed >>> to insert some data into the postgresql tables >>> >>> But after having converted it to cn=config (slaptest -f slapd.conf -F >>> slapd.d) slapd doesn't start anymore : >>> 0ff3f0a<<< dnPrettyNormal:<cn=root,dc=example,dc=com>, >>> <cn=root,dc=example,dc=com> >>> 50ff3f0a olcSqlInsEntryStmt: value #0:<olcSqlInsEntryStmt> extra cruft >>> after<SQL expression>. >>> 50ff3f0a config error processing olcDatabase={1}sql,cn=config: >>> <olcSqlInsEntryStmt> *extra cruft after<SQL expression>* >>> 50ff3f0a send_ldap_result: conn=-1 op=0 p=0 >>> 50ff3f0a send_ldap_result: err=19 matched="" text="" >>> 50ff3f0a slapd destroy: freeing system resources. >>> 50ff3f0a slapd stopped. >>> 50ff3f0a connections_destroy: nothing to destroy. >>> >>> I believe it's a bug, no ? > > -- -- Howard Chu CTO, Symas Corp. http://www.symas.com Director, Highland Sun http://highlandsun.com/hyc/ Chief Architect, OpenLDAP http://www.openldap.org/project/

1 0

Re: (ITS#7499)
by benintechnologies＠yahoo.fr 23 Jan '13

23 Jan '13

>>>>Yes, it's a bug. The conversion should have used double-quotes on these >>>>parameters. Will be fixed shortly. ok thanks, I added manually the double-quotes on olcSqlInsEntryStmt in the file olcDatabase={1}sql.ldif, like this : olcSqlInsEntryStmt: "insert into ldap_entries (id,dn,oc_map_id,parent,keyval) values ((select max(id)+1 from ldap_entries),?,?,?,?)" Now slapd starts, but ldapsearch returns "80 Other (e.g., implementation specific error)". With the old "slapd.conf", ldapsearch works fine. Is there anything else to do when converting slapd.conf to cn=config on a back-sql implementation ? Le 24/01/2013 02:44, hyc(a)symas.com a écrit : > benintechnologies(a)yahoo.fr wrote: >> Hi, >> >> thank you for your reply >> >> I simply took the slapd.conf file adapted to PostgreSQL in the source >> (/openldap-2.4.33/servers/slapd/back-sql/rdbms_depend/pgsql) >> >> In that file, we have : >> olcSqlInsEntryStmt: insert into ldap_entries >> (id,dn,oc_map_id,parent,keyval) values ((select max(id)+1 from >> ldap_entries),?,?,?,?) >> >> it works with static configuration (slapd.conf) : I successfully managed >> to insert some data into the postgresql tables >> >> But after having converted it to cn=config (slaptest -f slapd.conf -F >> slapd.d) slapd doesn't start anymore : >> 0ff3f0a<<< dnPrettyNormal:<cn=root,dc=example,dc=com>, >> <cn=root,dc=example,dc=com> >> 50ff3f0a olcSqlInsEntryStmt: value #0:<olcSqlInsEntryStmt> extra cruft >> after<SQL expression>. >> 50ff3f0a config error processing olcDatabase={1}sql,cn=config: >> <olcSqlInsEntryStmt> *extra cruft after<SQL expression>* >> 50ff3f0a send_ldap_result: conn=-1 op=0 p=0 >> 50ff3f0a send_ldap_result: err=19 matched="" text="" >> 50ff3f0a slapd destroy: freeing system resources. >> 50ff3f0a slapd stopped. >> 50ff3f0a connections_destroy: nothing to destroy. >> >> I believe it's a bug, no ?

1 0

(ITS#7500) libldap starttls crashes if invalid GnuTLS cipher suite string
by jouko.orava＠iki.fi 23 Jan '13

23 Jan '13

Full_Name: Jouko Orava Version: 2.4.28, 2.4.33 OS: Debian/Ubuntu URL: Submission from: (NULL) (82.181.197.37) If the cipher suite string is unacceptable to GnuTLS, libldap_r-2.4 crashes in ldap_start_tls_s() due to a double free. See https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1103353 for my original bug submission, including a suggested patch, https://launchpadlibrarian.net/129174364/openldap-ciphersuite.patch and a simple example ldapsearch-like program that can be used to test the issue. This bug is not critical, since using a valid GnuTLS cipher suite does work, for example "NORMAL" or "SECURE256". However, trying to use anything more specific is exceedingly difficult -- basically trial and error, due to applications crashing in libldap with an invalid one. The two other TLS implementations in OpenLDAP are not affected by this bug. The double free occurs in openldap/libraries/libldap/tls2.c:ldap_int_tls_init_ctx(), in the ldap_pvt_tls_ctx_free(lo->ldo_tls_ctx); call in the error_exit: path. Because the cipher suite string was unacceptable to GnuTLS, the context is either released by GnuTLS or never properly initialized. The error_exit: path tries to release that context, and causes the C library to abort the program as it detects a double free. Simply commenting the ldap_pvt_tls_ctx_free(lo->ldo_tls_ctx); call in the error_exit: path in openldap/libraries/libldap/tls2.c:ldap_int_tls_init_ctx() masks the issue, but is obviously incorrect (as it affects the two other TLS implementations too). My suggested patch is to use the configured cipher suite string when creating the new TLS context, instead of "NORMAL" as is currently done, in openldap/libraries/libldap/tls_g.c:tlsg_ctx_new(). If there is a problem with the cipher suite priority string, the initial context is torn down, and caught earlier in openldap/libraries/libldap/tls2.c, avoiding the crash. (However, the cipher suite string will be parsed twice.) There seem to be numerous unhandled bug reports in various distributions and applications, including http://www.openldap.org/its/index.cgi/Incoming?id=6939#themesg which are quite tricky to investigate, as the actual bug occurs deep in libldap. Only user checks with a patched libldap will prove whether these are actually caused by this bug or not. It is very easy to assume it is an application bug, due to the symptoms and pretty limited circumstances. Recap: libldap + GnuTLS, application using ldap_start_tls, and any cipher suite string not acceptable to GnuTLS will cause libldap to crash due to a double free.

1 0

Re: (ITS#7499)
by hyc＠symas.com 23 Jan '13

23 Jan '13

benintechnologies(a)yahoo.fr wrote: > Hi, > > thank you for your reply > > I simply took the slapd.conf file adapted to PostgreSQL in the source > (/openldap-2.4.33/servers/slapd/back-sql/rdbms_depend/pgsql) > > In that file, we have : > olcSqlInsEntryStmt: insert into ldap_entries > (id,dn,oc_map_id,parent,keyval) values ((select max(id)+1 from > ldap_entries),?,?,?,?) > > it works with static configuration (slapd.conf) : I successfully managed > to insert some data into the postgresql tables > > But after having converted it to cn=config (slaptest -f slapd.conf -F > slapd.d) slapd doesn't start anymore : > 0ff3f0a <<< dnPrettyNormal: <cn=root,dc=example,dc=com>, > <cn=root,dc=example,dc=com> > 50ff3f0a olcSqlInsEntryStmt: value #0: <olcSqlInsEntryStmt> extra cruft > after <SQL expression>. > 50ff3f0a config error processing olcDatabase={1}sql,cn=config: > <olcSqlInsEntryStmt> *extra cruft after <SQL expression>* > 50ff3f0a send_ldap_result: conn=-1 op=0 p=0 > 50ff3f0a send_ldap_result: err=19 matched="" text="" > 50ff3f0a slapd destroy: freeing system resources. > 50ff3f0a slapd stopped. > 50ff3f0a connections_destroy: nothing to destroy. > > I believe it's a bug, no ? Yes, it's a bug. The conversion should have used double-quotes on these parameters. Will be fixed shortly. -- -- 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

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