openldap-bugs December 2011

openldap-bugs@openldap.org

20 participants
34 discussions

Re: (ITS#7104) refreshOnly syncrepl out of sync during bulk update/delete operations
by mkrz＠free.fr 16 Dec '11

16 Dec '11

----- Mail Original ----- De: "Howard Chu" <hyc(a)symas.com> À: mkrz(a)free.fr Cc: openldap-its(a)openldap.org Envoyé: Jeudi 8 Décembre 2011 22h37:21 GMT +01:00 Amsterdam / Berlin / Berne / Rome / Stockholm / Vienne Objet: Re: (ITS#7104) refreshOnly syncrepl out of sync during bulk update/delete operations >> I noticed an issue with "refreshOnly" syncrepl when a large number of records is >> added, updated and deleted. At the end of synchronization the contextCSN is >> equal on all servers, but the data is out of synchronization for some deleted >> records that remains undeleted on consumer/slave servers. >> >> Restarting the consumer or forcing a synchronization with "slapd ... -c >> 'rid=1,csn=0' " does not help. > >This appears to caused by the sessionlog overflowing due to incoming modifies >that occur after the refresh operation has begun. I would call this a >misconfigured server, since the sessionlog can only ever be useful if you size >it large enough to accomodate all of your update traffic. > >I don't have any plans to fix this issue; fix the server configuration. Thank you for your answer. I withdrew the "syncprov-sessionlog" parameter and this fixed the data loss issue.

1 0

Re: (ITS#7112) Slapd Daemon leaking file descriptor
by quanah＠zimbra.com 15 Dec '11

15 Dec '11

--On Friday, December 16, 2011 5:45 AM +0000 aditya1606(a)gmail.com wrote: > Full_Name: Aditya Bajaj > Version: 2.2.30 > OS: RHEL 5.7 > URL: ftp://ftp.openldap.org/incoming/ > Submission from: (NULL) (192.100.112.203) 2.2 is not a supported release series. 2.3 is not a supported release series. Upgrade to a supported release series. This ticket will be closed. --Quanah -- Quanah Gibson-Mount Sr. Member of Technical Staff Zimbra, Inc A Division of VMware, Inc. -------------------- Zimbra :: the leader in open source messaging and collaboration

1 0

(ITS#7112) Slapd Daemon leaking file descriptor
by aditya1606＠gmail.com 15 Dec '11

15 Dec '11

Full_Name: Aditya Bajaj Version: 2.2.30 OS: RHEL 5.7 URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (192.100.112.203) Hello, losf of slapd is showing like this slapd 10127 root 585u sock 0,5 3532897126 can't identify protocol we have read openldap previous queries , were it as being mentioned that its already fixed in 2.3.32 or after. My question is what was the ticket number that fixed this issue. we would like to now more about that ticket. Regards Aditya

1 0

(ITS#7111) Forward bug-fix commits to ITS
by hyc＠OpenLDAP.org 15 Dec '11

15 Dec '11

Full_Name: Howard Chu Version: any OS: URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (76.94.188.8) Submitted by: hyc Testing...

1 0

Re: (ITS#7107) cn=config syncrepl fails with "controls require LDAPv3" on bound v3 connection
by hyc＠symas.com 15 Dec '11

15 Dec '11

hume-ol(a)bofh.ca wrote: > I have reproduced the problem on 2.4.27. The mentioned ldapsearch query > seems to have a high probability of success if run immediately after > server start, which also seems true on 2.4.28. > > I threw in an extra Debug() line and op->op_protocol == 2 at the check. > > I'm rebuilding with as many debugging symbols enabled as possible to try > to figure out what's going on. A fix for this is in git master, please test. -- -- Howard Chu CTO, Symas Corp. http://www.symas.com Director, Highland Sun http://highlandsun.com/hyc/ Chief Architect, OpenLDAP http://www.openldap.org/project/

1 0

(ITS#7110) cn=config mixes values
by raphael.ouazana＠linagora.com 15 Dec '11

15 Dec '11

Full_Name: Raphael Ouazana Version: 2.4.26 OS: Linux URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (213.41.232.151) Hi, I try to modify valuse of eg. olcAccess with a certain order, I get different values if numbered values are in the correct order or not. Case 1 (normal): dn: olcDatabase={3}bdb,cn=config changetype: modify replace: olcAccess olcAccess: {0} to * by dn.base=cn=0,dc=example,dc=com write olcAccess: {1} to * by dn.base=cn=1,dc=example,dc=com write olcAccess: {2} to * by dn.base=cn=2,dc=example,dc=com write Result: olcAccess: {0} to * by dn.base=cn=0,dc=example,dc=com write olcAccess: {1} to * by dn.base=cn=2,dc=example,dc=com write olcAccess: {2} to * by dn.base=cn=1,dc=example,dc=com write Case 2 (inversed values): dn: olcDatabase={3}bdb,cn=config changetype: modify replace: olcAccess olcAccess: {2} to * by dn.base=cn=2,dc=example,dc=com write olcAccess: {1} to * by dn.base=cn=1,dc=example,dc=com write olcAccess: {0} to * by dn.base=cn=0,dc=example,dc=com write Result: olcAccess: {0} to * by dn.base=cn=0,dc=example,dc=com write olcAccess: {1} to * by dn.base=cn=2,dc=example,dc=com write olcAccess: {2} to * by dn.base=cn=1,dc=example,dc=com write The two last values are incorrectly mixed. Regards, Raphaël Ouazana.

1 0

Re: (ITS#7109) Slapd Freezing
by h.b.furuseth＠usit.uio.no 14 Dec '11

14 Dec '11

I wrote: >> And what information should we provide to solve this problem? (strace, gdb >> log, db_stat or something else?) > > Server log from slapd, and gdb 'thread apply all backtrace'. Eh, I forgot the obvious one: slapd's configuration, minus any passwords. -- Hallvard

1 0

Re: (ITS#7109) Slapd Freezing
by quanah＠zimbra.com 12 Dec '11

12 Dec '11

--On Saturday, December 10, 2011 7:07 PM +0000 h.b.furuseth(a)usit.uio.no wrote: > Unfortunately OpenLDAP installation strips debugging symbols by default, > which makes backtraces nearly useless. You can prevent that by > configuring with > ./configure --enable-memberof ac_cv_prog_STRIP=: You can also do it at install time by simply typing: make install STRIP="" --Quanah -- Quanah Gibson-Mount Sr. Member of Technical Staff Zimbra, Inc A Division of VMware, Inc. -------------------- Zimbra :: the leader in open source messaging and collaboration

1 0

Re: (ITS#7050) meta stop at the first unreachable candidate
by hyc＠symas.com 12 Dec '11

12 Dec '11

llg(a)portaildulibre.fr wrote: > Does anybody knows if and when this patch will be included in future > versions ? No, the patch is wrong. A new fix is in git master now. -- -- 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#7109) Slapd Freezing
by h.b.furuseth＠usit.uio.no 10 Dec '11

10 Dec '11

nikolay.bogdanov(a)flant.ru writes: > Version: 2.4.23 > (...) What can you advice for us? Upgrade, building from the source at www.openldap.org. There are several possibly-related bugfixes since 2.4.23. Then report back whether nor not that fixed the problem. If it is: > And what information should we provide to solve this problem? (strace, gdb > log, db_stat or something else?) Server log from slapd, and gdb 'thread apply all backtrace'. Unfortunately OpenLDAP installation strips debugging symbols by default, which makes backtraces nearly useless. You can prevent that by configuring with ./configure --enable-memberof ac_cv_prog_STRIP=: -- Hallvard

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

openldap-bugs December 2011