- openldap-bugs - openldap.org

Re: (ITS#8148) exattrs=memberOf in consumer causes removal of memberOf attributes
by hyc＠symas.com 19 May '15

19 May '15

alexoz66(a)gmail.com wrote: > Full_Name: John Alex. > Version: 2.4.40 > OS: FreeBSD 9.3 > URL: ftp://ftp.openldap.org/incoming/ > Submission from: (NULL) (176.58.252.240) > > > I have a consumer configured with slapo-memberof and exattrs=memberof in order > to keep track of group memberships locally as suggested in the manpages. This > works ok when adding/deleting users to groups, but when a user entry containing > "memberOf" values is modified, those values are deleted in the consumer. > According to ITS#7400, exattrs=memberOf is necessary to avoid getting this > attribute from the provider. I see nothing in ITS#7400 that even mentions exattrs. In fact there's nothing conclusive in ITS#7400 at all, it only says the issue should be taken up on the -devel mailing list and needs new design work. > However, it was suggested to me to remove > "memberOf" from exattrs, which I did and now everything seems to work fine. > > In any case, even if exattrs=memberof is not needed anymore, it should not have > any effect to the local slapo-memberof operations. Sorry, that doesn't follow. Adding settings will invariably change some server behavior. Adding a setting that you didn't need generally turns a working config into a broken config. > See also: http://www.openldap.org/lists/openldap-technical/201505/msg00124.html -- -- 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#8148) exattrs=memberOf in consumer causes removal of memberOf attributes
by alexoz66＠gmail.com 19 May '15

19 May '15

Full_Name: John Alex. Version: 2.4.40 OS: FreeBSD 9.3 URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (176.58.252.240) I have a consumer configured with slapo-memberof and exattrs=memberof in order to keep track of group memberships locally as suggested in the manpages. This works ok when adding/deleting users to groups, but when a user entry containing "memberOf" values is modified, those values are deleted in the consumer. According to ITS#7400, exattrs=memberOf is necessary to avoid getting this attribute from the provider. However, it was suggested to me to remove "memberOf" from exattrs, which I did and now everything seems to work fine. In any case, even if exattrs=memberof is not needed anymore, it should not have any effect to the local slapo-memberof operations. See also: http://www.openldap.org/lists/openldap-technical/201505/msg00124.html

1 0

Re: (ITS#8142) back-ldap transparent reconnecting is not so transparent
by hyc＠symas.com 19 May '15

19 May '15

ebackes(a)symas.com wrote: > Full_Name: Emily Backes > Version: 2.4 > OS: > URL: > Submission from: (NULL) (50.113.67.84) > > > Currently, back-ldap stores credentials in the outbound connection > structure. When that disappears, e.g. from idle-timeout, conn-ttl, > network lossage, AD trouble, etc., the connection becomes unbound and > AD returns err=1 (Operations error), which isn't enougfofor back-ldap > to treat it as LDAP_UNAVAILABLE. > > Howard reports this is working-as-designed, even if the design is bad. > Several ITS filings are still open about this problem; 5110, 6571, and > 7464 are all related. > > At a minimum, we should drop the client connection if we can't keep > the session stable. This is not as simple as it sounds. In particular, back-ldap may be part of a larger glued tree of backends. A failure to search in the back-ldap context should not prevent the rest of the glued tree from being searched, and it should not drop the client connection. -- -- 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#8147) syncrepl fails when encountering bad data, master leaks memory
by Mark.Bannister＠morganstanley.com 19 May '15

19 May '15

> > I did see that a number of memory leaks have been fixed since 2.4.30, b= ut I > > didn't see anything that looked like this profile. Sorry I don't have = a newer > > version of OpenLDAP to hand to re-test. > > Closing this ITS. You can followup again if you see the same problem in t= he=20 > current 2.4.41 release candidate. 2.4.30 is over 3 years old, no one is g= oing=20 > to investigate this. I wasn't asking anyone to look into 2.4.30. Given how easy this is to test= , Howard, and in the interests of code hygiene, wouldn't it be better for you to spen= d 10 minutes attempting to reproduce the problem on the latest RC? It'll take me much l= onger to download and compile the new RC than it would do for you to import a bad en= try and set-up basic syncrepl. If, by doing so, you can identify and fix another m= emory leak then that's a really good thing. If you can't reproduce it in 2.4.41 after= 10 minutes, then I understand if you close the issue. Best regards, Mark. ---------------------------------------------------------------------------= ----- NOTICE: Morgan Stanley is not acting as a municipal advisor and the opinion= s or views contained herein are not intended to be, and do not constitute, = advice within the meaning of Section 975 of the Dodd-Frank Wall Street Refo= rm and Consumer Protection Act. If you have received this communication in = error, please destroy all electronic and paper copies; do not disclose, use= or act upon the information; and notify the sender immediately. Mistransmi= ssion is not intended to waive confidentiality or privilege. Morgan Stanley= reserves the right, to the extent permitted under applicable law, to monit= or electronic communications. This message is subject to terms available at= the following link: http://www.morganstanley.com/disclaimers. If you canno= t access these links, please notify us by reply message and we will send th= e contents to you. By messaging with Morgan Stanley you consent to the fore= going.=

1 0

Re: (ITS#8147) syncrepl fails when encountering bad data, master leaks memory
by hyc＠symas.com 19 May '15

19 May '15

mark.bannister(a)morganstanley.com wrote: > Full_Name: Mark Bannister > Version: 2.4.30 > OS: Oracle Solaris 11.2 > URL: ftp://ftp.openldap.org/incoming/ > Submission from: (NULL) (205.228.82.171) > > > I have a master server and a replica configured with syncrepl in > refreshAndPersist mode. Im using bdb (not mdb), simple auth (not SASL), > standard syncrepl (not delta-syncrepl). > > I noticed that the directory has about 5 erroneous entries in 300,000 where > there is a multi-valued attribute containing two identical values. These > entries were added by slapadd -q. Here is an example: > > dn: cn=test,ou=rpc,dc=mycompany,dc=com > objectClass: oncRpc > cn: test > cn: test > oncRpcNumber: 12345678 The docs already tell you to only use slapadd with known-good data. > I did see that a number of memory leaks have been fixed since 2.4.30, but I > didn't see anything that looked like this profile. Sorry I don't have a newer > version of OpenLDAP to hand to re-test. Closing this ITS. You can followup again if you see the same problem in the current 2.4.41 release candidate. 2.4.30 is over 3 years old, no one is going to investigate this. -- -- 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#8147) syncrepl fails when encountering bad data, master leaks memory
by mark.bannister＠morganstanley.com 19 May '15

19 May '15

Full_Name: Mark Bannister Version: 2.4.30 OS: Oracle Solaris 11.2 URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (205.228.82.171) I have a master server and a replica configured with syncrepl in refreshAndPersist mode. Im using bdb (not mdb), simple auth (not SASL), standard syncrepl (not delta-syncrepl). I noticed that the directory has about 5 erroneous entries in 300,000 where there is a multi-valued attribute containing two identical values. These entries were added by slapadd -q. Here is an example: dn: cn=test,ou=rpc,dc=mycompany,dc=com objectClass: oncRpc cn: test cn: test oncRpcNumber: 12345678 When the replica attempts to copy this data using syncrepl from the master server, it fails. All entries up to that point are synchronised fine, but any entries from that point onwards are missing. I didn't see any log entries telling me about this failure, although I admit I didn't look very hard or tweak the log levels. This then causes a memory leak in the master server: $ while :; do ps -p 9025 -o pid,ppid,pmem,rss,vsz,args | tail +2; sleep 60; done 9025 1 5.2 434204 463892 /usr/lib/slapd -f /etc/openldap/slapd.conf -u openldap -g openldap -h ldap:/// 9025 1 5.3 443216 472900 /usr/lib/slapd -f /etc/openldap/slapd.conf -u openldap -g openldap -h ldap:/// 9025 1 5.4 444384 474076 /usr/lib/sla - -f /etc/openldap/slapd.conf -u openldap -g openldap -h ldap:/// 9025 1 5.5 454680 484364 /usr/lib/slapd -f /etc/openldap/slapd.conf -u openldap -g openldap -h ldap:/// 9025 1 5.5 458288 487972 /usr/lib/slapd -f /etc/openldap/slapd.conf -u openldap -g openldap -h ldap:/// 9025 1 5.6 464996 494684 /usr/lib/slapd -f /etc/openldap/slapd.conf -u openldap -g openldap -h ldap:/// 9025 1 5.7 472952 502636 /usr/lib/slapd -f /etc/openldap/slapd.conf -u openldap -g openldap -h ldap:/// ... until memory is exhausted, and I get: ch_malloc of 606572 bytes failed ... followed by a 3GB core dump file. When the server restarts, the cycle starts over again, ad infinitum until the filesystem is full of core dump files. When I remove the 5 duplicate attribute values and restart the master and replica servers, the entire directory is then successfully replicated and the memory footprint of the slapd process remains stable. I am therefore assuming that the duplicate attribute values were causing syncrepl not to complete and a memory leak in the master server. I did see that a number of memory leaks have been fixed since 2.4.30, but I didn't see anything that looked like this profile. Sorry I don't have a newer version of OpenLDAP to hand to re-test.

1 0

Re: (ITS#8117) Bugs related to key-size in lmdb and backend
by h.b.furuseth＠usit.uio.no 18 May '15

18 May '15

On 04/05/15 02:13, h.b.furuseth(a)usit.uio.no wrote: > (...) If I understand correctly this time, the doc should > simply say that the two types size_t and unsigned int are supported. > The "typically" is plain misleading. > > That is, if mdb_node_search() shows the intent when it picks either > int-sized or size_t-sized for IS_BRANCH. OTOH, another bug: > > default_cmp pick cmp_int for INTEGERDUP|DUPFIXED and some other > replaces md_dcmp = cmp_int with cmp_long, which makes no sense unless > cmp_int is just a placeholder. Yet at least mdb_dcmp() calls that > placeholder directly without checking the data size. If that's the intent, branch "mdb/keysize" @ my UiO repo fixes it. Should it do the following too? > And if it's > just a placeholder, how about instead setting dcmp to something which > just abort()s, to make sure the bug of not replacing it is caught? Hallvard

1 0

Re: (ITS#8146) Slapd with mdb consumes 100% CPU if deref aliases is requested
by andrew.findlay＠skills-1st.co.uk 18 May '15

18 May '15

On Mon, May 18, 2015 at 04:58:29PM +0000, Howard Chu wrote: > > (On my laptop, "all possible" is 2^64 - 1 so yes, this will spin for .. a while.) 584942 years at 1M tests/sec - I am not waiting around for the timeout :-) (or the electricity bill: over £10M at todays prices) > Fixed now in git master. Thanks Andrew -- ----------------------------------------------------------------------- | From Andrew Findlay, Skills 1st Ltd | | Consultant in large-scale systems, networks, and directory services | | http://www.skills-1st.co.uk/ +44 1628 782565 | -----------------------------------------------------------------------

1 0

Re: (ITS#8146) Slapd with mdb consumes 100% CPU if deref aliases is requested
by hyc＠symas.com 18 May '15

18 May '15

hyc(a)symas.com wrote: > Andrew Findlay wrote: >> On Mon, May 18, 2015 at 04:48:13PM +0100, Howard Chu wrote: >> >>> ITS#8103 fix crash with more than 65535 aliases in a scope >> >> Ah - my test case does not have any aliases at all so it may be an >> unrelated issue. > > I see, your issue is caused by the fact you haven't indexed the objectClass > attribute. When back-mdb does a search to find all the alias objects in the > DB, instead of returning zero, it returns unknown which causes it to loop > through all possible entryIDs looking for alias entries. > > (On my laptop, "all possible" is 2^64 - 1 so yes, this will spin for .. a while.) > Fixed now in git master. -- -- 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#8146) Slapd with mdb consumes 100% CPU if deref aliases is requested
by hyc＠symas.com 18 May '15

18 May '15

Andrew Findlay wrote: > On Mon, May 18, 2015 at 04:48:13PM +0100, Howard Chu wrote: > >> ITS#8103 fix crash with more than 65535 aliases in a scope > > Ah - my test case does not have any aliases at all so it may be an > unrelated issue. I see, your issue is caused by the fact you haven't indexed the objectClass attribute. When back-mdb does a search to find all the alias objects in the DB, instead of returning zero, it returns unknown which causes it to loop through all possible entryIDs looking for alias entries. (On my laptop, "all possible" is 2^64 - 1 so yes, this will spin for .. a while.) -- -- 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#8146) Slapd with mdb consumes 100% CPU if deref aliases is requested
by andrew.findlay＠skills-1st.co.uk 18 May '15

18 May '15

On Mon, May 18, 2015 at 04:48:13PM +0100, Howard Chu wrote: > ITS#8103 fix crash with more than 65535 aliases in a scope Ah - my test case does not have any aliases at all so it may be an unrelated issue. Andrew -- ----------------------------------------------------------------------- | From Andrew Findlay, Skills 1st Ltd | | Consultant in large-scale systems, networks, and directory services | | http://www.skills-1st.co.uk/ +44 1628 782565 | -----------------------------------------------------------------------

1 0

Re: (ITS#8146) Slapd with mdb consumes 100% CPU if deref aliases is requested
by hyc＠symas.com 18 May '15

18 May '15

Andrew Findlay wrote: > On Mon, May 18, 2015 at 12:39:17PM +0100, Howard Chu wrote: > >> Already fixed in RE24. > > Not in the version that I pulled 10 minutes ago... > > openldap-OPENLDAP_REL_ENG_2_4-e445af3 Hmm. violino:~/OD/gr24/servers/slapd> git log -1 back-mdb commit e1fdac9db59e4677b9a2403a072558bd89e44321 Author: Howard Chu <hyc(a)openldap.org> Date: Mon Apr 13 13:11:29 2015 -0700 ITS#8103 fix crash with more than 65535 aliases in a scope I'll look at your test case shortly, thanks. -- -- 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#8146) Slapd with mdb consumes 100% CPU if deref aliases is requested
by andrew.findlay＠skills-1st.co.uk 18 May '15

18 May '15

On Mon, May 18, 2015 at 12:39:17PM +0100, Howard Chu wrote: > Already fixed in RE24. Not in the version that I pulled 10 minutes ago... openldap-OPENLDAP_REL_ENG_2_4-e445af3 Andrew -- ----------------------------------------------------------------------- | From Andrew Findlay, Skills 1st Ltd | | Consultant in large-scale systems, networks, and directory services | | http://www.skills-1st.co.uk/ +44 1628 782565 | -----------------------------------------------------------------------

1 0

Re: (ITS#8146) Slapd with mdb consumes 100% CPU if deref aliases is requested
by hyc＠symas.com 18 May '15

18 May '15

andrew.findlay(a)skills-1st.co.uk wrote: > Full_Name: Andrew Findlay > Version: 2.4.40 > OS: Linux: OpenSuSE 13.2 > URL: ftp://ftp.openldap.org/incoming/openldap-mdb-spin-bug.tgz > Submission from: (NULL) (2001:8b0:8d0:f7e1:61a6:169e:b4ba:9954) > > > Some client programs (such as Apache Directory Studio) request alias > dereferencing by default. This puts slapd with mdb into a spin where it consumes > 100% of a CPU. Other threads continue to work and new connections are accepted. > Timeouts do not terminate the spin. Disconnecting the client does not terminate > the spin. Already fixed in RE24. > To reproduce: start slapd and issue a search of the form: > > ldapsearch -a search -x -b dc=example,dc=org objectclass=person > > I have placed a tarball on the FTP server containing: > > slapd.conf > sample data in LDIF > gdb output showing thread trace after breaking in > script of client commands > > The build options were: > > CFLAGS=-g > export CFLAGS > > ./configure --prefix=/meme/andrew/test/openldap-2.4.40 \ > --enable-spasswd \ > --enable-crypt \ > --enable-slapi \ > --enable-overlays \ > --enable-hdb=no \ > --enable-bdb=no \ > --enable-ldap \ > --enable-rewrite \ > --enable-meta \ > --enable-null \ > --enable-monitor \ > --enable-relay \ > --enable-sock \ > --with-cyrus-sasl \ > --with-tls > > > For those that need it, the workaround with Apache Directory Studio is to > disable alias dereferencing in the Browser Options tab for the connection. > > Andrew > > -- -- 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#8146) Slapd with mdb consumes 100% CPU if deref aliases is requested
by andrew.findlay＠skills-1st.co.uk 18 May '15

18 May '15

Full_Name: Andrew Findlay Version: 2.4.40 OS: Linux: OpenSuSE 13.2 URL: ftp://ftp.openldap.org/incoming/openldap-mdb-spin-bug.tgz Submission from: (NULL) (2001:8b0:8d0:f7e1:61a6:169e:b4ba:9954) Some client programs (such as Apache Directory Studio) request alias dereferencing by default. This puts slapd with mdb into a spin where it consumes 100% of a CPU. Other threads continue to work and new connections are accepted. Timeouts do not terminate the spin. Disconnecting the client does not terminate the spin. To reproduce: start slapd and issue a search of the form: ldapsearch -a search -x -b dc=example,dc=org objectclass=person I have placed a tarball on the FTP server containing: slapd.conf sample data in LDIF gdb output showing thread trace after breaking in script of client commands The build options were: CFLAGS=-g export CFLAGS ./configure --prefix=/meme/andrew/test/openldap-2.4.40 \ --enable-spasswd \ --enable-crypt \ --enable-slapi \ --enable-overlays \ --enable-hdb=no \ --enable-bdb=no \ --enable-ldap \ --enable-rewrite \ --enable-meta \ --enable-null \ --enable-monitor \ --enable-relay \ --enable-sock \ --with-cyrus-sasl \ --with-tls For those that need it, the workaround with Apache Directory Studio is to disable alias dereferencing in the Browser Options tab for the connection. Andrew

1 0

Re: (ITS#8145) The olcThreadQueues config element is not documented
by elecharny＠gmail.com 16 May '15

16 May '15

Le 15/05/15 19:14, Howard Chu a écrit : > Emmanuel Lécharny wrote: >> Le 15/05/15 13:40, Howard Chu a écrit : >>> elecharny(a)apache.org wrote: >>>> Full_Name: Emmanuel L.charny >>>> Version: 2.4.40 >>>> OS: >>>> URL: ftp://ftp.openldap.org/incoming/ >>>> Submission from: (NULL) (83.202.0.248) >>>> >>>> >>>> The olcThreadQueues AttributeType is part of the olcGlobal >>>> OvjectClass since >>>> 2.4.36, where it's has been added. >>>> A man slapd-config provides no information on this parameter. >>> >>> You're mistaken. The olcThreadQueues feature has not been included in >>> any official 2.4 release, it is a 2.5 feature. >>> >> Sadly, I can't comment on an ITS. So here it is : >> >> "It may not be official, but it's present in the code base since 2.4.36, >> it's also present as a MAY attribute in the olcGlobal ObjectClass. > > No. You misunderstand - it is *NOT* present in the 2.4 source tree. It > has *never* been present in the 2.4 source tree. > It's present in HEAD, which I suppose is now the 2.5 branch : http://www.openldap.org/devel/gitweb.cgi?p=openldap.git;a=blob;f=servers/sl… The web browser is kind of confusing... And, no, it's not present in tag 2.4.40. The ITS can be closed, sorry for the noise.

1 0

Re: (ITS#8125) MMR throws away valid changes causing drift
by quanah＠zimbra.com 15 May '15

15 May '15

--On Friday, May 15, 2015 7:45 PM +0000 quanah(a)zimbra.com wrote: > --On Friday, May 15, 2015 8:39 PM +0100 Howard Chu <hyc(a)symas.com> wrote: > >> quanah(a)zimbra.com wrote: >>> This is caused by modify ops: >>> >>> [zimbra@ldap02-dc01 xx]$ grep $20$ /var/log/zimbra.log >>> May 15 08:35:46 ldap02-dc01 slapd[18167]: syncrepl_message_to_op: >>> rid=201 be_modify uid=xxx,ou=people,dc=xxx,dc=com (20) >> >> Multiple TYPE_OR_VALUE_EXISTS errors indicate you're sending a lot of >> mods that were already performed. Sounds more like a serverID or URL >> misconfig here if there are actually only 2 servers talking. > > ServerID's are unique (2 & 3). There is no URL portion to the config, as > we're not replicating cn=config. In 6 days, the servers have gotten > totally out of sync with one another, and REFRESH mode isn't fixing it > either. Note that the drift is occurring on an attribute that is multi-valued: zimbraPasswordLockoutFailureTime The values stored in the attribute are only granular down to the second, so it's not uncommon for multiple writes of the same value (add/mod/delete) to occur for this attribute. --Quanah -- Quanah Gibson-Mount Platform Architect Zimbra, Inc. -------------------- Zimbra :: the leader in open source messaging and collaboration

1 0

Re: (ITS#8125) MMR throws away valid changes causing drift
by quanah＠zimbra.com 15 May '15

15 May '15

--On Friday, May 15, 2015 8:39 PM +0100 Howard Chu <hyc(a)symas.com> wrote: > quanah(a)zimbra.com wrote: >> This is caused by modify ops: >> >> [zimbra@ldap02-dc01 xx]$ grep $20$ /var/log/zimbra.log >> May 15 08:35:46 ldap02-dc01 slapd[18167]: syncrepl_message_to_op: rid=201 >> be_modify uid=xxx,ou=people,dc=xxx,dc=com (20) > > Multiple TYPE_OR_VALUE_EXISTS errors indicate you're sending a lot of > mods that were already performed. Sounds more like a serverID or URL > misconfig here if there are actually only 2 servers talking. ServerID's are unique (2 & 3). There is no URL portion to the config, as we're not replicating cn=config. In 6 days, the servers have gotten totally out of sync with one another, and REFRESH mode isn't fixing it either. --Quanah -- Quanah Gibson-Mount Platform Architect Zimbra, Inc. -------------------- Zimbra :: the leader in open source messaging and collaboration

1 0

Re: (ITS#8125) MMR throws away valid changes causing drift
by hyc＠symas.com 15 May '15

15 May '15

quanah(a)zimbra.com wrote: > This is caused by modify ops: > > [zimbra@ldap02-dc01 xx]$ grep $20$ /var/log/zimbra.log > May 15 08:35:46 ldap02-dc01 slapd[18167]: syncrepl_message_to_op: rid=201 > be_modify uid=xxx,ou=people,dc=xxx,dc=com (20) Multiple TYPE_OR_VALUE_EXISTS errors indicate you're sending a lot of mods that were already performed. Sounds more like a serverID or URL misconfig here if there are actually only 2 servers talking. > May 15 08:47:44 ldap02-dc01 slapd[18167]: syncrepl_message_to_op: rid=201 > be_modify uid=xxx,ou=people,dc=yyy,dc=co,dc=za (20) > May 15 08:56:03 ldap02-dc01 slapd[18167]: syncrepl_message_to_op: rid=201 > be_modify uid=xxx,ou=people,dc=zzz,dc=co,dc=za (20) > May 15 09:31:12 ldap02-dc01 slapd[18167]: syncrepl_message_to_op: rid=201 > be_modify uid=xxx,ou=people,dc=www,dc=co,dc=za (20) > May 15 10:46:58 ldap02-dc01 slapd[18167]: syncrepl_message_to_op: rid=201 > be_modify uid=xxx,ou=people,dc=ppp,dc=co,dc=za (20) > May 15 13:44:11 ldap02-dc01 slapd[18167]: syncrepl_message_to_op: rid=201 > be_modify uid=xxx,ou=people,dc=rrr,dc=co,dc=za (20) > May 15 14:54:49 ldap02-dc01 slapd[18167]: syncrepl_message_to_op: rid=201 > be_modify uid=xxx,ou=people,dc=zzz,dc=com (20) > May 15 17:23:11 ldap02-dc01 slapd[18167]: syncrepl_message_to_op: rid=201 > be_modify uid=xxx,ou=people,dc=zzz,dc=com (20) > > So overall, there seems to be significant problems with RE24 in relation to > replication at this time. > > Clocks are tightly in sync. > > --Quanah > > -- > > Quanah Gibson-Mount > Platform Architect > Zimbra, Inc. > -------------------- > Zimbra :: the leader in open source messaging and collaboration > > > > -- -- 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#8125) MMR throws away valid changes causing drift
by quanah＠zimbra.com 15 May '15

15 May '15

--On Friday, May 15, 2015 7:25 PM +0000 quanah(a)zimbra.com wrote: > Clocks are tightly in sync. Seeing tons of "greater than snapshot errors". 108 so far today on one host, 144 on the other. Example of one: May 15 17:33:19 ldap01-dc01 slapd[31479]: Entry uid=xxxx,ou=people,dc=yyyy,dc=co,dc=za CSN 20150515153317.592677Z#000000#002#000000 greater than snapshot 20150515153317.320608Z#000000#002#000000 --Quanah -- Quanah Gibson-Mount Platform Architect Zimbra, Inc. -------------------- Zimbra :: the leader in open source messaging and collaboration

1 0

Re: (ITS#8125) MMR throws away valid changes causing drift
by quanah＠zimbra.com 15 May '15

15 May '15

--On Monday, May 11, 2015 7:32 PM +0000 quanah(a)zimbra.com wrote: > --On Friday, May 08, 2015 7:56 PM +0000 quanah(a)zimbra.com wrote: > >> >> >> --On May 4, 2015 at 8:00:45 PM +0000 openldap-its(a)OpenLDAP.org wrote: >> >> >> In addition to the missing entries, multiple differences exist for >> existing entries as well. At this point, it seems that replication with >> 2.4.41 is entirely unsafe. > > The existing entry drift seems to be related to the locked up replication > that occured because of a bug in openssl. So the real issue is just the > entries that weren't created, which is a current known limitation of > syncrepl refresh that needs fixing. Unfortunately, I'm now seeing this at a second customer site with 2-node MMR, where it is running current RE24 (2.4.41). In this case: ldap01 and ldap02 were stopped openldap was upgraded from 2.4.39 to 2.4.41 ldap01's db was slapcat'd ldap02's db was erased ldap02's db was recreated from ldap01's slapcat Now they are having drift, and constant refresh troubles: [zimbra@ldap01-dc01 ~]$ grep REFRESH /var/log/zimbra.log May 15 08:56:02 ldap01-dc01 slapd[31479]: do_syncrep2: rid=201 delta-sync lost sync on (reqStart=20150515065528.000299Z,cn=accesslog), switching to REFRESH May 15 08:58:07 ldap01-dc01 slapd[31479]: do_syncrep2: rid=201 LDAP_RES_INTERMEDIATE - REFRESH_DELETE May 15 09:57:18 ldap01-dc01 slapd[31479]: do_syncrep2: rid=201 delta-sync lost sync on (reqStart=20150515075718.000081Z,cn=accesslog), switching to REFRESH May 15 10:46:57 ldap01-dc01 slapd[31479]: do_syncrep2: rid=201 delta-sync lost sync on (reqStart=20150515084653.000032Z,cn=accesslog), switching to REFRESH May 15 12:43:18 ldap01-dc01 slapd[31479]: do_syncrep2: rid=201 delta-sync lost sync on (reqStart=20150515104318.000049Z,cn=accesslog), switching to REFRESH May 15 16:32:19 ldap01-dc01 slapd[31479]: do_syncrep2: rid=201 delta-sync lost sync on (reqStart=20150515143211.000250Z,cn=accesslog), switching to REFRESH May 15 16:36:41 ldap01-dc01 slapd[31479]: do_syncrep2: rid=201 delta-sync lost sync on (reqStart=20150515143556.000046Z,cn=accesslog), switching to REFRESH May 15 17:23:10 ldap01-dc01 slapd[31479]: do_syncrep2: rid=201 delta-sync lost sync on (reqStart=20150515152310.000002Z,cn=accesslog), switching to REFRESH [zimbra@ldap02-dc01 xx]$ grep FRESH /var/log/zimbra.log May 15 08:35:46 ldap02-dc01 slapd[18167]: do_syncrep2: rid=201 delta-sync lost sync on (reqStart=20150515063539.000009Z,cn=accesslog), switching to REFRESH May 15 08:47:44 ldap02-dc01 slapd[18167]: do_syncrep2: rid=201 delta-sync lost sync on (reqStart=20150515064733.000043Z,cn=accesslog), switching to REFRESH May 15 08:56:03 ldap02-dc01 slapd[18167]: do_syncrep2: rid=201 delta-sync lost sync on (reqStart=20150515065528.000234Z,cn=accesslog), switching to REFRESH May 15 08:57:24 ldap02-dc01 slapd[18167]: do_syncrep2: rid=201 LDAP_RES_INTERMEDIATE - REFRESH_DELETE May 15 09:31:12 ldap02-dc01 slapd[18167]: do_syncrep2: rid=201 delta-sync lost sync on (reqStart=20150515073112.000086Z,cn=accesslog), switching to REFRESH May 15 10:46:58 ldap02-dc01 slapd[18167]: do_syncrep2: rid=201 delta-sync lost sync on (reqStart=20150515084653.000003Z,cn=accesslog), switching to REFRESH May 15 13:44:11 ldap02-dc01 slapd[18167]: do_syncrep2: rid=201 delta-sync lost sync on (reqStart=20150515114405.000313Z,cn=accesslog), switching to REFRESH May 15 14:54:49 ldap02-dc01 slapd[18167]: do_syncrep2: rid=201 delta-sync lost sync on (reqStart=20150515125448.000002Z,cn=accesslog), switching to REFRESH May 15 17:23:11 ldap02-dc01 slapd[18167]: do_syncrep2: rid=201 delta-sync lost sync on (reqStart=20150515152311.000035Z,cn=accesslog), switching to REFRESH This is caused by modify ops: [zimbra@ldap02-dc01 xx]$ grep $20$ /var/log/zimbra.log May 15 08:35:46 ldap02-dc01 slapd[18167]: syncrepl_message_to_op: rid=201 be_modify uid=xxx,ou=people,dc=xxx,dc=com (20) May 15 08:47:44 ldap02-dc01 slapd[18167]: syncrepl_message_to_op: rid=201 be_modify uid=xxx,ou=people,dc=yyy,dc=co,dc=za (20) May 15 08:56:03 ldap02-dc01 slapd[18167]: syncrepl_message_to_op: rid=201 be_modify uid=xxx,ou=people,dc=zzz,dc=co,dc=za (20) May 15 09:31:12 ldap02-dc01 slapd[18167]: syncrepl_message_to_op: rid=201 be_modify uid=xxx,ou=people,dc=www,dc=co,dc=za (20) May 15 10:46:58 ldap02-dc01 slapd[18167]: syncrepl_message_to_op: rid=201 be_modify uid=xxx,ou=people,dc=ppp,dc=co,dc=za (20) May 15 13:44:11 ldap02-dc01 slapd[18167]: syncrepl_message_to_op: rid=201 be_modify uid=xxx,ou=people,dc=rrr,dc=co,dc=za (20) May 15 14:54:49 ldap02-dc01 slapd[18167]: syncrepl_message_to_op: rid=201 be_modify uid=xxx,ou=people,dc=zzz,dc=com (20) May 15 17:23:11 ldap02-dc01 slapd[18167]: syncrepl_message_to_op: rid=201 be_modify uid=xxx,ou=people,dc=zzz,dc=com (20) So overall, there seems to be significant problems with RE24 in relation to replication at this time. Clocks are tightly in sync. --Quanah -- Quanah Gibson-Mount Platform Architect Zimbra, Inc. -------------------- Zimbra :: the leader in open source messaging and collaboration

1 0

Re: (ITS#8145) The olcThreadQueues config element is not documented
by quanah＠zimbra.com 15 May '15

15 May '15

--On Friday, May 15, 2015 12:50 PM +0000 elecharny(a)gmail.com wrote: > You migth object that the reference is what's in the man page, but then, > how possibly can we detect missing parts in the documentation?" You're either using a Symas or Zimbra openldap build to test against, both of which backport 2.5 features not generally available in stock OpenLDAP 2.4. --Quanah -- Quanah Gibson-Mount Platform Architect Zimbra, Inc. -------------------- Zimbra :: the leader in open source messaging and collaboration

1 0

Re: (ITS#8145) The olcThreadQueues config element is not documented
by hyc＠symas.com 15 May '15

15 May '15

Emmanuel Lécharny wrote: > Le 15/05/15 13:40, Howard Chu a écrit : >> elecharny(a)apache.org wrote: >>> Full_Name: Emmanuel L.charny >>> Version: 2.4.40 >>> OS: >>> URL: ftp://ftp.openldap.org/incoming/ >>> Submission from: (NULL) (83.202.0.248) >>> >>> >>> The olcThreadQueues AttributeType is part of the olcGlobal >>> OvjectClass since >>> 2.4.36, where it's has been added. >>> A man slapd-config provides no information on this parameter. >> >> You're mistaken. The olcThreadQueues feature has not been included in >> any official 2.4 release, it is a 2.5 feature. >> > Sadly, I can't comment on an ITS. So here it is : > > "It may not be official, but it's present in the code base since 2.4.36, > it's also present as a MAY attribute in the olcGlobal ObjectClass. No. You misunderstand - it is *NOT* present in the 2.4 source tree. It has *never* been present in the 2.4 source tree. -- -- 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#8145) The olcThreadQueues config element is not documented
by elecharny＠gmail.com 15 May '15

15 May '15

Le 15/05/15 13:40, Howard Chu a écrit : > elecharny(a)apache.org wrote: >> Full_Name: Emmanuel L.charny >> Version: 2.4.40 >> OS: >> URL: ftp://ftp.openldap.org/incoming/ >> Submission from: (NULL) (83.202.0.248) >> >> >> The olcThreadQueues AttributeType is part of the olcGlobal >> OvjectClass since >> 2.4.36, where it's has been added. >> A man slapd-config provides no information on this parameter. > > You're mistaken. The olcThreadQueues feature has not been included in > any official 2.4 release, it is a 2.5 feature. > Sadly, I can't comment on an ITS. So here it is : "It may not be official, but it's present in the code base since 2.4.36, it's also present as a MAY attribute in the olcGlobal ObjectClass. There is no way for me to know that it's a 2.5 feature, if it's in 2.4 branch, and if it's not documented as so. This is not really convenient, as I'm basing the OpenLDAP configuration editor on the content of the existing ObjectClasses. You migth object that the reference is what's in the man page, but then, how possibly can we detect missing parts in the documentation?"

1 0

Re: (ITS#8145) The olcThreadQueues config element is not documented
by hyc＠symas.com 15 May '15

15 May '15

elecharny(a)apache.org wrote: > Full_Name: Emmanuel L.charny > Version: 2.4.40 > OS: > URL: ftp://ftp.openldap.org/incoming/ > Submission from: (NULL) (83.202.0.248) > > > The olcThreadQueues AttributeType is part of the olcGlobal OvjectClass since > 2.4.36, where it's has been added. > A man slapd-config provides no information on this parameter. You're mistaken. The olcThreadQueues feature has not been included in any official 2.4 release, it is a 2.5 feature. -- -- 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

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

openldap-bugs