- openldap-bugs - openldap.org

(ITS#8184) MOD operation with a double delete of a pwdFailureTime attribute
by elecharny＠apache.org 02 Jul '15

02 Jul '15

Full_Name: Emmanuel L.charny Version: 2.4.40 OS: URL: Submission from: (NULL) (212.195.127.200) We get an error when trying to change a password in some combinaison of settings : - 2 servers, one being the master, one being the slave - a few backends (MDB) - one of those backends using the glue overlay, the other being subordinates - 2 backends using the PPolicy overlay : the one which is the parent, and another one being a subordinate. FTR, the PPolicy in use are different What happens is that the password update will try to delete the pwdFailureTime attribute of the impacted entry (and two other attributes, too : pwdGraceUseTime and pwdAccountLockedTime. As we have 2 PPolicies, the attribute deletion will be requested twice, in one single MOD operation. The second DEL modification will then fail, leading to the rejection of the modification. To make it a bit more complex, the pwdFailureTime was updated on the slave, not replicated (it's a slave), and the password update was done on the master, so the failure was on the slave, as the master was pushing the modification to it. At the end, the two servers were not anymore in sync. The reason for this failure was that the code in charge of checking the MOD request, in ppolicy.c, lines 1575 to 1666, aren't checking if a DEL of one of the three attributes is already present in the list of MODIFICATION. Howard's suggestion to get this fix is to replace this code : got_del_fail = 1; if ( !a_fail ) drop = 1; by : if ( !a_fail || got_del_fail ) { drop = 1; } else { got_del_fail = 1; }

1 0

(ITS#8183) ldap_init() failed at sub thread but runs ok at main.
by 1727647302＠qq.com 02 Jul '15

02 Jul '15

Full_Name: wondersoft Version: 2.4.39 OS: CentOS 6.6 X86_64 URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (182.50.119.36) Hi: My server is CentOS 6.6(x86_64). When I create a thread on the main(), it's failed on ldap_init(), but it's ok at main not running on a sub thread. But using the same version and the same code, it runs pretty well at CentOS 6.6(x86_32). Test code is here: void pthread_ldap() { LDAP *ld = NULL; ld=(LDAP*)ldap_init(HOSTNAME,0); if(ld ==NULL) { perror("ldap_init"); return ; } int protocolVersion = LDAP_VERSION3; //It failed here, if ituns s on CentOS 6.6(x86_64) as a sub thread. ldap_set_option( ld, LDAP_OPT_PROTOCOL_VERSION, &(protocolVersion)); return ; } int main() { int ret = 0; pthread_attr_t attr_attribute; pthread_attr_init(&attr_attribute); pthread_attr_setdetachstate(&attr_attribute,PTHREAD_CREATE_DETACHED); pthread_t pid; //If no sub thread created, it's ok //pthread_ldap(); if( pthread_create( &pid, &attr_attribute, (void*)pthread_ldap, NULL ) ) { perror(" Create pthread_ldap ERROR"); } } gdb chasing result: (gdb) 222 rc = ldap_set_option(ld, LDAP_OPT_HOST_NAME, defhost); (gdb) 223 if ( rc != LDAP_SUCCESS ) { (gdb) p ld $6 = (LDAP *) 0x7ffff00008c0 (gdb) pthread_ldap () at OPENLDAP_exam.c8686 186 printf("ldap_init ld = %d\n", ld); (gdb) p ld $7 = (LDAP *) 0xfffffffff00008c0 gcc version: gcc (GCC) 4.4.7 20120313 (Red Hat 4.4.7-11) Copyright (C) 2010 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. OS version: Linux localhost.localdomain 2.6.32-504.el6.x86_64 #1 SMP Wed Oct 15 04:27:16 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux gcc command: gcc OPENLDAP_exam.c -g -o OPENLDAP_exam -L/usr/local/lib -lldap -llber -lpthread

1 0

(ITS#8182) setspec matching fails unexpectedly
by daniel.kauffman＠rocksolidsolutions.org 01 Jul '15

01 Jul '15

Full_Name: Daniel Kauffman Version: 2.4.40 OS: Debian 8.1 URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (76.178.89.137) Issue: Using access control set=<setspec> to compare an attribute value against a string converts the attribute value to lower case but does not convert the string to lower case, so matching sometimes fails unexpectedly. Expected behavior: When an attribute value is compared against a string, matching should use the attribute equality matching rule to determine whether or not to do a case-sensitive match. An exact match would not convert either the attribute value or the string, and a case-insensitive matching rule would convert both the attribute value and the string for comparison. Steps to reproduce: Create a user objectclass with a roleName attribute and set the attribute value to "canBrowse". Note the mixed case. Create an access control statement with mixed case: olcAccess: to * by set="user/roleName & [canBrowse]" read Because the roleName attribute value is converted to lower-case before comparison, the above will always fail, regardless of the case of the roleName attribute value. However, this works, regardless of the case of the roleName attribute value: olcAccess: to * by set="user/roleName & [canbrowse]" read

1 0

Re: (ITS#8048) back-sock/slapo-sock issue
by michael＠stroeder.com 30 Jun '15

30 Jun '15

This is a multi-part message in MIME format. --------------090704060507030702010600 Content-Type: text/plain; charset=ISO-8859-2 Content-Transfer-Encoding: quoted-printable hyc(a)symas.com wrote: > hyc(a)symas.com wrote: >> michael(a)stroeder.com wrote: >=20 >>> Can I raise the debug level? Log level trace does not really show the= ori=3D >>> ginal >>> byte sequence received by the external listener. >> >> Currently there is no debug code for this. >=20 > Actually, if you use debug level SHELL you'll get a plaintext dump of t= he=20 > received text. If you direct this into a file you can examine it with a= hex=20 > editor. I tested this again running as overlay with -d SHELL. See attachment of t= he log excerpt as Python string representation read with open(file,'rb') bef= ore. You can find *exactly* the lines from this response string generated by t= he external listener: 'RESULT\nmsgid: 1\ncode: 49\ninfo: HOTP value wrong\n\n' All lines starting with sock search reading line: (RESULT\n) (msgid: 1\n) (code: 49\n) (info: HOTP value wrong\n) Excerpt of slapd's log repeated here for better readability in the ITS. P= lease note the extra space after "text=3D" which is not what the external liste= ner returned. ------------------------------------------------ 5592d039 sock search reading line (RESULT ) 5592d039 sock search reading line (msgid: 1 ) 5592d039 sock search reading line (code: 49 ) 5592d039 sock search reading line (info: HOTP value wrong ) 5592d039 sock search reading line ( ) 5592d039 str2result (msgid: 1 code: 49 info: HOTP value wrong ) unknown 5592d039 str2result ( ) unknown 5592d039 conn=3D1000 op=3D0 RESULT tag=3D97 err=3D49 text=3D HOTP value w= rong ------------------------------------------------ Ciao, Michael. --------------090704060507030702010600 Content-Type: text/plain; charset=UTF-8; name="string" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="string" NTU5MmQwMzkgY29ubj0xMDAwIGZkPTEyIEFDQ0VQVCBmcm9tIFBBVEg9L29wdC91aS92YXIv b3BlbmxkYXAvcnVuL2xkYXBpLXAgKFBBVEg9L29wdC91aS92YXIvb3BlbmxkYXAvcnVuL2xk YXBpLXApXG41NTkyZDAzOSBjb25uPTEwMDAgb3A9MCBCSU5EIGRuPSJ1aWQ9c2VvZmosY249 dGVzdCxvdT1leGFtcGxlIiBtZXRob2Q9MTI4XG41NTkyZDAzOSBjb25uPTEwMDEgZmQ9MTQg QUNDRVBUIGZyb20gUEFUSD0vb3B0L3VpL3Zhci9vcGVubGRhcC9ydW4vbGRhcGktcCAoUEFU SD0vb3B0L3VpL3Zhci9vcGVubGRhcC9ydW4vbGRhcGktcClcbjU1OTJkMDM5IGNvbm49MTAw MSBvcD0wIEJJTkQgZG49IiIgbWV0aG9kPTE2M1xuNTU5MmQwMzkgY29ubj0xMDAxIG9wPTAg QklORCBhdXRoY2lkPSJnaWROdW1iZXI9MTAwK3VpZE51bWJlcj0xMDAwLGNuPXBlZXJjcmVk LGNuPWV4dGVybmFsLGNuPWF1dGgiIGF1dGh6aWQ9ImdpZE51bWJlcj0xMDArdWlkTnVtYmVy PTEwMDAsY249cGVlcmNyZWQsY249ZXh0ZXJuYWwsY249YXV0aCJcbjU1OTJkMDM5IGNvbm49 MTAwMSBvcD0wIEJJTkQgZG49ImNuPXJvb3Qsb3U9ZXhhbXBsZSIgbWVjaD1FWFRFUk5BTCBz YXNsX3NzZj0wIHNzZj0yNTZcbjU1OTJkMDM5IGNvbm49MTAwMSBvcD0wIFJFU1VMVCB0YWc9 OTcgZXJyPTAgdGV4dD1cbjU1OTJkMDM5IGNvbm49MTAwMSBvcD0xIFNSQ0ggYmFzZT0idWlk PXNlb2ZqLGNuPXRlc3Qsb3U9ZXhhbXBsZSIgc2NvcGU9MCBkZXJlZj0wIGZpbHRlcj0iKCYo b2JqZWN0Q2xhc3M9b2F0aEhPVFBVc2VyKShvYXRoSE9UUENvdW50ZXI9Kikob2F0aFNlY3Jl dD0qKSh8KCEodWlOb3RCZWZvcmU9KikpKHVpTm90QmVmb3JlPD0yMDE1MDYzMDE3MjIwMVop KSh8KCEodWlOb3RBZnRlcj0qKSkodWlOb3RBZnRlcj49MjAxNTA2MzAxNzIyMDFaKSkpIlxu NTU5MmQwMzkgY29ubj0xMDAxIG9wPTEgU1JDSCBhdHRyPW9hdGhIT1RQQ291bnRlciBvYXRo SE9UUFBhcmFtcyBvYXRoU2VjcmV0IG9hdGhUb2tlblNlcmlhbE51bWJlciBvYmplY3RDbGFz cyBwd2RQb2xpY3lTdWJlbnRyeSB1c2VyUGFzc3dvcmRcbjU1OTJkMDM5IGNvbm49MTAwMSBv cD0xIFNFQVJDSCBSRVNVTFQgdGFnPTEwMSBlcnI9MCBuZW50cmllcz0xIHRleHQ9XG41NTky ZDAzOSBjb25uPTEwMDEgb3A9MiBTUkNIIGJhc2U9ImNuPW9hdGgtcG9saWN5LWhvdHAtdXNl cnMsY249ZXhhbXBsZSxvdT1leGFtcGxlIiBzY29wZT0wIGRlcmVmPTAgZmlsdGVyPSIob2Jq ZWN0Q2xhc3M9b2F0aEhPVFBQYXJhbXMpIlxuNTU5MmQwMzkgY29ubj0xMDAxIG9wPTIgU1JD SCBhdHRyPW9hdGhIT1RQQ291bnRlck1heCBvYXRoSE9UUExvb2tBaGVhZCBvYXRoT1RQTGVu Z3RoXG41NTkyZDAzOSBjb25uPTEwMDEgb3A9MiBTRUFSQ0ggUkVTVUxUIHRhZz0xMDEgZXJy PTAgbmVudHJpZXM9MSB0ZXh0PVxuNTU5MmQwMzkgc29jayBzZWFyY2ggcmVhZGluZyBsaW5l IChSRVNVTFRcbilcbjU1OTJkMDM5IHNvY2sgc2VhcmNoIHJlYWRpbmcgbGluZSAobXNnaWQ6 IDFcbilcbjU1OTJkMDM5IHNvY2sgc2VhcmNoIHJlYWRpbmcgbGluZSAoY29kZTogNDlcbilc bjU1OTJkMDM5IHNvY2sgc2VhcmNoIHJlYWRpbmcgbGluZSAoaW5mbzogSE9UUCB2YWx1ZSB3 cm9uZ1xuKVxuNTU5MmQwMzkgc29jayBzZWFyY2ggcmVhZGluZyBsaW5lIChcbilcbjU1OTJk MDM5IHN0cjJyZXN1bHQgKG1zZ2lkOiAxXG5jb2RlOiA0OVxuaW5mbzogSE9UUCB2YWx1ZSB3 cm9uZ1xuXG4pIHVua25vd25cbjU1OTJkMDM5IHN0cjJyZXN1bHQgKFxuKSB1bmtub3duXG41 NTkyZDAzOSBjb25uPTEwMDAgb3A9MCBSRVNVTFQgdGFnPTk3IGVycj00OSB0ZXh0PSBIT1RQ IHZhbHVlIHdyb25nXG41NTkyZDAzOSBjb25uPTEwMDAgb3A9MSBVTkJJTkRcbjU1OTJkMDM5 IGNvbm49MTAwMCBmZD0xMiBjbG9zZWRcbg== --------------090704060507030702010600--

1 0

Re: (ITS#8181) LMDB page leaks etc when treating DBs as data
by h.b.furuseth＠usit.uio.no 30 Jun '15

30 Jun '15

On 30. juni 2015 14:52, hyc(a)symas.com wrote: > We have already documented this. "Database names are kept as keys in the > unnamed database." "Hey, that may mean I can drop a DB without having to open it and mess with LMDB's DBI handling! Let me try this..." > It should be obvious that if you muck with the record of an > existing key, things will change, therefore you should not muck with those keys. Lots of people think differently than you or me. We're not going to agree. Not on this, and not on what you said in your next mail. I don't see the point of rehashing those arguments yet again, and I didn't intend to. I was just ITSing a commit before pushing, _after_ asking you about it. I thought. -- Hallvard

1 0

Re: (ITS#8181) LMDB page leaks etc when treating DBs as data
by hyc＠symas.com 30 Jun '15

30 Jun '15

Hallvard Breien Furuseth wrote: > On 29/06/15 23:05, hyc(a)symas.com wrote: >> Seriously, why aren't we just saying "don't do this" and moving on? > > OK, then document it. Maybe keeping it simple, call > mixing mainDB data and named DBs a user error and warn this > can break the DB. > >> There are >> lots of stupid things you can do with software. It's a waste of time and >> energy to prevent them all. > > We totally disagree, starting with what is stupid. But we knew > that. Ultimately it's redundant work. I.e., every restriction you place inside the code still requires documentation, otherwise all you've done is changed "why doesn't this work" into "why doesn't LMDB let me do what I tried to do?" Simpler to only write the doc and leave the code pristine. The library's purpose is to perform its intended uses efficiently. Misuses are not our responsibility. Preventing misuse is the responsibility of the documentation, it doesn't belong in the code. -- -- 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#8181) LMDB page leaks etc when treating DBs as data
by hyc＠symas.com 30 Jun '15

30 Jun '15

Hallvard Breien Furuseth wrote: > On 29/06/15 23:05, hyc(a)symas.com wrote: >> Seriously, why aren't we just saying "don't do this" and moving on? > > OK, then document it. Maybe keeping it simple, call > mixing mainDB data and named DBs a user error and warn this > can break the DB. We have already documented this. "Database names are kept as keys in the unnamed database." It should be obvious that if you muck with the record of an existing key, things will change, therefore you should not muck with those keys. >> There are >> lots of stupid things you can do with software. It's a waste of time and >> energy to prevent them all. > > We totally disagree, starting with what is stupid. But we knew > that. That's I asked which parts of "mdb/bundle" to push and > which you rejected, we must have misunderstood each other. I > thought I was just ITSing this commit properly before pushing. I just don't see this happening in practice. Most applications will never use subDBs. It's not like some random person is going to come along and open an arbitrary LMDB file created by some other application and start mucking with it, without knowing the meaning of what's inside. Embedded database libraries are used in specific contexts by their enclosing application. They don't just get random ops thrown at them from 3rd party code. The designer of the enclosing app will design a schema/whatever set of tables to use and that scheme will be fixed for the life of the application. -- -- 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#8181) LMDB page leaks etc when treating DBs as data
by h.b.furuseth＠usit.uio.no 30 Jun '15

30 Jun '15

On 29/06/15 23:05, hyc(a)symas.com wrote: > Seriously, why aren't we just saying "don't do this" and moving on? OK, then document it. Maybe keeping it simple, call mixing mainDB data and named DBs a user error and warn this can break the DB. > There are > lots of stupid things you can do with software. It's a waste of time and > energy to prevent them all. We totally disagree, starting with what is stupid. But we knew that. That's I asked which parts of "mdb/bundle" to push and which you rejected, we must have misunderstood each other. I thought I was just ITSing this commit properly before pushing.

1 0

Re: (ITS#8048) back-sock/slapo-sock issue
by hyc＠symas.com 30 Jun '15

30 Jun '15

hyc(a)symas.com wrote: > michael(a)stroeder.com wrote: >> Can I raise the debug level? Log level trace does not really show the ori= >> ginal >> byte sequence received by the external listener. > > Currently there is no debug code for this. Actually, if you use debug level SHELL you'll get a plaintext dump of the received text. If you direct this into a file you can examine it with a hex editor. -- -- 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#8048) back-sock/slapo-sock issue
by hyc＠symas.com 30 Jun '15

30 Jun '15

michael(a)stroeder.com wrote: > Howard Chu wrote: >> michael(a)stroeder.com wrote: >>> michael(a)stroeder.com wrote: >>>> Null-bytes really needed? >>> >>> Hmm, with null-bytes the wrong result code is returned to the LDAP cli= > ent. >>> >>> Without null-bytes the correct result code is returned to the client b= > ut slapd >>> complains about unknown string: >>> >>> 'RESULT\nmsgid: 1\ncode: 49\nmatched: uid=3Dwuqww,cn=3Dampua,ou=3Dampu= > a\ninfo: >>> NOK\n\n' >>> >>> results in log message: >>> >>> 559174df str2result (msgid: 1 >>> code: 0 >>> >>> ) unknown >>> 559174df str2result ( >>> ) unknown >> =20 >> I would almost suspect you were running on Windows. None of the behavio= > r >> you're reporting occurs for me using the searchexample.pl script. > > Your script does not return any real 'RESULT..' responses. Sure it does: print "dn: cn=test, dc=example, dc=com\n"; print "cn: test\n"; print "objectclass: cnobject\n"; print "\n"; print "RESULT\n"; print "code: 0\n"; print "info: answered by process $$\n"; And the result at the client: violino:~/OD/hobj/tests> ../clients/tools/ldapsearch -x -H ldap://:9011 -b dc=example,dc=com # extended LDIF # # LDAPv3 # base <dc=example,dc=com> with scope subtree # filter: (objectclass=*) # requesting: ALL # # test, example.com dn: cn=test,dc=example,dc=com cn: test objectClass: cnobject # search result search: 2 result: 0 Success text: answered by process 3077 # numResponses: 2 # numEntries: 1 Notice there are no embedded NUL characters. Only newlines. > I also have less issues when just returning 'CONTINUE\n'. > >> Sounds like your problem is a python runtime configuration, not a slapd= > >> bug. > > Not on Windows and no run-time configuration involved. > > Look at the raw string representations I've posted. That string goes dire= > ctly > to SocketServer.BaseRequestHandler.request.sendall(response_str). > > Can I raise the debug level? Log level trace does not really show the ori= > ginal > byte sequence received by the external listener. Currently there is no debug code for this. At any rate, the code uses fgets(3) which stops reading at a newline character. The fact that your string isn't being parsed correctly implies either libc fgets is broken inside your slapd process (pretty unlikely) or your socket sender isn't really sending newline characters. -- -- 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#8181) LMDB page leaks etc when treating DBs as data
by hyc＠symas.com 29 Jun '15

29 Jun '15

h.b.furuseth(a)usit.uio.no wrote: > Full_Name: Hallvard B Furuseth > Version: LMDB_0.9.15 > OS: > URL: > Submission from: (NULL) (81.191.45.5) > Submitted by: hallvard > > > The user can overwrite or delete a named DB record > with normal data. This leaks the pages of the DB. > Also the new non-DB can then be treated as a DB. > A fix is coming (from my branch mdb/bundle). Seriously, why aren't we just saying "don't do this" and moving on? There are lots of stupid things you can do with software. It's a waste of time and energy to prevent them all. -- -- 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#8048) back-sock/slapo-sock issue
by michael＠stroeder.com 29 Jun '15

29 Jun '15

Howard Chu wrote: > michael(a)stroeder.com wrote: >> michael(a)stroeder.com wrote: >>> Null-bytes really needed? >> >> Hmm, with null-bytes the wrong result code is returned to the LDAP cli= ent. >> >> Without null-bytes the correct result code is returned to the client b= ut slapd >> complains about unknown string: >> >> 'RESULT\nmsgid: 1\ncode: 49\nmatched: uid=3Dwuqww,cn=3Dampua,ou=3Dampu= a\ninfo: >> NOK\n\n' >> >> results in log message: >> >> 559174df str2result (msgid: 1 >> code: 0 >> >> ) unknown >> 559174df str2result ( >> ) unknown >=20 > I would almost suspect you were running on Windows. None of the behavio= r > you're reporting occurs for me using the searchexample.pl script. Your script does not return any real 'RESULT..' responses. I also have less issues when just returning 'CONTINUE\n'. > Sounds like your problem is a python runtime configuration, not a slapd= > bug. Not on Windows and no run-time configuration involved. Look at the raw string representations I've posted. That string goes dire= ctly to SocketServer.BaseRequestHandler.request.sendall(response_str). Can I raise the debug level? Log level trace does not really show the ori= ginal byte sequence received by the external listener. Ciao, Michael.

1 0

(ITS#8181) LMDB page leaks etc when treating DBs as data
by h.b.furuseth＠usit.uio.no 29 Jun '15

29 Jun '15

Full_Name: Hallvard B Furuseth Version: LMDB_0.9.15 OS: URL: Submission from: (NULL) (81.191.45.5) Submitted by: hallvard The user can overwrite or delete a named DB record with normal data. This leaks the pages of the DB. Also the new non-DB can then be treated as a DB. A fix is coming (from my branch mdb/bundle).

1 0

Re: (ITS#8048) back-sock/slapo-sock issue
by hyc＠symas.com 29 Jun '15

29 Jun '15

michael(a)stroeder.com wrote: > michael(a)stroeder.com wrote: >> Null-bytes really needed? > > Hmm, with null-bytes the wrong result code is returned to the LDAP client. > > Without null-bytes the correct result code is returned to the client but slapd > complains about unknown string: > > 'RESULT\nmsgid: 1\ncode: 49\nmatched: uid=wuqww,cn=ampua,ou=ampua\ninfo: NOK\n\n' > > results in log message: > > 559174df str2result (msgid: 1 > code: 0 > > ) unknown > 559174df str2result ( > ) unknown I would almost suspect you were running on Windows. None of the behavior you're reporting occurs for me using the searchexample.pl script. Sounds like your problem is a python runtime configuration, not a slapd bug. -- -- 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#8048) back-sock/slapo-sock issue
by michael＠stroeder.com 29 Jun '15

29 Jun '15

michael(a)stroeder.com wrote: > Null-bytes really needed? Hmm, with null-bytes the wrong result code is returned to the LDAP client. Without null-bytes the correct result code is returned to the client but slapd complains about unknown string: 'RESULT\nmsgid: 1\ncode: 49\nmatched: uid=wuqww,cn=ampua,ou=ampua\ninfo: NOK\n\n' results in log message: 559174df str2result (msgid: 1 code: 0 ) unknown 559174df str2result ( ) unknown

1 0

Re: (ITS#8048) back-sock/slapo-sock issue
by michael＠stroeder.com 29 Jun '15

29 Jun '15

Michael Str=F6der wrote: > This is my Python response string: >=20 > 'RESULT\nmsgid: 1\ncode: 49\ninfo: remote NOK\n\n' Hmmpf! After adding null-bytes in each line like this 'RESULT\n\x00msgid: 1\n\x00code: 49\n\x00\n\x00' at least this message went away also with RE24: > This leads to slapd debug output: >=20 > 55914b01 str2result (msgid: 1 > code: 49 > info: remote NOK >=20 > ) unknown > 55914b01 str2result ( > ) unknown Null-bytes really needed? str2result() checks for null-bytes in a bunch o= f cases. I really wonder why null-terminated char *s is used. Ciao, Michael.

1 0

Re: (ITS#8048) back-sock/slapo-sock issue
by michael＠stroeder.com 29 Jun '15

29 Jun '15

hyc(a)openldap.org wrote: > Full_Name: Howard Chu > Version: 2.4 > OS:=20 > URL: ftp://ftp.openldap.org/incoming/ > Submission from: (NULL) (110.49.207.42) > Submitted by: hyc >=20 > The result parser is checking for CONTINUE in the wrong place. Please re-open this ticket. RE24 (tagged as 2.4.41) made things worse. Is there a chance to get things fixed? I promise to help testing. First CONTINUE\n works in RE24 better than in 2.4.40 which was the cause = of this ITS. But handling RESULT is seriously broken, even more than in 2.4.40. Example: This is my Python response string: 'RESULT\nmsgid: 1\ncode: 49\ninfo: remote NOK\n\n' This leads to slapd debug output: 55914b01 str2result (msgid: 1 code: 49 info: remote NOK ) unknown 55914b01 str2result ( ) unknown Note that the whole string is returned as being unknown. Also with 2.4.40 my client script receives ' remote NOK' as diagnostic message. With RE24 the diagnostic message is complete garbage. So I tried many response string variants regarding number of \n and leavi= ng away space after the colon etc. But not really working. Sometimes slapd hangs, sometimes my client hangs e.g. when sending two subsequent bind requests in one open LDAP connection.

1 0

(ITS#8180) back-sock should not return sucess in case of error
by michael＠stroeder.com 29 Jun '15

29 Jun '15

Full_Name: Version: HEAD OS: URL: Submission from: (NULL) (84.181.173.53) back-sock should definitely never return success(0) to the client in case the external listener returned non-parseable message: Example trace log: 55913915 => str2entry: "FOOBAR msgid: 1 code: 49 " 55913915 <= str2entry NULL (parse_line) 55913915 str2entry: entry -1 has no dn 55913915 str2entry(FOOBAR) failed 55913915 sock: fgets failed: Success (0)

1 0

(ITS#8179) LMDB: Feature Request: mdb_env_check_mapsize(env)
by scott＠GameRanger.com 28 Jun '15

28 Jun '15

Full_Name: Scott Kevill Version: LMDB 0.9.14 OS: CentOS 5-7 URL: ftp://ftp.openldap.org/incoming/scott-kevill-150628.patch Submission from: (NULL) (60.224.160.178) mdb_txn_begin / mdb_txn_renew will return MDB_MAP_RESIZED for the current process if another process has changed the mapsize AND the data has grown past the current process mapsize. However, by that point, in a multithreaded environment it may be difficult to wind back to a "safe" point of no active txns in order to call mdb_env_set_mapsize(env, 0) to update the mapsize. Requesting: int mdb_env_check_mapsize(MDB_env *env); to return either MDB_SUCCESS or MDB_MAP_RESIZED. This should be lightweight enough to call frequently enough to decide whether to initiate a "safe" point to enable calling mdb_env_set_mapsize(env, 0). Return MDB_SUCCESS if the MDB has not been opened yet. Scenario: - Process W is a writer - Process R is a reader with multiple reader threads (read-only) - Both processes are running and using a 2GB mapsize MDB - Data is currently 1GB - Ops decide W should increase mapsize to 3GB allowing for more expansion - W calls mdb_env_set_mapsize(env, 3GB) - R's mapsize remains at 2GB%0 D Data grows - R:1 thread begins a moderately long read-only txn - Data grows past 2GB - R:2 thread tries to begin a read-only txn, but fails with MDB_MAP_RESIZED - R:2 thread cannot call mdb_env_set_mapsize(env, 0), because of R:1's txn - A major control flow issue exists now, as R:2 may be deep into work, but can't continue nor back out With mdb_env_check_mapsize(), R could periodically test it and if needed, initiate a "safe" point where none of R's threads have active txns. This could be done long before the data size actually reaches R's original mapsize (ie. when data is ~1GB rather >2GB). - Enforcing synchronisation to a "safe" point might be relatively expensive, so it would be important to know if the mapsize has changed first. ie. Making mdb_env_set_mapsize(env, 0) lightweight for the unchanged mapsize case isn't enough I've attached a sample patch against master (scott-kevill-150628.patch). I've tested it against 0.9.14. The code is trivial and is based on the behaviour of mdb_env_set_mapsize(env, 0). I didn't use git for the patch, so not too difficult to get working. Less than 10 new lines, but for the record, I release it to public domain. Feel free to massage it as needed.

1 0

Re: (ITS#7791) 3-Way delta MMR segfault
by quanah＠zimbra.com 27 Jun '15

27 Jun '15

--On Saturday, June 27, 2015 8:01 AM +0000 frederic.nass(a)univ-lorraine.fr wrote: > ------=_Part_4076294_1166621201.1435388481648 > Content-Type: text/plain; charset=utf-8 > Content-Transfer-Encoding: quoted-printable > > Hi,=20 > > We are facing the exact same situation with a 3-way configuration with > open= ldap-2.4.39.2z packaged by Zimbra 8.6 p2.=20 > > Slapd crashes at some point during first replication. We can reproduce > this= on any of the 3 nodes by stopping ldap service, deleting databases > (access= log and mdb) and restarting ldap service.=20 > > Please tell us how we can be helpful.=20 Provide a gdb backtrace. <http://www.openldap.org/faq/data/cache/59.html> --Quanah -- Quanah Gibson-Mount Platform Architect Zimbra, Inc. -------------------- Zimbra :: the leader in open source messaging and collaboration

1 0

(ITS#7791) 3-Way delta MMR segfault
by frederic.nass＠univ-lorraine.fr 27 Jun '15

27 Jun '15

------=_Part_4076294_1166621201.1435388481648 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Hi,=20 We are facing the exact same situation with a 3-way configuration with open= ldap-2.4.39.2z packaged by Zimbra 8.6 p2.=20 Slapd crashes at some point during first replication. We can reproduce this= on any of the 3 nodes by stopping ldap service, deleting databases (access= log and mdb) and restarting ldap service.=20 Please tell us how we can be helpful.=20 Fr=C3=A9d=C3=A9ric Nass=20 Sous-direction Infrastructures=20 Direction du Num=C3=A9rique=20 Universit=C3=A9 de Lorraine=20 ------=_Part_4076294_1166621201.1435388481648 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable <html><body><div style=3D"font-family: arial, helvetica, sans-serif; font-s= ize: 12pt; color: #000000"><div>Hi,</div><div> </di= v><div>We are facing the exact same situation with a 3-way configurati= on with openldap-2.4.39.2z packaged by Zimbra 8.6 p2.</div><div> </= div><div>Slapd crashes at some point during first replication. We can repro= duce this on any of the 3 nodes by stopping ldap service, deleting dat= abases (accesslog and mdb) and restarting ldap service.</div><div> </div= ><div>Please tell us how we can be helpful.</div><div data-marker=3D"__SIG_= PRE__"> Fr=C3=A9d=C3=A9ric Nass Sous-direction Infrastructures <b= r>Direction du Num=C3=A9rique Universit=C3=A9 de Lorraine </div></d= iv></body></html> ------=_Part_4076294_1166621201.1435388481648--

1 0

Re: (ITS#8173)
by hyc＠symas.com 25 Jun '15

25 Jun '15

Adrian.Raemy(a)vtg.admin.ch wrote: > --_000_BE8E19527611BA409D68FF6EA186AF9002A24849BEREXMBX19ifc1i_ > Content-Type: text/plain; charset="us-ascii" > Content-Transfer-Encoding: quoted-printable > > Dear Howard, > > I did a core dump when the crash occurred at slapd respectively when the ba= > ck-ldap crashed. > Maybe the output of the gdb can help you find out where the problem is. > Please let me know what you need more. This trace seems to lack debug symbols. Without source line numbers etc. there's nothing we can determine from this trace. Please read the FAQ. http://www.openldap.org/faq/index.cgi?file=59 The trace shows that you probably have some overlays configured. What overlays? You need to provide your slapd config files if you want any help here. Volunteers aren't going to go out of their way to help you if you aren't going to provide the needed info. > Core was generated by `/usr/lib/openldap/slapd -h ldap://0.0.0.0:389 ldap= > s://0.0.0.0:636 -f /etc/op'. > Program terminated with signal 11, Segmentation fault. > #0 0x00007fc0627492c6 in ldap_back_bind () > (gdb) where > #0 0x00007fc0627492c6 in ldap_back_bind () > #1 0x00007fc062639fcb in fe_op_bind () > #2 0x00007fc0626a86fd in overlay_op_walk () > #3 0x00007fc0626a8956 in over_op_func () > #4 0x00007fc0626a89de in over_op_bind () > #5 0x00007fc062639697 in do_bind () > #6 0x00007fc06260ff19 in connection_operation () > #7 0x00007fc0626104e1 in connection_read_thread () > #8 0x00007fc062145c3c in ldap_int_thread_pool_wrapper () from /usr/lib64/l= > ibldap_r-2.4.so.2 > #9 0x00007fc06155e806 in start_thread () from /lib64/libpthread.so.0 > #10 0x00007fc05fda902d in clone () from /lib64/libc.so.6 > #11 0x0000000000000000 in ?? () > > Core was generated by `/usr/lib/openldap/slapd -h ldap://0.0.0.0:389 ldap= > s://0.0.0.0:636 -f /etc/op'. > Program terminated with signal 11, Segmentation fault. > #0 0x00007fc0627492c6 in ldap_back_bind () > (gdb) where > #0 0x00007fc0627492c6 in ldap_back_bind () > #1 0x00007fc062639fcb in fe_op_bind () > #2 0x00007fc0626a86fd in overlay_op_walk () > #3 0x00007fc0626a8956 in ?? () > #4 0x00007fc0626a89de in ?? () > #5 0x00007fc062639697 in do_bind () > #6 0x00007fc06260ff19 in ?? () > #7 0x00007fc0626104e1 in ?? () > #8 0x00007fc062145c3c in ldap_int_thread_pool_wrapper () from /usr/lib64/l= > ibldap_r-2.4.so.2 > #9 0x00007fc06155e806 in start_thread () from /lib64/libpthread.so.0 > #10 0x00007fc05fda902d in gnu_dev_makedev () from /lib64/libc.so.6 > #11 0x0000000000000000 in ?? () > > Best regards > Adrian -- -- 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#8173)
by Adrian.Raemy＠vtg.admin.ch 24 Jun '15

24 Jun '15

--_000_BE8E19527611BA409D68FF6EA186AF9002A24849BEREXMBX19ifc1i_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Dear Howard, I did a core dump when the crash occurred at slapd respectively when the ba= ck-ldap crashed. Maybe the output of the gdb can help you find out where the problem is. Please let me know what you need more. Core was generated by `/usr/lib/openldap/slapd -h ldap://0.0.0.0:389 ldap= s://0.0.0.0:636 -f /etc/op'. Program terminated with signal 11, Segmentation fault. #0 0x00007fc0627492c6 in ldap_back_bind () (gdb) where #0 0x00007fc0627492c6 in ldap_back_bind () #1 0x00007fc062639fcb in fe_op_bind () #2 0x00007fc0626a86fd in overlay_op_walk () #3 0x00007fc0626a8956 in over_op_func () #4 0x00007fc0626a89de in over_op_bind () #5 0x00007fc062639697 in do_bind () #6 0x00007fc06260ff19 in connection_operation () #7 0x00007fc0626104e1 in connection_read_thread () #8 0x00007fc062145c3c in ldap_int_thread_pool_wrapper () from /usr/lib64/l= ibldap_r-2.4.so.2 #9 0x00007fc06155e806 in start_thread () from /lib64/libpthread.so.0 #10 0x00007fc05fda902d in clone () from /lib64/libc.so.6 #11 0x0000000000000000 in ?? () Core was generated by `/usr/lib/openldap/slapd -h ldap://0.0.0.0:389 ldap= s://0.0.0.0:636 -f /etc/op'. Program terminated with signal 11, Segmentation fault. #0 0x00007fc0627492c6 in ldap_back_bind () (gdb) where #0 0x00007fc0627492c6 in ldap_back_bind () #1 0x00007fc062639fcb in fe_op_bind () #2 0x00007fc0626a86fd in overlay_op_walk () #3 0x00007fc0626a8956 in ?? () #4 0x00007fc0626a89de in ?? () #5 0x00007fc062639697 in do_bind () #6 0x00007fc06260ff19 in ?? () #7 0x00007fc0626104e1 in ?? () #8 0x00007fc062145c3c in ldap_int_thread_pool_wrapper () from /usr/lib64/l= ibldap_r-2.4.so.2 #9 0x00007fc06155e806 in start_thread () from /lib64/libpthread.so.0 #10 0x00007fc05fda902d in gnu_dev_makedev () from /lib64/libc.so.6 #11 0x0000000000000000 in ?? () Best regards Adrian --_000_BE8E19527611BA409D68FF6EA186AF9002A24849BEREXMBX19ifc1i_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable <html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr= osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" = xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:= //www.w3.org/TR/REC-html40"> <head> <meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"= > <meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)"> <style></style> </head> <body lang=3D"DE-CH" link=3D"blue" vlink=3D"purple"> <div class=3D"WordSection1"> Dear Howard,<o:p></o:p> <o:p> </o:p> I did a core dump when the cras= h occurred at slapd respectively when the back-ldap crashed.<o:p></o:p></sp= an> Maybe the output of the gdb can= help you find out where the problem is.<o:p></o:p> Please let me know what you nee= d more.<o:p></o:p> <o:p> </o:p> Core was generated by `/usr/lib= /openldap/slapd -h  ldap://0.0.0.0:389  ldaps://0.0.0.0:636 = -f /etc/op'.<o:p></o:p> Program terminated with signal = 11, Segmentation fault.<o:p></o:p> #0  0x00007fc0627492c6 in = ldap_back_bind ()<o:p></o:p> (gdb) where<o:p></o:p></= p> #0  0x00007fc0627492c6 in = ldap_back_bind ()<o:p></o:p> #1  0x00007fc062639fcb in fe_op_bind ()<o:p></o= :p> #2  0x00007fc0626a86fd in = overlay_op_walk ()<o:p></o:p> #3  0x00007fc0626a8956 in = over_op_func ()<o:p></o:p> #4  0x00007fc0626a89de in = over_op_bind ()<o:p></o:p> #5  0x00007fc062639697 in = do_bind ()<o:p></o:p> #6  0x00007fc06260ff19 in = connection_operation ()<o:p></o:p> #7  0x00007fc0626104e1 in = connection_read_thread ()<o:p></o:p> #8  0x00007fc062145c3c in = ldap_int_thread_pool_wrapper () from /usr/lib64/libldap_r-2.4.so.2<o:p></o:= p> #9  0x00007fc06155e806 in = start_thread () from /lib64/libpthread.so.0<o:p></o:p> #10 0x00007fc05fda902d in clone= () from /lib64/libc.so.6<o:p></o:p> #11 0x0000000000000000 in ?? ()= <o:p></o:p> <o:p> </o:p> Core was generated by `/usr/lib= /openldap/slapd -h  ldap://0.0.0.0:389  ldaps://0.0.0.0:636 = -f /etc/op'.<o:p></o:p> Program terminated with signal = 11, Segmentation fault.<o:p></o:p> #0  0x00007fc0627492c6 in = ldap_back_bind ()<o:p></o:p> (gdb) where<o:p></o:p></= p> #0  0x00007fc0627492c6 in = ldap_back_bind ()<o:p></o:p> #1  0x00007fc062639fcb in fe_op_bind ()<o:p></o= :p> #2  0x00007fc0626a86fd in = overlay_op_walk ()<o:p></o:p> #3  0x00007fc0626a8956 in = ?? ()<o:p></o:p> #4  0x00007fc0626a89de in = ?? ()<o:p></o:p> #5  0x00007fc062639697 in = do_bind ()<o:p></o:p> #6  0x00007fc06260ff19 in = ?? ()<o:p></o:p> #7  0x00007fc0626104e1 in = ?? ()<o:p></o:p> #8  0x00007fc062145c3c in = ldap_int_thread_pool_wrapper () from /usr/lib64/libldap_r-2.4.so.2<o:p></o:= p> #9  0x00007fc06155e806 in = start_thread () from /lib64/libpthread.so.0<o:p></o:p> #10 0x00007fc05fda902d in gnu_d= ev_makedev () from /lib64/libc.so.6<o:p></o:p> #11 0x0000000000000000 in ?? ()= <o:p></o:p> <o:p>&nbs= p;</o:p> Best rega= rds<o:p></o:p> Adrian</s= pan><o:p></o:p> </div> </body> </html> --_000_BE8E19527611BA409D68FF6EA186AF9002A24849BEREXMBX19ifc1i_--

1 0

(ITS#8178) back-sock: Timeout to avoid locking
by michael＠stroeder.com 24 Jun '15

24 Jun '15

Full_Name: Version: HEAD OS: URL: Submission from: (NULL) (2001:8d8:1fe:700::1:3) If a back-sock listener does not correctly respond to a request slapd thread hangs forever and slapd has to be stopped with kill -9. slapd should implement a timeout after which it abandons processing the LDAP request.

1 0

(ITS#8177) RFE: back-sock to receive controls
by michael＠stroeder.com 22 Jun '15

22 Jun '15

Full_Name: Version: HEAD OS: URL: Submission from: (NULL) (84.178.24.72) It would be nice if back-sock would also receive the extended controls sent by the client and could generate response control to be returned to the client.

1 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

openldap-bugs