openldap-bugs

openldap-bugs@openldap.org

1 participants
21001 discussions

(ITS#7503) slapcat: retry a few times when retrieving an entry
by balint＠balintreczey.hu 25 Jan '13

25 Jan '13

Full_Name: Balint Reczey Version: master OS: Linux URL: http://rbalint.cs.bme.hu/0001-slapcat-retry-a-few-times-when-retrieving-an-… Submission from: (NULL) (84.0.168.17) From: Axel Beckert <beckert(a)phys.ethz.ch> To: Debian Bug Tracking System <submit(a)bugs.debian.org> Subject: slapd: slapcat output truncated every now and then Date: Tue, 15 May 2012 18:33:57 +0200 Package: slapd Severity: grave Version: 2.4.23-7.2 Justification: Causes data loss Every now and then slapcat's output does not contain the whole content of the LDAP but is truncated at some LDIF entry border (i.e. all printed LDIF records seem complete). To reproduce run "while sleep 1; do slapcat | wc; done" on a moderately busy LDAP server (writes every few seconds to minutes; about 10000 entries) while slapd is running and notice the occasionally occurring huge change in wc's printed values, e.g.: # while sleep 1; do slapcat | wc; done 471698 1015498 15336677 471698 1015498 15336677 471698 1015498 15336677 ... 471698 1015497 15336635 471698 1015497 15336635 281829 606820 8632165 <-- 471698 1015497 15336635 471698 1015497 15336635 471698 1015497 15336635 308627 664573 9476751 <-- 471698 1015497 15336635 471698 1015497 15336635 471698 1015497 15336637 Please see email thread starting at http://www.openldap.org/lists/openldap-technical/201301/msg00195.html The attached modifications to OpenLDAP Software are subject to the following notice: Copyright 2013 Balint Reczey <balint(a)balintreczey.hu> Redistribution and use in source and binary forms, with or without modification, are permitted only as authorized by the OpenLDAP Public License.

1 0

(ITS#7502) slapcat: retry a few times when retrieving an entry
by balint＠balintreczey.hu 25 Jan '13

25 Jan '13

Full_Name: Balint Reczey Version: master OS: Linux URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (84.0.168.17) From: Axel Beckert <beckert(a)phys.ethz.ch> To: Debian Bug Tracking System <submit(a)bugs.debian.org> Subject: slapd: slapcat output truncated every now and then Date: Tue, 15 May 2012 18:33:57 +0200 Package: slapd Severity: grave Version: 2.4.23-7.2 Justification: Causes data loss Every now and then slapcat's output does not contain the whole content of the LDAP but is truncated at some LDIF entry border (i.e. all printed LDIF records seem complete). To reproduce run "while sleep 1; do slapcat | wc; done" on a moderately busy LDAP server (writes every few seconds to minutes; about 10000 entries) while slapd is running and notice the occasionally occurring huge change in wc's printed values, e.g.: # while sleep 1; do slapcat | wc; done 471698 1015498 15336677 471698 1015498 15336677 471698 1015498 15336677 ... 471698 1015497 15336635 471698 1015497 15336635 281829 606820 8632165 <-- 471698 1015497 15336635 471698 1015497 15336635 471698 1015497 15336635 308627 664573 9476751 <-- 471698 1015497 15336635 471698 1015497 15336635 471698 1015497 15336637 Please see email thread starting at http://www.openldap.org/lists/openldap-technical/201301/msg00195.html

1 0

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

25 Jan '13

Le 25/01/2013 15:59, Howard Chu a écrit : > Benin Technologies wrote: >> i was just testing back-sql, so my slapd.conf is basically the one >> that's shipped with openldap, as in >> "servers/slapd/back-sql/rdbms_depend/pgsql/slapd.conf > > OK, found the bug, fixed now in master. YEP, just tested it, it works. Many thanks !

1 0

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

25 Jan '13

Benin Technologies wrote: > i was just testing back-sql, so my slapd.conf is basically the one > that's shipped with openldap, as in > "servers/slapd/back-sql/rdbms_depend/pgsql/slapd.conf OK, found the bug, fixed now in master. > Le 24/01/2013 20:00, Howard Chu a écrit : >> Benin Technologies wrote: >>> Le 24/01/2013 13:31, Howard Chu a écrit : >>>> 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.) >> >>> OK let me know when you fixed it, it the meantime I'll switch back to >>> slapd.conf >> >> Can you please include your slapd.conf here in this ITS? -- -- 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

i was just testing back-sql, so my slapd.conf is basically the one that's shipped with openldap, as in "servers/slapd/back-sql/rdbms_depend/pgsql/slapd.conf I just changed a few parameters, like the pid and argfile directory, odbc and database parameters here it is include /usr/local/etc/openldap/schema/core.schema include /usr/local/etc/openldap/schema/cosine.schema include /usr/local/etc/openldap/schema/inetorgperson.schema # Define global ACLs to disable default read access. pidfile /var/run/slapd/slapd.pid argsfile /var/run/slapd/slapd.args ####################################################################### # sql database definitions ####################################################################### database sql suffix "dc=example,dc=com" rootdn "cn=root,dc=example,dc=com" rootpw secret dbname LdapTest dbuser ldaptest dbpasswd ldaptest insentry_stmt "insert into ldap_entries (id,dn,oc_map_id,parent,keyval) values ((select max(id)+1 from ldap_entries),?,?,?,?)" upper_func "upper" strcast_func "text" concat_pattern "?||?" has_ldapinfo_dn_ru no Le 24/01/2013 20:00, Howard Chu a écrit : > Benin Technologies wrote: >> Le 24/01/2013 13:31, Howard Chu a écrit : >>> 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.) > >> OK let me know when you fixed it, it the meantime I'll switch back to >> slapd.conf > > Can you please include your slapd.conf here in this ITS? >

1 0

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

24 Jan '13

Benin Technologies wrote: > Le 24/01/2013 13:31, Howard Chu a écrit : >> 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.) > OK let me know when you fixed it, it the meantime I'll switch back to > slapd.conf Can you please include your slapd.conf here in this ITS? -- -- 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

Le 24/01/2013 13:31, Howard Chu a écrit : > 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.) > OK let me know when you fixed it, it the meantime I'll switch back to slapd.conf Thanks BT

1 0

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

24 Jan '13

On Jan 24, 2013, at 5:32 AM, Howard Chu wrote: > 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. > "#if 0" seems to be a common practice in the code. I only removed the one in the patch. Please find in the link below. https://dl.dropbox.com/u/94235048/back_ldap_tcp_keepalive.patch Ted C. Cheng Symas Corporation

1 0

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

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