- openldap-bugs - openldap.org

Re: (ITS#7456) slapo-smbk5pwd: Makefile with -L
by michael＠stroeder.com 02 Dec '12

02 Dec '12

fumiyas(a)osstech.jp wrote: > At Wed, 28 Nov 2012 20:04:41 GMT, > michael(a)stroeder.com wrote: >> I'd like to propose the following patch to Makefile of slapo-smbk5pwd to ease >> building it without installed OpenLDAP client libs: > > This ITS is a dup of #7309. > http://www.openldap.org/its/index.cgi?findid=7309 > > And see also: > http://www.openldap.org/its/index.cgi?findid=7308 > > This problem is fixed in master, but not in 2.4 branch... Ah, thanks for the hint. The Makefile in master looks much better than my suggestion. @Quanah: Could you please port this to RE24 branch? Ciao, Michael.

1 0

Re: (ITS#7457) residentialPerson contains preferredDeliveryMethod twice
by kurt＠OpenLDAP.org 30 Nov '12

30 Nov '12

Per RFC 4519. See list archives for discussion. -- Kurt On Nov 30, 2012, at 10:50 AM, peter(a)adpm.de wrote: > Full_Name: Peter Marschall > Version: 2.4.33 > OS: Linux > URL: ftp://ftp.openldap.org/incoming/ > Submission from: (NULL) (178.2.172.201) > > > Hi, > > trying to convert the residentialPerson objectclass to a format for another > directory server type, I noticed that it contains the attribute > preferredDeliveryMethod twice in its MAY list. > > I do not know if this is an issue, but wanted to report it nonetheless. > > Thanks for OpenLDAP > Peter >

1 0

(ITS#7457) residentialPerson contains preferredDeliveryMethod twice
by peter＠adpm.de 30 Nov '12

30 Nov '12

Full_Name: Peter Marschall Version: 2.4.33 OS: Linux URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (178.2.172.201) Hi, trying to convert the residentialPerson objectclass to a format for another directory server type, I noticed that it contains the attribute preferredDeliveryMethod twice in its MAY list. I do not know if this is an issue, but wanted to report it nonetheless. Thanks for OpenLDAP Peter

1 0

Re: (ITS#7456) slapo-smbk5pwd: Makefile with -L
by fumiyas＠osstech.jp 30 Nov '12

30 Nov '12

Hi, At Wed, 28 Nov 2012 20:04:41 GMT, michael(a)stroeder.com wrote: > I'd like to propose the following patch to Makefile of slapo-smbk5pwd to ease > building it without installed OpenLDAP client libs: This ITS is a dup of #7309. http://www.openldap.org/its/index.cgi?findid=7309 And see also: http://www.openldap.org/its/index.cgi?findid=7308 This problem is fixed in master, but not in 2.4 branch... > diff --git a/contrib/slapd-modules/smbk5pwd/Makefile > b/contrib/slapd-modules/smbk5pwd/Makefile > index 46b340a..01c7bc2 100644 > --- a/contrib/slapd-modules/smbk5pwd/Makefile > +++ b/contrib/slapd-modules/smbk5pwd/Makefile > @@ -26,7 +26,7 @@ INCS=$(LDAP_INC) $(HEIMDAL_INC) $(SSL_INC) > > HEIMDAL_LIB=-L/usr/heimdal/lib -lkrb5 -lkadm5srv > SSL_LIB=-lcrypto > -LDAP_LIB=-lldap_r -llber > +LDAP_LIB=-L../../../libraries/libldap_r/.libs/ -lldap_r -llber > LIBS=$(LDAP_LIB) $(HEIMDAL_LIB) $(SSL_LIB) > > prefix=/usr/local -- -- Name: SATOH Fumiyasu (fumiyas @ osstech co jp) -- Business Home: http://www.OSSTech.co.jp/ -- GitHub Home: https://GitHub.com/fumiyas/

1 0

Re: (ITS#7455) MDB database grows without bound
by hyc＠symas.com 30 Nov '12

30 Nov '12

This is a multi-part message in MIME format. --------------040901020606020603090609 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Howard Chu wrote: > quanah(a)OpenLDAP.org wrote: >> Full_Name: Quanah Gibson-Mount >> Version: 2.4.33 >> OS: Linux 2.6 >> URL: ftp://ftp.openldap.org/incoming/ >> Submission from: (NULL) (74.196.25.250) >> >> >> I have a very small DB (about 25MB from a fresh slapadd). However, the data.mdb >> file grows by about 50MB a day. I.e., the database size on disk *doubles* every >> day. It is now up to 571MB in size after >> >> >> Here is the DB after a fresh slapadd: >> zimbra@zre-ldap002:~/data/ldap/mdb/db$ du -c -h data.mdb >> 25M data.mdb >> >> Here is the DB on the production server: >> [zimbra@ldap01-zcs db]$ du -c -h data.mdb >> 571M data.mdb > > Based on the mdb_stat output you pasted, this is simply a case of overflow > pages not reusing freelist pages. The significant info here is the freelist > info and the number of overflow pages used in the id2e database. Here's the patch we're currently testing for this issue. It appears to work but is maybe not being aggressive enough in reclaiming space. We may want to increase the number of retries a bit more. -- -- Howard Chu CTO, Symas Corp. http://www.symas.com Director, Highland Sun http://highlandsun.com/hyc/ Chief Architect, OpenLDAP http://www.openldap.org/project/ --------------040901020606020603090609 Content-Type: text/plain; charset=UTF-8; name="diff.txt" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="diff.txt" diff --git a/libraries/libmdb/mdb.c b/libraries/libmdb/mdb.c index 251ab6a..117b402 100644 --- a/libraries/libmdb/mdb.c +++ b/libraries/libmdb/mdb.c @@ -1242,6 +1242,7 @@ mdb_page_alloc(MDB_cursor *mc, int num, MDB_page **mp) MDB_page *np; pgno_t pgno = P_INVALID; MDB_ID2 mid; + txnid_t oldest = 0, last; int rc; *mp = NULL; @@ -1254,12 +1255,11 @@ mdb_page_alloc(MDB_cursor *mc, int num, MDB_page **mp) if (!txn->mt_env->me_pghead && txn->mt_dbs[FREE_DBI].md_root != P_INVALID) { /* See if there's anything in the free DB */ - int j; MDB_reader *r; MDB_cursor m2; MDB_node *leaf; MDB_val data; - txnid_t *kptr, last; + txnid_t *kptr; mdb_cursor_init(&m2, txn, FREE_DBI, NULL); if (!txn->mt_env->me_pgfirst) { @@ -1282,15 +1282,21 @@ again: last = *(txnid_t *)key.mv_data; } - /* Unusable if referred by a meta page or reader... */ - j = 1; - if (last < txn->mt_txnid-1) { - j = txn->mt_env->me_txns->mti_numreaders; - r = txn->mt_env->me_txns->mti_readers + j; - for (j = -j; j && (last<r[j].mr_txnid || !r[j].mr_pid); j++) ; + { + unsigned int i, nr; + txnid_t mr; + oldest = txn->mt_txnid - 1; + nr = txn->mt_env->me_txns->mti_numreaders; + r = txn->mt_env->me_txns->mti_readers; + for (i=0; i<nr; i++) { + if (!r[i].mr_pid) continue; + mr = r[i].mr_txnid; + if (mr < oldest) + oldest = mr; + } } - if (!j) { + if (oldest > last) { /* It's usable, grab it. */ MDB_oldpages *mop; @@ -1331,29 +1337,108 @@ none: if (txn->mt_env->me_pghead) { MDB_oldpages *mop = txn->mt_env->me_pghead; if (num > 1) { - /* FIXME: For now, always use fresh pages. We - * really ought to search the free list for a - * contiguous range. - */ - ; + MDB_cursor m2; + int retry = 2, readit = 0, n2 = num-1; + unsigned int i, j, k; + + /* If current list is too short, must fetch more and coalesce */ + if (mop->mo_pages[0] < (unsigned)num) + readit = 1; + + mdb_cursor_init(&m2, txn, FREE_DBI, NULL); + do { + if (readit) { + MDB_val key, data; + MDB_oldpages *mop2; + pgno_t *idl; + int exact; + + last = mop->mo_txnid + 1; + + /* We haven't hit the readers list yet? */ + if (!oldest) { + MDB_reader *r; + unsigned int nr; + txnid_t mr; + + oldest = txn->mt_txnid - 1; + nr = txn->mt_env->me_txns->mti_numreaders; + r = txn->mt_env->me_txns->mti_readers; + for (i=0; i<nr; i++) { + if (!r[i].mr_pid) continue; + mr = r[i].mr_txnid; + if (mr < oldest) + oldest = mr; + } + } + + /* There's nothing we can use on the freelist */ + if (oldest - last < 1) + break; + + exact = 0; + key.mv_data = &last; + key.mv_size = sizeof(last); + rc = mdb_cursor_set(&m2, &key, &data, MDB_SET, &exact); + if (rc) + return rc; + idl = (MDB_ID *) data.mv_data; + mop2 = malloc(sizeof(MDB_oldpages) + MDB_IDL_SIZEOF(idl) - 2*sizeof(pgno_t) + MDB_IDL_SIZEOF(mop->mo_pages)); + if (!mop2) + return ENOMEM; + /* merge in sorted order */ + i = idl[0]; j = mop->mo_pages[0]; mop2->mo_pages[0] = k = i+j; + mop->mo_pages[0] = P_INVALID; + while (i>0 || j>0) { + if (i && idl[i] < mop->mo_pages[j]) + mop2->mo_pages[k--] = idl[i--]; + else + mop2->mo_pages[k--] = mop->mo_pages[j--]; + } + txn->mt_env->me_pglast = last; + mop2->mo_txnid = last; + mop2->mo_next = mop->mo_next; + txn->mt_env->me_pghead = mop2; + free(mop); + mop = mop2; + /* Keep trying to read until we have enough */ + if (mop->mo_pages[0] < (unsigned)num) { + continue; + } + } + + /* current list has enough pages, but are they contiguous? */ + for (i=mop->mo_pages[0]; i>=(unsigned)num; i--) { + if (mop->mo_pages[i-n2] == mop->mo_pages[i] + n2) { + pgno = mop->mo_pages[i]; + i -= n2; + /* move any stragglers down */ + for (j=i+num; j<=mop->mo_pages[0]; j++) + mop->mo_pages[i++] = mop->mo_pages[j]; + mop->mo_pages[0] -= num; + break; + } + } + + /* Stop if we succeeded, or no more retries */ + if (!retry || pgno != P_INVALID) + break; + readit = 1; + retry--; + + } while (1); } else { /* peel pages off tail, so we only have to truncate the list */ pgno = MDB_IDL_LAST(mop->mo_pages); - if (MDB_IDL_IS_RANGE(mop->mo_pages)) { - mop->mo_pages[2]++; - if (mop->mo_pages[2] > mop->mo_pages[1]) - mop->mo_pages[0] = 0; + mop->mo_pages[0]--; + } + if (MDB_IDL_IS_ZERO(mop->mo_pages)) { + txn->mt_env->me_pghead = mop->mo_next; + if (mc->mc_dbi == FREE_DBI) { + mop->mo_next = txn->mt_env->me_pgfree; + txn->mt_env->me_pgfree = mop; } else { - mop->mo_pages[0]--; - } - if (MDB_IDL_IS_ZERO(mop->mo_pages)) { - txn->mt_env->me_pghead = mop->mo_next; - if (mc->mc_dbi == FREE_DBI) { - mop->mo_next = txn->mt_env->me_pgfree; - txn->mt_env->me_pgfree = mop; - } else { - free(mop); - } + free(mop); } } } --------------040901020606020603090609--

1 0

Re: (ITS#7432) slapd crashes when removing members from a large group
by hyc＠symas.com 30 Nov '12

30 Nov '12

hyc(a)symas.com wrote: > marvin.mundry(a)uni-hamburg.de wrote: >> Full_Name: Marvin Mundry >> Version: 2.4.33 >> OS: Ubuntu 12.10 >> URL: https://idmswiki.rrz.uni-hamburg.de:8005/debug.tar.bz >> Submission from: (NULL) (134.100.2.183) >> > > Thanks for the report. The crash has been fixed in git, but your test runs > into another (known) issue in MDB. > > You're working with a very large entry, which libmdb stores in overflow pages. > In the current version of libmdb, freespace management for overflow pages is > not fully implemented, so every time you update the entry libmdb will always > use new pages (instead of reusing old pages). Thus, after a few hundred > operations, your 1GB map will be exhausted. > > It looks like you won't be able to use back-mdb until this feature is fully > implemented in libmdb. The overflow page freespace management issue is being addressed in ITS#7455. A patch is currently being tested. -- -- 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#7444) Check the return value of ldap_pvt_thread_set_concurrency
by hyc＠symas.com 30 Nov '12

30 Nov '12

Tianyin Xu wrote: > > On Sun, Nov 25, 2012 at 7:54 PM, Howard Chu <hyc(a)symas.com > <mailto:hyc@symas.com>> wrote: > > tixu(a)cs.ucsd.edu <mailto:tixu@cs.ucsd.edu> wrote: > > Full_Name: Tianyin Xu > Version: 2.4.33 > OS: Ubuntu 12.04 (actually doesn't matter) > URL: > Submission from: (NULL) (2607:f720:1300:1241:590b:49c:__889f:7b21) > > > Hi, all, > > Still the verbosity idea. In the current version of slapd, when > handling users' > "concurrency" setting, slapd does not check the return value of > "ldap_pvt_thread_set___concurrency" (essentially the return value of > "pthread_setconcurrency") to see whether the setting is successful or not. > > So when the user setting is inappropriate (i.e., too big), slapd says > nothing. > But users have no way to be aware of such configuration failure. I > suggest to > check and notify users in this case. > > > pthread_setconcurrency is a no-op on Linux systems. Even on systems where > this setting might have an effect, it is generally unused. We have more > important things to worry about than this. > > > Yes, I understand that user configuration is never a high-priority issue. > That's why I attached my patch which simply checks the return value, and > prints out a log messge to notify users. The patch itself does not have any > side effect to other part of code. > > I personally think the verbosity idea can improve the system reactions to > users' configurations including this one and its #7443. It is safe (no side > effect) and easy to do (simply adding some log messages), but can greatly > improve the usability and friendlyness to configurations. If you agree, I'm > happy to write patches and corresponding code. We appreciate your desire to help, but as I said before, these two directives are essentially unused in 99.999% of deployments. If you're looking for code to improve, I suggest you review some of the other open reports in the ITS. > > Thanks, > Tianyin > > Here's the patch: > > --- ../openldap-2.4.33/servers/__slapd/bconfig.c 2012-10-10 > 05:18:49.000000000 -0700 > +++ servers/slapd/bconfig.c 2012-11-16 14:52:37.211421828 -0800 > @@ -1530,7 +1530,14 @@ > break; > > case CFG_CONCUR: > - ldap_pvt_thread_set___concurrency(c->value_int); > + > + > if(ldap_pvt_thread_set___concurrency(c->value_int) != 0) > { > + snprintf( c->cr_msg, sizeof( c->cr_msg ), > + "concurrency=%d is not > valid; using > the default setting", > + c->value_int ); > + Debug(LDAP_DEBUG_ANY, "%s: %s.\n", > c->log, > c->cr_msg, 0 ); > + > + } > break; > > case CFG_THREADS: > > > > -- -- 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#7455) MDB database grows without bound
by hyc＠symas.com 28 Nov '12

28 Nov '12

quanah(a)OpenLDAP.org wrote: > Full_Name: Quanah Gibson-Mount > Version: 2.4.33 > OS: Linux 2.6 > URL: ftp://ftp.openldap.org/incoming/ > Submission from: (NULL) (74.196.25.250) > > > I have a very small DB (about 25MB from a fresh slapadd). However, the data.mdb > file grows by about 50MB a day. I.e., the database size on disk *doubles* every > day. It is now up to 571MB in size after > > > Here is the DB after a fresh slapadd: > zimbra@zre-ldap002:~/data/ldap/mdb/db$ du -c -h data.mdb > 25M data.mdb > > Here is the DB on the production server: > [zimbra@ldap01-zcs db]$ du -c -h data.mdb > 571M data.mdb Based on the mdb_stat output you pasted, this is simply a case of overflow pages not reusing freelist pages. The significant info here is the freelist info and the number of overflow pages used in the id2e database. Environment Info Map address: (nil) Map size: 85899345920 Page size: 4096 Max pages: 20971520 Number of pages used: 146230 Last transaction ID: 192037 Max readers: 126 Number of readers used: 10 Freelist Status Tree depth: 3 Branch pages: 7 Leaf pages: 668 Overflow pages: 32 Entries: 10671 Free pages: 141005 Status of Main DB Tree depth: 1 Branch pages: 0 Leaf pages: 1 Overflow pages: 0 Entries: 38 ... Status of ad2i Tree depth: 2 Branch pages: 1 Leaf pages: 20 Overflow pages: 0 Entries: 976 Status of cn Tree depth: 2 Branch pages: 1 Leaf pages: 231 Overflow pages: 0 Entries: 30224 Status of displayName Tree depth: 2 Branch pages: 1 Leaf pages: 91 Overflow pages: 0 Entries: 13625 Status of dn2i Tree depth: 2 Branch pages: 1 Leaf pages: 114 Overflow pages: 0 Entries: 5935 Status of entryCSN Tree depth: 2 Branch pages: 1 Leaf pages: 37 Overflow pages: 0 Entries: 2967 Status of entryUUID Tree depth: 2 Branch pages: 1 Leaf pages: 26 Overflow pages: 0 Entries: 2967 Status of givenName Tree depth: 2 Branch pages: 1 Leaf pages: 24 Overflow pages: 0 Entries: 3318 Status of id2e Tree depth: 3 Branch pages: 7 Leaf pages: 721 Overflow pages: 1937 Entries: 2968 Status of mail Tree depth: 2 Branch pages: 1 Leaf pages: 141 Overflow pages: 0 Entries: 33250 Status of objectClass Tree depth: 2 Branch pages: 1 Leaf pages: 9 Overflow pages: 0 Entries: 9353 Status of sn Tree depth: 2 Branch pages: 1 Leaf pages: 53 Overflow pages: 0 Entries: 7502 Status of uid Tree depth: 2 Branch pages: 1 Leaf pages: 13 Overflow pages: 0 Entries: 3148 ... -- -- 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#7455) MDB database grows without bound
by quanah＠zimbra.com 28 Nov '12

28 Nov '12

--On Wednesday, November 28, 2012 6:50 PM +0000 quanah(a)OpenLDAP.org wrote: > Here is the DB after a fresh slapadd: > zimbra@zre-ldap002:~/data/ldap/mdb/db$ du -c -h data.mdb > 25M data.mdb > > Here is the DB on the production server: > [zimbra@ldap01-zcs db]$ du -c -h data.mdb > 571M data.mdb In 1 week: 24,108 MODs 14 Adds 7 Deletes For a client with a large database of several gigs, this will quickly lead to significant problems, even with a large amount of free disk space. If I have a client with a 12GB DB, then they'll hit their DB maxsize of 80GB in just a few days. --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#7456) slapo-smbk5pwd: Makefile with -L
by michael＠stroeder.com 28 Nov '12

28 Nov '12

Full_Name: Version: HEAD OS: URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (79.227.167.175) I'd like to propose the following patch to Makefile of slapo-smbk5pwd to ease building it without installed OpenLDAP client libs: diff --git a/contrib/slapd-modules/smbk5pwd/Makefile b/contrib/slapd-modules/smbk5pwd/Makefile index 46b340a..01c7bc2 100644 --- a/contrib/slapd-modules/smbk5pwd/Makefile +++ b/contrib/slapd-modules/smbk5pwd/Makefile @@ -26,7 +26,7 @@ INCS=$(LDAP_INC) $(HEIMDAL_INC) $(SSL_INC) HEIMDAL_LIB=-L/usr/heimdal/lib -lkrb5 -lkadm5srv SSL_LIB=-lcrypto -LDAP_LIB=-lldap_r -llber +LDAP_LIB=-L../../../libraries/libldap_r/.libs/ -lldap_r -llber LIBS=$(LDAP_LIB) $(HEIMDAL_LIB) $(SSL_LIB) prefix=/usr/local

1 0

(ITS#7455) MDB database grows without bound
by quanah＠OpenLDAP.org 28 Nov '12

28 Nov '12

Full_Name: Quanah Gibson-Mount Version: 2.4.33 OS: Linux 2.6 URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (74.196.25.250) I have a very small DB (about 25MB from a fresh slapadd). However, the data.mdb file grows by about 50MB a day. I.e., the database size on disk *doubles* every day. It is now up to 571MB in size after Here is the DB after a fresh slapadd: zimbra@zre-ldap002:~/data/ldap/mdb/db$ du -c -h data.mdb 25M data.mdb Here is the DB on the production server: [zimbra@ldap01-zcs db]$ du -c -h data.mdb 571M data.mdb

1 0

(ITS#7454) ldapurl has broken examples
by reed＠reedmedia.net 28 Nov '12

28 Nov '12

Full_Name: Jeremy C. Reed Version: OS: NetBSD URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (173.74.104.132) doc/man/man1/ldapurl.1 examples show ldapuri but the tool is called ldapurl. --- external/bsd/openldap/man/ldapurl.1 2010-12-12 14:20:43.000000000 -0600 +++ /home/reed/J 2012-11-28 10:47:55.000000000 -0600 @@ -130,7 +130,7 @@ The following command: .LP .nf - ldapuri \-h ldap.example.com \-b dc=example,dc=com \-s sub \-f "(cn=Some One)" + ldapurl \-h ldap.example.com \-b dc=example,dc=com \-s sub \-f "(cn=Some One)" .fi .LP returns @@ -142,7 +142,7 @@ The command: .LP .nf - ldapuri \-H ldap://ldap.example.com:389/dc=example,dc=com??sub?(cn=Some%20One) + ldapurl \-H ldap://ldap.example.com:389/dc=example,dc=com??sub?(cn=Some%20One) .fi .LP returns

1 0

Re: (ITS#7451) [PATCH] slapcat: fix segfault when unable to get database first entry
by jvcelak＠redhat.com 28 Nov '12

28 Nov '12

> > Not happening here: > Your patch is invalid, but it appears there was a bug in the underlying > back-ldif code. Still, it did not result in a SEGV. back-ldif is now fixed > in master. e1ccebcf indeed fixes the problem. (I can see the SEGV when started via gdb.) Thanks. Jan

1 0

(ITS#7453) Reset(MDB_NOSYNC/MDB_NOMETASYNC) fails
by h.b.furuseth＠usit.uio.no 27 Nov '12

27 Nov '12

Full_Name: Hallvard B Furuseth Version: 2.4.33 OS: URL: Submission from: (NULL) (193.69.163.163) Submitted by: hallvard mdb_env_open() with MDB_NOSYNC or MDB_NOMETASYNC does not open a sync descriptor, so resetting these flags does not work. Fixing.

1 0

Re: (ITS#7451) [PATCH] slapcat: fix segfault when unable to get database first entry
by hyc＠symas.com 27 Nov '12

27 Nov '12

hyc(a)symas.com wrote: > jvcelak(a)redhat.com wrote: >> Full_Name: Jan Vcelak >> Version: git master >> OS: Linux >> URL: ftp://ftp.openldap.org/incoming/jvcelak-121126-slapcat-fix-segfault-unable-… >> Submission from: (NULL) (209.132.186.34) >> >> >> Tool slapcat segfaults when there is an empty slapd.d config directory and >> 'slapcat -c -H ldap:///cn=config' is invoked. > > Not happening here: Your patch is invalid, but it appears there was a bug in the underlying back-ldif code. Still, it did not result in a SEGV. back-ldif is now fixed in master. > violino:~/OD/hobj/tests> ../servers/slapd/slapd -Tc -H ldap:///cn=config -d -1 > 50b538d7 slapcat init: initiated tool. > 50b538d7 slap_sasl_init: initialized! > 50b538d7 hdb_back_initialize: initialize HDB backend > 50b538d7 hdb_back_initialize: Berkeley DB 5.3.21: (May 11, 2012) > 50b538d7 mdb_back_initialize: initialize MDB backend > 50b538d7 mdb_back_initialize: MDB 0.9.4: (September 14, 2012) > 50b538d7 backend_startup_one: starting "cn=config" > 50b538d7 ldif_read_file: no entry file > "/usr/local/etc/openldap/slapd.d/cn=config.ldif" > 50b538d7 send_ldap_result: conn=-1 op=0 p=0 > 50b538d7 send_ldap_result: err=32 matched="" text="" > 50b538d7 could not stat config file "/usr/local/etc/openldap/slapd.conf": No > such file or directory (2) > slapcat: bad configuration file! > -- -- 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#7451) [PATCH] slapcat: fix segfault when unable to get database first entry
by hyc＠symas.com 27 Nov '12

27 Nov '12

jvcelak(a)redhat.com wrote: > Full_Name: Jan Vcelak > Version: git master > OS: Linux > URL: ftp://ftp.openldap.org/incoming/jvcelak-121126-slapcat-fix-segfault-unable-… > Submission from: (NULL) (209.132.186.34) > > > Tool slapcat segfaults when there is an empty slapd.d config directory and > 'slapcat -c -H ldap:///cn=config' is invoked. Not happening here: violino:~/OD/hobj/tests> ../servers/slapd/slapd -Tc -H ldap:///cn=config -d -1 50b538d7 slapcat init: initiated tool. 50b538d7 slap_sasl_init: initialized! 50b538d7 hdb_back_initialize: initialize HDB backend 50b538d7 hdb_back_initialize: Berkeley DB 5.3.21: (May 11, 2012) 50b538d7 mdb_back_initialize: initialize MDB backend 50b538d7 mdb_back_initialize: MDB 0.9.4: (September 14, 2012) 50b538d7 backend_startup_one: starting "cn=config" 50b538d7 ldif_read_file: no entry file "/usr/local/etc/openldap/slapd.d/cn=config.ldif" 50b538d7 send_ldap_result: conn=-1 op=0 p=0 50b538d7 send_ldap_result: err=32 matched="" text="" 50b538d7 could not stat config file "/usr/local/etc/openldap/slapd.conf": No such file or directory (2) slapcat: bad configuration file! -- -- 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#7448) "assertion failed" in MDB
by artemciy＠gmail.com 27 Nov '12

27 Nov '12

--f46d042f95be98959504cf7fc847 Content-Type: text/plain; charset=ISO-8859-1 On Wed, Nov 28, 2012 at 12:06 AM, Quanah Gibson-Mount <quanah(a)zimbra.com>wrote: > --On Tuesday, November 27, 2012 9:09 AM +0000 artemciy(a)gmail.com wrote: > > http://www.chiark.greenend.**org.uk/~sgtatham/bugs.html<http://www.chiark.greenend.org.uk/~sgtatham/bugs.html> >> > > I would suggest you actually take the time to read what you link to. > Clearly, in this case, you have failed to do that. Yeah, too many letters. --f46d042f95be98959504cf7fc847 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable On Wed, Nov 28, 2012 at 12:06 AM, Quanah Gibson-Mount &lt= ;<a href=3D"mailto:quanah@zimbra.com" target=3D"_blank">quanah(a)zimbra.com</= a>> wrote: <div class=3D"gmail_quote"><blockquote class=3D"gma= il_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-lef= t:1ex"> --On Tuesday, November 27, 2012 9:09 AM +0000 <a href=3D"mailto:artemciy@gm= ail.com" target=3D"_blank">artemciy(a)gmail.com</a> wrote: <blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p= x #ccc solid;padding-left:1ex"> <a href=3D"http://www.chiark.greenend.org.uk/~sgtatham/bugs.html" target=3D= "_blank">http://www.chiark.greenend.org.uk/~sgtatham/bugs.html</a><b= r> </blockquote> I would suggest you actually take the time to read what you link to. Clearl= y, in this case, you have failed to do that.</blockquote><div> </div><di= v>Yeah, too many letters.</div></div> --f46d042f95be98959504cf7fc847--

1 0

Re: (ITS#7448) "assertion failed" in MDB
by quanah＠zimbra.com 27 Nov '12

27 Nov '12

--On Tuesday, November 27, 2012 9:09 AM +0000 artemciy(a)gmail.com wrote: > http://www.chiark.greenend.org.uk/~sgtatham/bugs.html I would suggest you actually take the time to read what you link to. Clearly, in this case, you have failed to do that. For example, under the section: "Show me how to show myself." This is the era of the Internet. This is the era of worldwide communication. This is the era in which I can send my software to somebody in Russia at the touch of a button, and he can send me comments about it just as easily. But if he has a problem with my program, he can't have me standing in front of it while it fails. "Show me" is good when you can, but often you can't. If you have to report a bug to a programmer who can't be present in person, the aim of the exercise is to enable them to reproduce the problem. You want the programmer to run their own copy of the program, do the same things to it, and make it fail in the same way. When they can see the problem happening in front of their eyes, then they can deal with it. So tell them exactly what you did. If it's a graphical program, tell them which buttons you pressed and what order you pressed them in. If it's a program you run by typing a command, show them precisely what command you typed. Wherever possible, you should provide a verbatim transcript of the session, showing what commands you typed and what the computer output in response. Give the programmer all the input you can think of. If the program reads from a file, you will probably need to send a copy of the file. If the program talks to another computer over a network, you probably can't send a copy of that computer, but you can at least say what kind of computer it is, and (if you can) what software is running on it. We're asking you to "Show us" what you did. Provide your code that caused an issue, since mdb is working fine with numerous projects. You are refusing to do provide code that shows what the issue is, and then expecting the developers to magically fix things with no relevant code path to examine. I don't understand your attitude in this at all. --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#7448) "assertion failed" in MDB
by hyc＠symas.com 27 Nov '12

27 Nov '12

Artem Grinblat wrote: > On Tue, Nov 27, 2012 at 1:04 PM, Howard Chu <hyc(a)symas.com > <mailto:hyc@symas.com>> wrote: > > > Indeed, you might stress on http://www.openldap.org/its/__index.cgi > <http://www.openldap.org/its/index.cgi> that bugs > without a test case wouldn't be investigated so that people won't waste > their time. > > > http://www.openldap.org/faq/__data/cache/1122.html > <http://www.openldap.org/faq/data/cache/1122.html> > > > "In case the first aim doesn't succeed, and the programmer /can't/ see it > failing themselves, the second aim of a bug report is to describe what went > wrong. Describe everything in detail. State what you saw, and also state what > you expected to see. Write down the error messages, /especially/ if they have > numbers in". - http://www.chiark.greenend.org.uk/~sgtatham/bugs.html > > Stack trace and proposal to do ltrace is the best detail you've got in a > normal bug report. > Good luck. A complete stack trace is usually sufficient, when we have complete source code in hand. In this case your source code is not present. Ultimately the question is "do you want help to make this work?" Clearly you're not interested in helping. ITS closed. -- -- 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#7448) "assertion failed" in MDB
by artemciy＠gmail.com 27 Nov '12

27 Nov '12

--047d7b2e40c6a4d17e04cf7665de Content-Type: text/plain; charset=ISO-8859-1 On Tue, Nov 27, 2012 at 1:04 PM, Howard Chu <hyc(a)symas.com> wrote: > > Indeed, you might stress on http://www.openldap.org/its/**index.cgi<http://www.openldap.org/its/index.cgi>that bugs >> without a test case wouldn't be investigated so that people won't waste >> their time. >> > > http://www.openldap.org/faq/**data/cache/1122.html<http://www.openldap.org/faq/data/cache/1122.html> "In case the first aim doesn't succeed, and the programmer *can't* see it failing themselves, the second aim of a bug report is to describe what went wrong. Describe everything in detail. State what you saw, and also state what you expected to see. Write down the error messages, *especially* if they have numbers in". - http://www.chiark.greenend.org.uk/~sgtatham/bugs.html Stack trace and proposal to do ltrace is the best detail you've got in a normal bug report. Good luck. --047d7b2e40c6a4d17e04cf7665de Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable On Tue, Nov 27, 2012 at 1:04 PM, Howard Chu <<a href= =3D"mailto:hyc@symas.com" target=3D"_blank">hyc(a)symas.com</a>> wr= ote: <div class=3D"gmail_quote"><blockquote class=3D"gmail_quote" style= =3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> </blockquote><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8= ex;border-left:1px #ccc solid;padding-left:1ex"><blockquote class=3D"gmail_= quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1= ex"> <div class=3D"im">Indeed, you might stress on <a href=3D"http://www.openlda= p.org/its/index.cgi" target=3D"_blank">http://www.openldap.org/its/i= ndex.cgi</a> that bugs without a test case wouldn't be investigated so that people won't w= aste their time. </div></blockquote> <a href=3D"http://www.openldap.org/faq/data/cache/1122.html" target=3D"_bla= nk">http://www.openldap.org/faq/data/cache/1122.html</a></blockquote= ><div> </div><div>"In case the first aim doesn't succeed, and the p= rogrammer=A0can't=A0see it failing themselves, the second aim of a bu= g report is to describe what went wrong. Describe everything in detail. Sta= te what you saw, and also state what you expected to see. Write down the er= ror messages,=A0especially=A0if they have numbers in". -=A0<f= ont face=3D"Times New Roman" size=3D"3"><a href=3D"http://www.chiark.greene= nd.org.uk/~sgtatham/bugs.html">http://www.chiark.greenend.org.uk/~sgtatham/= bugs.html</a></div> <div> </div><div>Stack trace a= nd proposal to do ltrace is the best detail you've got in a normal bug = report.</div><div>Good luc= k.</div> </div> --047d7b2e40c6a4d17e04cf7665de--

1 0

Re: (ITS#7448) "assertion failed" in MDB
by hyc＠symas.com 27 Nov '12

27 Nov '12

artemciy(a)gmail.com wrote: > --f46d042fddcee1dc8704cf74ca2b > Content-Type: text/plain; charset=ISO-8859-1 > > On Tue, Nov 27, 2012 at 1:54 AM, Quanah Gibson-Mount <quanah(a)zimbra.com>wrote: > >> You can close the issue then, because I won't be producing one. >>> >> >> I don't understand why you would take the time to report a bug, but then >> refuse to provide the information necessary to fix it. > > > Indeed, you might stress on http://www.openldap.org/its/index.cgi that bugs > without a test case wouldn't be investigated so that people won't waste > their time. http://www.openldap.org/faq/data/cache/1122.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

Re: (ITS#7448) "assertion failed" in MDB
by artemciy＠gmail.com 26 Nov '12

26 Nov '12

--f46d042fddcee1dc8704cf74ca2b Content-Type: text/plain; charset=ISO-8859-1 On Tue, Nov 27, 2012 at 1:54 AM, Quanah Gibson-Mount <quanah(a)zimbra.com>wrote: > You can close the issue then, because I won't be producing one. >> > > I don't understand why you would take the time to report a bug, but then > refuse to provide the information necessary to fix it. Indeed, you might stress on http://www.openldap.org/its/index.cgi that bugs without a test case wouldn't be investigated so that people won't waste their time. That is not particularly helpful. :/ > > --Quanah > --f46d042fddcee1dc8704cf74ca2b Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable On Tue, Nov 27, 2012 at 1:54 AM, Quanah Gibson-Mount <= <a href=3D"mailto:quanah@zimbra.com" target=3D"_blank">quanah(a)zimbra.com</a= >> wrote:=A0<div class=3D"gmail_quote"><blockquote class=3D"gmail= _quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:= 1ex"> <blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p= x #ccc solid;padding-left:1ex"><div class=3D"im">You can close the issue th= en, because I won't be producing one. </div></blockquote> I don't understand why you would take the time to report a bug, but the= n refuse to provide the information necessary to fix it.</blockquote><div><= br></div><div>Indeed, you might stress on=A0<a href=3D"http://www.openldap.= org/its/index.cgi">http://www.openldap.org/its/index.cgi</a> that bugs with= out a test case wouldn't be investigated so that people won't waste= their time.</div> <div> </div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex= ;border-left:1px #ccc solid;padding-left:1ex"> =A0That is not particularly = helpful. :/ --Quanah </blockquote><div> </div></div> --f46d042fddcee1dc8704cf74ca2b--

1 0

(ITS#7452) back-mdb envflags bug
by hyc＠OpenLDAP.org 26 Nov '12

26 Nov '12

Full_Name: Howard Chu Version: 2.4.33 OS: URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (37.19.96.255) Submitted by: hyc In mdb_cf_gen, setting flags using the envflags keyword sets the wrong flags. Will be fixed shortly.

1 0

Re: (ITS#7448) "assertion failed" in MDB
by artemciy＠gmail.com 26 Nov '12

26 Nov '12

--047d7b10cce9fad8bc04cf6e2a0a Content-Type: text/plain; charset=ISO-8859-1 On Tue, Nov 27, 2012 at 3:16 AM, Howard Chu <hyc(a)symas.com> wrote: > Quanah, from past experience I know that making a test case is a research >> endeavor that can be quite costly. IMO, refusing to investigate a bug >> without a test case is not a sane support politics. >> > > Chasing "bugs" in 3rd party code that you haven't shared with us is not a > sane policy. If we can't see the code, we certainly can't identify the root > cause of the issue. Given that our library is working in our primary > application (slapd) as well as multiple other projects, the burden of proof > is on you to demonstrate that the bug is not caused by your C++ application. If you think it is acceptable for your library to die with "assert" because of a 3rd party code then I have no further questions about the "reliability" of your software. --047d7b10cce9fad8bc04cf6e2a0a Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable On Tue, Nov 27, 2012 at 3:16 AM, Howard Chu <<a href= =3D"mailto:hyc@symas.com" target=3D"_blank">hyc(a)symas.com</a>> wr= ote: <div class=3D"gmail_quote"><blockquote class=3D"gmail_quote" style= =3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> <blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p= x #ccc solid;padding-left:1ex"><div class=3D"im">Quanah, from past experien= ce I know that making a test case is a research endeavor that can be quite costly. IMO, refusing to investigate a bug without a test case is not a sane support politics. </div></blockquote> Chasing "bugs" in 3rd party code that you haven't shared with= us is not a sane policy. If we can't see the code, we certainly can&#3= 9;t identify the root cause of the issue. Given that our library is working= in our primary application (slapd) as well as multiple other projects, the= burden of proof is on you to demonstrate that the bug is not caused by you= r C++ application.</blockquote> <div> </div><div>If you think it is acceptable for your library to die w= ith "assert" because of a 3rd party code then I have no further q= uestions about the "reliability" of your software.</div></div> --047d7b10cce9fad8bc04cf6e2a0a--

1 0

Re: (ITS#7448) "assertion failed" in MDB
by hyc＠symas.com 26 Nov '12

26 Nov '12

artemciy(a)gmail.com wrote: > --e89a8f3b55c652009c04cf6d24b9 > Content-Type: text/plain; charset=ISO-8859-1 > > On Tue, Nov 27, 2012 at 1:54 AM, Quanah Gibson-Mount <quanah(a)zimbra.com>wrote: > >> You can close the issue then, because I won't be producing one. >>> >> >> I don't understand why you would take the time to report a bug, but then >> refuse to provide the information necessary to fix it. That is not >> particularly helpful. :/ >> >> --Quanah >> > > Quanah, from past experience I know that making a test case is a research > endeavor that can be quite costly. IMO, refusing to investigate a bug > without a test case is not a sane support politics. Chasing "bugs" in 3rd party code that you haven't shared with us is not a sane policy. If we can't see the code, we certainly can't identify the root cause of the issue. Given that our library is working in our primary application (slapd) as well as multiple other projects, the burden of proof is on you to demonstrate that the bug is not caused by your C++ application. > For now I have found switching to Leveldb easier than taking another > library for maintance (e.g. http://lambda-the-ultimate.org/node/4636 -> > http://akkartik.name/blog/libraries). > BTW, here is an example of good support: > http://tracker.newdream.net/issues/3495 -- -- 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#7448) "assertion failed" in MDB
by artemciy＠gmail.com 26 Nov '12

26 Nov '12

--e89a8f3b55c652009c04cf6d24b9 Content-Type: text/plain; charset=ISO-8859-1 On Tue, Nov 27, 2012 at 1:54 AM, Quanah Gibson-Mount <quanah(a)zimbra.com>wrote: > You can close the issue then, because I won't be producing one. >> > > I don't understand why you would take the time to report a bug, but then > refuse to provide the information necessary to fix it. That is not > particularly helpful. :/ > > --Quanah > Quanah, from past experience I know that making a test case is a research endeavor that can be quite costly. IMO, refusing to investigate a bug without a test case is not a sane support politics. For now I have found switching to Leveldb easier than taking another library for maintance (e.g. http://lambda-the-ultimate.org/node/4636 -> http://akkartik.name/blog/libraries). BTW, here is an example of good support: http://tracker.newdream.net/issues/3495 --e89a8f3b55c652009c04cf6d24b9 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable On Tue, Nov 27, 2012 at 1:54 AM, Quanah Gibson-Mount <= <a href=3D"mailto:quanah@zimbra.com" target=3D"_blank">quanah(a)zimbra.com</a= >> wrote: <div class=3D"gmail_quote"><blockquote class=3D"gmai= l_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left= :1ex"> <blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p= x #ccc solid;padding-left:1ex"><div class=3D"im">You can close the issue th= en, because I won't be producing one. </div></blockquote> I don't understand why you would take the time to report a bug, but the= n refuse to provide the information necessary to fix it. =A0That is not par= ticularly helpful. :/ --Quanah </blockquote><div> </div><div>Quanah, from past experience I= know that making a test case is a research endeavor that can be quite cost= ly. IMO, refusing to investigate a bug without a test case is not a sane su= pport politics.</div> <div>For now I have found switching to Leveldb easier than taking another l= ibrary for maintance (e.g. <a href=3D"http://lambda-the-ultimate.org/node/4= 636">http://lambda-the-ultimate.org/node/4636</a> -> <a href=3D"http://a= kkartik.name/blog/libraries">http://akkartik.name/blog/libraries</a>).</div= > <div>BTW, here is an example of good support:=A0<a href=3D"http://tracker.n= ewdream.net/issues/3495">http://tracker.newdream.net/issues/3495</a></div><= /div> --e89a8f3b55c652009c04cf6d24b9--

1 0

Re: (ITS#7448) "assertion failed" in MDB
by quanah＠zimbra.com 26 Nov '12

26 Nov '12

--On Monday, November 26, 2012 12:01 PM +0000 artemciy(a)gmail.com wrote: > --047d7b339025cf973e04cf64ae11 > Content-Type: text/plain; charset=ISO-8859-1 > > On Mon, Nov 26, 2012 at 4:55 AM, Howard Chu <hyc(a)symas.com> wrote: > >> We will investigate this when a reproducible test case is available. >> > > You can close the issue then, because I won't be producing one. I don't understand why you would take the time to report a bug, but then refuse to provide the information necessary to fix it. That is not particularly helpful. :/ --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#7451) [PATCH] slapcat: fix segfault when unable to get database first entry
by jvcelak＠redhat.com 26 Nov '12

26 Nov '12

Full_Name: Jan Vcelak Version: git master OS: Linux URL: ftp://ftp.openldap.org/incoming/jvcelak-121126-slapcat-fix-segfault-unable-… Submission from: (NULL) (209.132.186.34) Tool slapcat segfaults when there is an empty slapd.d config directory and 'slapcat -c -H ldap:///cn=config' is invoked. # gdb --args ./servers/slapd/slapcat -c -H 'ldap:///cn=config' ... (gdb) r ... [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib64/libthread_db.so.1". # no data for entry id=00000000 Program received signal SIGSEGV, Segmentation fault. 0x000000000052d761 in ldif_tool_entry_next (be=0x8ac250) at ../../../../servers/slapd/back-ldif/ldif.c:1743 1743 Entry *e = tl->entries[ tl->ecurrent ]; (gdb) bt full #0 0x000000000052d761 in ldif_tool_entry_next (be=0x8ac250) at ../../../../servers/slapd/back-ldif/ldif.c:1743 e = 0x8ac250 tl = 0x989560 #1 0x000000000043c83d in config_tool_entry_next (be=0x9892d0) at ../../../servers/slapd/bconfig.c:7254 cfb = 0x8ac240 bi = 0x8a3dc0 #2 0x00000000004f0dac in slapcat (argc=4, argv=0x7fffffffdfe8) at ../../../servers/slapd/slapcat.c:99 id = 0 rc = 1 op = {o_hdr = 0x0, o_tag = 0, o_time = 0, o_tincr = 0, o_bd = 0x9892d0, o_req_dn = {bv_len = 0, bv_val = 0x0}, o_req_ndn = {bv_len = 0, bv_val = 0x0}, o_request = {oq_add = {rs_modlist = 0x0, rs_e = 0x0}, oq_bind = {rb_method = 0, rb_cred = {bv_len = 0, bv_val = 0x0}, rb_edn = {bv_len = 0, bv_val = 0x0}, rb_ssf = 0, rb_mech = {bv_len = 0, bv_val = 0x0}}, oq_compare = {rs_ava = 0x0}, oq_modify = {rs_mods = {rs_modlist = 0x0, rs_no_opattrs = 0 '\000'}, rs_increment = 0}, oq_modrdn = {rs_mods = { rs_modlist = 0x0, rs_no_opattrs = 0 '\000'}, rs_deleteoldrdn = 0, rs_newrdn = {bv_len = 0, bv_val = 0x0}, rs_nnewrdn = {bv_len = 0, bv_val = 0x0}, rs_newSup = 0x0, rs_nnewSup = 0x0}, oq_search = {rs_scope = 0, rs_deref = 0, rs_slimit = 0, rs_tlimit = 0, rs_limit = 0x0, rs_attrsonly = 0, rs_attrs = 0x0, rs_filter = 0x0, rs_filterstr = {bv_len = 0, bv_val = 0x0}}, oq_abandon = {rs_msgid = 0}, oq_cancel = {rs_msgid = 0}, oq_extended = {rs_reqoid = {bv_len = 0, bv_val = 0x0}, rs_flags = 0, rs_reqdata = 0x0}, oq_pwdexop = {rs_extended = {rs_reqoid = {bv_len = 0, bv_val = 0x0}, rs_flags = 0, rs_reqdata = 0x0}, rs_old = {bv_len = 0, bv_val = 0x0}, rs_new = {bv_len = 0, bv_val = 0x0}, rs_mods = 0x0, rs_modtail = 0x0}}, o_abandon = 0, o_cancel = 0, o_groups = 0x0, o_do_not_cache = 0 '\000', o_is_auth_check = 0 '\000', o_dont_replicate = 0 '\000', o_acl_priv = ACL_NONE, o_nocaching = 0 '\000', o_delete_glue_parent = 0 '\000', o_no_schema_check = 0 '\000', o_no_subordinate_glue = 0 '\000', o_ctrlflag = '\000' <repeats 31 times>, o_controls = 0x0, o_authz = {sai_method = 0, sai_mech = {bv_len = 0, bv_val = 0x0}, sai_dn = {bv_len = 0, bv_val = 0x0}, sai_ndn = {bv_len = 0, bv_val = 0x0}, sai_ssf = 0, sai_transport_ssf = 0, sai_tls_ssf = 0, sai_sasl_ssf = 0}, o_ber = 0x0, o_res_ber = 0x0, o_callback = 0x0, o_ctrls = 0x0, o_csn = {bv_len = 0, bv_val = 0x0}, o_private = 0x0, o_extra = {slh_first = 0x0}, o_next = {stqe_next = 0x0}} progname = 0x62e5d8 "slapcat" requestBSF = 1 doBSF = 0 __PRETTY_FUNCTION__ = "slapcat" #3 0x0000000000424581 in main (argc=4, argv=0x7fffffffdfe8) at ../../../servers/slapd/main.c:411 i = 1 no_detach = 0 rc = 1 urls = 0x0 username = 0x0 groupname = 0x0 sandbox = 0x0 syslogUser = 160 pid = 0 waitfds = {-8560, 32767} g_argc = 4 g_argv = 0x7fffffffdfe8 configfile = 0x0 configdir = 0x0 serverName = 0x7fffffffe265 "slapcat" serverMode = 1 scp = 0x0 scp_entry = 0x0 debug_unknowns = 0x0 syslog_unknowns = 0x0 serverNamePrefix = 0x60c858 "" l = 1 slapd_pid_file_unlink = 0 slapd_args_file_unlink = 0 firstopt = 1 __PRETTY_FUNCTION__ = "main" The attached file is derived from OpenLDAP Software. All of the modifications to OpenLDAP Software represented in the following patch(es) were developed by Red Hat. Red Hat has not assigned rights and/or interest in this work to any party. I, Jan Vcelak am authorized by Red Hat, my employer, to release this work under the following terms. Red Hat hereby place the following modifications to OpenLDAP Software (and only these modifications) into the public domain. Hence, these modifications may be freely used and/or redistributed for any purpose with or without attribution and/or other notice.

1 0

Re: (ITS#7448) "assertion failed" in MDB
by artemciy＠gmail.com 26 Nov '12

26 Nov '12

--047d7b339025cf973e04cf64ae11 Content-Type: text/plain; charset=ISO-8859-1 On Mon, Nov 26, 2012 at 4:55 AM, Howard Chu <hyc(a)symas.com> wrote: > We will investigate this when a reproducible test case is available. > You can close the issue then, because I won't be producing one. --047d7b339025cf973e04cf64ae11 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable <div class=3D"gmail_quote">On Mon, Nov 26, 2012 at 4:55 AM, Howard Chu <spa= n dir=3D"ltr"><<a href=3D"mailto:hyc@symas.com" target=3D"_blank">hyc@sy= mas.com</a>> wrote: <blockquote class=3D"gmail_quote" style=3D= "margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> We will investigate this when a reproducible test case is available. </blockquote> = </div>You can close the issue then, because I won't be producing one.<b= r> --047d7b339025cf973e04cf64ae11--

1 0

Re: (ITS#7444) Check the return value of ldap_pvt_thread_set_concurrency
by tixu＠cs.ucsd.edu 26 Nov '12

26 Nov '12

--f46d04428c6e0fb88b04cf62891a Content-Type: text/plain; charset=ISO-8859-1 On Sun, Nov 25, 2012 at 7:54 PM, Howard Chu <hyc(a)symas.com> wrote: > tixu(a)cs.ucsd.edu wrote: > >> Full_Name: Tianyin Xu >> Version: 2.4.33 >> OS: Ubuntu 12.04 (actually doesn't matter) >> URL: >> Submission from: (NULL) (2607:f720:1300:1241:590b:49c:**889f:7b21) >> >> >> Hi, all, >> >> Still the verbosity idea. In the current version of slapd, when handling >> users' >> "concurrency" setting, slapd does not check the return value of >> "ldap_pvt_thread_set_**concurrency" (essentially the return value of >> "pthread_setconcurrency") to see whether the setting is successful or not. >> >> So when the user setting is inappropriate (i.e., too big), slapd says >> nothing. >> But users have no way to be aware of such configuration failure. I >> suggest to >> check and notify users in this case. >> > > pthread_setconcurrency is a no-op on Linux systems. Even on systems where > this setting might have an effect, it is generally unused. We have more > important things to worry about than this. > > Yes, I understand that user configuration is never a high-priority issue. That's why I attached my patch which simply checks the return value, and prints out a log messge to notify users. The patch itself does not have any side effect to other part of code. I personally think the verbosity idea can improve the system reactions to users' configurations including this one and its #7443. It is safe (no side effect) and easy to do (simply adding some log messages), but can greatly improve the usability and friendlyness to configurations. If you agree, I'm happy to write patches and corresponding code. Thanks, Tianyin > Here's the patch: >> >> --- ../openldap-2.4.33/servers/**slapd/bconfig.c 2012-10-10 >> 05:18:49.000000000 -0700 >> +++ servers/slapd/bconfig.c 2012-11-16 14:52:37.211421828 -0800 >> @@ -1530,7 +1530,14 @@ >> break; >> >> case CFG_CONCUR: >> - ldap_pvt_thread_set_**concurrency(c->value_int); >> + >> + if(ldap_pvt_thread_set_**concurrency(c->value_int) >> != 0) >> { >> + snprintf( c->cr_msg, sizeof( c->cr_msg ), >> + "concurrency=%d is not valid; >> using >> the default setting", >> + c->value_int ); >> + Debug(LDAP_DEBUG_ANY, "%s: %s.\n", >> c->log, >> c->cr_msg, 0 ); >> + >> + } >> break; >> >> case CFG_THREADS: >> >> >> >> > > -- > -- Howard Chu > CTO, Symas Corp. http://www.symas.com > Director, Highland Sun http://highlandsun.com/hyc/ > Chief Architect, OpenLDAP http://www.openldap.org/**project/<http://www.openldap.org/project/> > -- Tianyin XU, http://cseweb.ucsd.edu/~tixu/ --f46d04428c6e0fb88b04cf62891a Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable <div class=3D"gmail_extra"> <div class=3D"gmail_quote">On Sun, Nov 25, 2= 012 at 7:54 PM, Howard Chu <<a href=3D"mailto:hyc@syma= s.com" target=3D"_blank">hyc(a)symas.com</a>> wrote: <blockquote= class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc soli= d;padding-left:1ex"> <div class=3D"im"><a href=3D"mailto:tixu@cs.ucsd.edu" target=3D"_blank">tix= u(a)cs.ucsd.edu</a> wrote: <blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p= x #ccc solid;padding-left:1ex"> Full_Name: Tianyin Xu Version: 2.4.33 OS: Ubuntu 12.04 (actually doesn't matter) URL: Submission from: (NULL) (2607:f720:1300:1241:590b:49c:889f:7b21) Hi, all, Still the verbosity idea. In the current version of slapd, when handling us= ers' "concurrency" setting, slapd does not check the return value of<b= r> "ldap_pvt_thread_set_concurrency" (essentially the return = value of "pthread_setconcurrency") to see whether the setting is successfu= l or not. So when the user setting is inappropriate (i.e., too big), slapd says nothi= ng. But users have no way to be aware of such configuration failure. I suggest = to check and notify users in this case. </blockquote> </div> pthread_setconcurrency is a no-op on Linux systems. Even on systems where t= his setting might have an effect, it is generally unused. We have more impo= rtant things to worry about than this.<div class=3D"HOEnZb"><div> </div> </div></blockquote><div> Yes, I understand that user configuration is ne= ver a high-priority issue. That's why I attached my patch which simply = checks the return value, and prints out a log messge to notify users. The p= atch itself does not have any side effect to other part of code. I personally think the verbosity idea can improve the system reactions = to users' configurations including this one and its #7443. It is safe (= no side effect) and easy to do (simply adding some log messages), but can g= reatly improve the usability and friendlyness to configurations. If you agr= ee, I'm happy to write patches and corresponding code. Thanks, Tianyin =A0</div><blockquote class=3D"gmail_quote" st= yle=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div = class=3D"HOEnZb"><div class=3D"h5"> <blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p= x #ccc solid;padding-left:1ex"> Here's the patch: --- ../openldap-2.4.33/servers/slapd/bconfig.c =A0 =A0 =A02012-10-10= 05:18:49.000000000 -0700 +++ servers/slapd/bconfig.c =A0 =A0 2012-11-16 14:52:37.211421828 -0800 @@ -1530,7 +1530,14 @@ =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0break; =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0case CFG_CONCUR: - =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 ldap_pvt_thread_set_co= ncurrency(c->value_int); + + =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0if(ldap_pvt_thread_set_= concurrency(c->value_int) !=3D 0) { + =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 snprintf( c-&= gt;cr_msg, sizeof( c->cr_msg ), + =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 "concurrency=3D%d is not valid; using the default setting", + =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 c->value_int ); + =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0Debug(LDAP= _DEBUG_ANY, "%s: %s.\n", c->log, c->cr_msg, 0 ); + + =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 } =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0break; =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0case CFG_THREADS: </blockquote> </div></div> -- =A0 -- Howard Chu =A0 CTO, Symas Corp. =A0 =A0 =A0 =A0 =A0 <a href=3D"http://www.symas.com" t= arget=3D"_blank">http://www.symas.com</a> =A0 Director, Highland Sun =A0 =A0 <a href=3D"http://highlandsun.com/hyc/" = target=3D"_blank">http://highlandsun.com/hyc/</a> =A0 Chief Architect, OpenLDAP =A0<a href=3D"http://www.openldap.org/project= /" target=3D"_blank">http://www.openldap.org/project/</a> </blockquote></div> -- <span sty= le=3D"border-collapse:separate;color:rgb(0,0,0);font-family:'Times New = Roman';font-style:normal;font-variant:normal;font-weight:normal;letter-= spacing:normal;line-height:normal;text-align:-webkit-auto;text-indent:0px;t= ext-transform:none;white-space:normal;word-spacing:0px;font-size:medium"><s= pan style=3D"color:rgb(102,102,102);font-family:arial;font-size:small">Tian= yin XU, <a href=3D"http://cseweb.ucsd.edu/%7Etixu/" target=3D"_blank">http://cseweb= .ucsd.edu/~tixu/</a> </div> --f46d04428c6e0fb88b04cf62891a--

1 0

Re: (ITS#7450) segfault with listener-threads=8
by jackie.qq.zhang＠gmail.com 25 Nov '12

25 Nov '12

Hi, Howard, Thanks for the explanation. Yes, it seems that I was confused by the numbers. I cannot reproduce the case when setting listener-thread as 8. It's possible that I confused myself by setting the number many times. I thought the number is to specify the listening threads but it seems my understanding was wrong. Best regards, Jackie On Sun, Nov 25, 2012 at 7:40 PM, Howard Chu <hyc(a)symas.com> wrote: > jackie.qq.zhang(a)gmail.com wrote: >> >> Hi, Howard, >> >> GDB did stop at the statement: >> **assert( SLAP_SOCK_NOT_ACTIVE(id, s) );** >> >> But the system output is >> **Segmentation fault (core dumped)** >> >> It seems not related to whether it's a power of 2 or not, because even >> I specify it as 64, i.e., 2^6, the result and error message are still >> the same. > > > That's to be expected since currently this setting has a hard-coded maximum > of 16. Unless you have a machine with more than 1024 cores, I don't think > your setting is valid. > > So again, this bug report is invalid. > > -- > -- 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#7444) Check the return value of ldap_pvt_thread_set_concurrency
by hyc＠symas.com 25 Nov '12

25 Nov '12

tixu(a)cs.ucsd.edu wrote: > Full_Name: Tianyin Xu > Version: 2.4.33 > OS: Ubuntu 12.04 (actually doesn't matter) > URL: > Submission from: (NULL) (2607:f720:1300:1241:590b:49c:889f:7b21) > > > Hi, all, > > Still the verbosity idea. In the current version of slapd, when handling users' > "concurrency" setting, slapd does not check the return value of > "ldap_pvt_thread_set_concurrency" (essentially the return value of > "pthread_setconcurrency") to see whether the setting is successful or not. > > So when the user setting is inappropriate (i.e., too big), slapd says nothing. > But users have no way to be aware of such configuration failure. I suggest to > check and notify users in this case. pthread_setconcurrency is a no-op on Linux systems. Even on systems where this setting might have an effect, it is generally unused. We have more important things to worry about than this. > Here's the patch: > > --- ../openldap-2.4.33/servers/slapd/bconfig.c 2012-10-10 > 05:18:49.000000000 -0700 > +++ servers/slapd/bconfig.c 2012-11-16 14:52:37.211421828 -0800 > @@ -1530,7 +1530,14 @@ > break; > > case CFG_CONCUR: > - ldap_pvt_thread_set_concurrency(c->value_int); > + > + if(ldap_pvt_thread_set_concurrency(c->value_int) != 0) > { > + snprintf( c->cr_msg, sizeof( c->cr_msg ), > + "concurrency=%d is not valid; using > the default setting", > + c->value_int ); > + Debug(LDAP_DEBUG_ANY, "%s: %s.\n", c->log, > c->cr_msg, 0 ); > + > + } > break; > > case CFG_THREADS: > > > -- -- 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#7450) segfault with listener-threads=8
by hyc＠symas.com 25 Nov '12

25 Nov '12

jackie.qq.zhang(a)gmail.com wrote: > Hi, Howard, > > GDB did stop at the statement: > **assert( SLAP_SOCK_NOT_ACTIVE(id, s) );** > > But the system output is > **Segmentation fault (core dumped)** > > It seems not related to whether it's a power of 2 or not, because even > I specify it as 64, i.e., 2^6, the result and error message are still > the same. That's to be expected since currently this setting has a hard-coded maximum of 16. Unless you have a machine with more than 1024 cores, I don't think your setting is valid. So again, this bug report is invalid. -- -- 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#7450) segfault with listener-threads=8
by jackie.qq.zhang＠gmail.com 25 Nov '12

25 Nov '12

Hi, Howard, GDB did stop at the statement: **assert( SLAP_SOCK_NOT_ACTIVE(id, s) );** But the system output is **Segmentation fault (core dumped)** It seems not related to whether it's a power of 2 or not, because even I specify it as 64, i.e., 2^6, the result and error message are still the same. Best regards, Jackie On Sun, Nov 25, 2012 at 5:04 PM, Howard Chu <hyc(a)symas.com> wrote: > > jackie.qq.zhang(a)gmail.com wrote: >> >> --20cf300faffd868e6d04cf5a0c62 >> Content-Type: text/plain; charset=ISO-8859-1 >> Content-Transfer-Encoding: quoted-printable >> >> >> Hi, Michael, >> >> This is my simplified configuration file which can reproduce the segfault. >> For the purpose of replay, I use "50" instead of "8" because using "8" >> sometime cannot reproduce the error. > > > This bug report is invalid. You reported a "segfault" originally, not an assert() as shown in this trace. The slapd.conf(5) manpage clearly states that the value should be a power of 2. > >> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= >> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D >> slapd.conf >> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= >> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D >> >> listener-threads 50 >> include /xxx/etc/openldap/schema/core.schema >> pidfile /xxx/var/run/slapd.pid >> argsfile /xxx/var/run/slapd.args >> >> database bdb >> suffix "dc=3Dxxx,dc=3Dxxx" >> rootdn "cn=3Dxxx,dc=3Dxxx,dc=3Dxxx" >> >> rootpw secret >> directory /xxx/var/openldap-data >> index objectClass eq >> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= >> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D >> >> >> >> The stack traces are: >> >> Thread 3 (Thread 0x7ffff4f2c700 (LWP 24897)): >> #0 0x00007ffff6d40481 in clone () from /lib/x86_64-linux-gnu/libc.so.6 >> #1 0x00007ffff7012dc0 in ?? () from /lib/x86_64-linux-gnu/libpthread.so.0 >> #2 0x00007ffff4f2c700 in ?? () >> #3 0x0000000000000000 in ?? () >> >> Thread 2 (Thread 0x7ffff572d700 (LWP 24896)): >> #0 0x000000000042543f in slapd_add (s=3D10, isactive=3D0, sl=3D0x0, id=3D0= >> ) at >> daemon.c:857 >> #1 0x0000000000429afc in slapd_daemon_task (ptr=3D0xaa8ed0) at daemon.c:21= >> >> 37 >> #2 0x00007ffff7012e9a in start_thread () from >> /lib/x86_64-linux-gnu/libpthread.so.0 >> #3 0x00007ffff6d404bd in clone () from /lib/x86_64-linux-gnu/libc.so.6 >> #4 0x0000000000000000 in ?? () >> >> Thread 1 (Thread 0x7ffff7fe1700 (LWP 24893)): >> #0 0x00007ffff6d40481 in clone () from /lib/x86_64-linux-gnu/libc.so.6 >> #1 0x00007ffff7011f70 in do_clone.constprop.4 () from >> /lib/x86_64-linux-gnu/libpthread.so.0 >> #2 0x00007ffff70138ba in pthread_create@@GLIBC_2.2.5 () from >> /lib/x86_64-linux-gnu/libpthread.so.0 >> #3 0x000000000058ccbb in ldap_pvt_thread_create (thread=3D0xaa8ed8, >> detach=3D0, start_routine=3D0x429a7c <slapd_daemon_task>, arg=3D0xaa8ed8\ >> >> ) at thr_posix.c:165 >> #4 0x000000000042bf28 in slapd_daemon () at daemon.c:2918 >> #5 0x00000000004087b8 in main (argc=3D7, argv=3D0x7fffffffe008) at main.c:= >> >> 1012 >> >> The GDB stopped at the following statement: >> >> assert( SLAP_SOCK_NOT_ACTIVE(id, s) ); >> >> which is in slapd_add, daemon.c:857. >> >> Best regards, >> Jackie >> >> >> >> On Sun, Nov 25, 2012 at 6:29 AM, Michael Str=F6der <michael(a)stroeder.com>wr= >> ote: >> >>> jackie.qq.zhang(a)gmail.com wrote: >>>> >>>> The default configuration does not have this problem. So I checked ever= >> >> y >>>> >>>> configuration setting I made and finally found it's caused by the >>> >>> following >>>> >>>> setting: >>>> >>>> listener-threads 8 >>> >>> >>> I tried to reproduce this by adding the line above to my local config. Bu= >> >> t >>> >>> slapd still works on my system. >>> >>> Could you please provide a canned config which reproduces the seg fault a= >> >> nd >>> >>> preferrably a full stack trace? >>> >>> http://www.openldap.org/faq/data/cache/59.html >>> >>> Make sure you have installed slapd with debug symbols (make install >>> STRIP=3D""). >>> >>> Ciao, Michael. >>> >> >> --20cf300faffd868e6d04cf5a0c62 >> Content-Type: text/html; charset=ISO-8859-1 >> Content-Transfer-Encoding: quoted-printable >> >> Hi, Michael, This is my simplified configuration file which can repr= >> oduce the segfault. For the purpose of replay, I use "50" instead= >> of "8" because using "8" sometime cannot reproduce the= >> error. >> >> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= >> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D >> slapd.conf >> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= >> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D >> listener-threads 50 include=A0=A0=A0=A0=A0=A0 /xxx/etc/openldap/schema/c= >> ore.schema >> pidfile=A0=A0=A0=A0=A0=A0=A0=A0 /xxx/var/run/slapd.pid >> argsfile=A0=A0=A0=A0=A0=A0 /xxx/var/run/slapd.args >> >> database=A0=A0=A0=A0=A0=A0=A0 bdb >> suffix=A0=A0=A0=A0=A0=A0=A0=A0=A0 "dc=3Dxxx,dc=3Dxxx" >> rootdn=A0=A0=A0=A0=A0=A0=A0=A0=A0 "cn=3Dxxx,dc=3Dxxx,dc=3Dxxx"<br= >>> >>> >> rootpw=A0=A0=A0=A0=A0=A0=A0=A0=A0 secret >> directory=A0=A0=A0=A0=A0=A0 /xxx/var/openldap-data >> index=A0=A0 objectClass=A0=A0=A0=A0 eq >> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= >> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D The stack traces are:= >> Thread 3 (Thread 0x7ffff4f2c700 (LWP 24897)): #0=A0 0x00007ffff6= >> d40481 in clone () from /lib/x86_64-linux-gnu/libc.so.6 #1=A0 0x00007fff= >> f7012dc0 in ?? () from /lib/x86_64-linux-gnu/libpthread.so.0 >> #2=A0 0x00007ffff4f2c700 in ?? () #3=A0 0x0000000000000000 in ?? () <= >> br>Thread 2 (Thread 0x7ffff572d700 (LWP 24896)): #0=A0 0x000000000042543= >> f in slapd_add (s=3D10, isactive=3D0, sl=3D0x0, id=3D0) at daemon.c:857 = >> #1=A0 0x0000000000429afc in slapd_daemon_task (ptr=3D0xaa8ed0) at daemon.c:= >> 2137 >> #2=A0 0x00007ffff7012e9a in start_thread () from /lib/x86_64-linux-gnu/libp= >> thread.so.0 #3=A0 0x00007ffff6d404bd in clone () from /lib/x86_64-linux-= >> gnu/libc.so.6 #4=A0 0x0000000000000000 in ?? () Thread 1 (Thread = >> 0x7ffff7fe1700 (LWP 24893)): >> #0=A0 0x00007ffff6d40481 in clone () from /lib/x86_64-linux-gnu/libc.so.6<b= >> r>#1=A0 0x00007ffff7011f70 in do_clone.constprop.4 () from /lib/x86_64-linu= >> x-gnu/libpthread.so.0 #2=A0 0x00007ffff70138ba in pthread_create@@GLIBC_= >> 2.2.5 () from /lib/x86_64-linux-gnu/libpthread.so.0 >> #3=A0 0x000000000058ccbb in ldap_pvt_thread_create (thread=3D0xaa8ed8, deta= >> ch=3D0, start_routine=3D0x429a7c <slapd_daemon_task>, arg=3D0xaa8ed8\= >> ) at thr_posix.c:165 #4=A0 0x000000000042bf28 in slapd_daemon () at = >> daemon.c:2918 >> #5=A0 0x00000000004087b8 in main (argc=3D7, argv=3D0x7fffffffe008) at main.= >> c:1012 The GDB stopped at the following statement: assert( S= >> LAP_SOCK_NOT_ACTIVE(id, s) ); which is in slapd_add, daemon.c:857.<b= >> r> >> Best regards, Jackie <div class=3D"gmail_quote">On Su= >> n, Nov 25, 2012 at 6:29 AM, Michael Str=F6der <<a href= >> =3D"mailto:michael@stroeder.com" target=3D"_blank">michael(a)stroeder.com</a>= >> > wrote: >> <blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p= >> x #ccc solid;padding-left:1ex"><a href=3D"mailto:jackie.qq.zhang@gmail.com"= >>> >>> jackie.qq.zhang(a)gmail.com</a> wrote: >> >> > The default configuration does not have this problem. So I checked eve= >> ry >> > configuration setting I made and finally found it's caused by the = >> following >> > setting: >> > >> > listener-threads 8 >> >> I tried to reproduce this by adding the line above to my local config. But<= >> br> >> slapd still works on my system. >> >> Could you please provide a canned config which reproduces the seg fault and= >> >> preferrably a full stack trace? >> >> <a href=3D"http://www.openldap.org/faq/data/cache/59.html" target=3D"_blank= >> ">http://www.openldap.org/faq/data/cache/59.html</a> >> >> >> Make sure you have installed slapd with debug symbols (make install STRIP= >> =3D""). >> >> Ciao, Michael. >> </blockquote></div> >> >> --20cf300faffd868e6d04cf5a0c62-- >> >> >> > > > -- > -- 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#7450) segfault with listener-threads=8
by hyc＠symas.com 25 Nov '12

25 Nov '12

jackie.qq.zhang(a)gmail.com wrote: > --20cf300faffd868e6d04cf5a0c62 > Content-Type: text/plain; charset=ISO-8859-1 > Content-Transfer-Encoding: quoted-printable > > Hi, Michael, > > This is my simplified configuration file which can reproduce the segfault. > For the purpose of replay, I use "50" instead of "8" because using "8" > sometime cannot reproduce the error. This bug report is invalid. You reported a "segfault" originally, not an assert() as shown in this trace. The slapd.conf(5) manpage clearly states that the value should be a power of 2. > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > slapd.conf > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > listener-threads 50 > include /xxx/etc/openldap/schema/core.schema > pidfile /xxx/var/run/slapd.pid > argsfile /xxx/var/run/slapd.args > > database bdb > suffix "dc=3Dxxx,dc=3Dxxx" > rootdn "cn=3Dxxx,dc=3Dxxx,dc=3Dxxx" > rootpw secret > directory /xxx/var/openldap-data > index objectClass eq > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > > > The stack traces are: > > Thread 3 (Thread 0x7ffff4f2c700 (LWP 24897)): > #0 0x00007ffff6d40481 in clone () from /lib/x86_64-linux-gnu/libc.so.6 > #1 0x00007ffff7012dc0 in ?? () from /lib/x86_64-linux-gnu/libpthread.so.0 > #2 0x00007ffff4f2c700 in ?? () > #3 0x0000000000000000 in ?? () > > Thread 2 (Thread 0x7ffff572d700 (LWP 24896)): > #0 0x000000000042543f in slapd_add (s=3D10, isactive=3D0, sl=3D0x0, id=3D0= > ) at > daemon.c:857 > #1 0x0000000000429afc in slapd_daemon_task (ptr=3D0xaa8ed0) at daemon.c:21= > 37 > #2 0x00007ffff7012e9a in start_thread () from > /lib/x86_64-linux-gnu/libpthread.so.0 > #3 0x00007ffff6d404bd in clone () from /lib/x86_64-linux-gnu/libc.so.6 > #4 0x0000000000000000 in ?? () > > Thread 1 (Thread 0x7ffff7fe1700 (LWP 24893)): > #0 0x00007ffff6d40481 in clone () from /lib/x86_64-linux-gnu/libc.so.6 > #1 0x00007ffff7011f70 in do_clone.constprop.4 () from > /lib/x86_64-linux-gnu/libpthread.so.0 > #2 0x00007ffff70138ba in pthread_create@@GLIBC_2.2.5 () from > /lib/x86_64-linux-gnu/libpthread.so.0 > #3 0x000000000058ccbb in ldap_pvt_thread_create (thread=3D0xaa8ed8, > detach=3D0, start_routine=3D0x429a7c <slapd_daemon_task>, arg=3D0xaa8ed8\ > ) at thr_posix.c:165 > #4 0x000000000042bf28 in slapd_daemon () at daemon.c:2918 > #5 0x00000000004087b8 in main (argc=3D7, argv=3D0x7fffffffe008) at main.c:= > 1012 > > The GDB stopped at the following statement: > > assert( SLAP_SOCK_NOT_ACTIVE(id, s) ); > > which is in slapd_add, daemon.c:857. > > Best regards, > Jackie > > > > On Sun, Nov 25, 2012 at 6:29 AM, Michael Str=F6der <michael(a)stroeder.com>wr= > ote: > >> jackie.qq.zhang(a)gmail.com wrote: >>> The default configuration does not have this problem. So I checked ever= > y >>> configuration setting I made and finally found it's caused by the >> following >>> setting: >>> >>> listener-threads 8 >> >> I tried to reproduce this by adding the line above to my local config. Bu= > t >> slapd still works on my system. >> >> Could you please provide a canned config which reproduces the seg fault a= > nd >> preferrably a full stack trace? >> >> http://www.openldap.org/faq/data/cache/59.html >> >> Make sure you have installed slapd with debug symbols (make install >> STRIP=3D""). >> >> Ciao, Michael. >> > > --20cf300faffd868e6d04cf5a0c62 > Content-Type: text/html; charset=ISO-8859-1 > Content-Transfer-Encoding: quoted-printable > > Hi, Michael, This is my simplified configuration file which can repr= > oduce the segfault. For the purpose of replay, I use "50" instead= > of "8" because using "8" sometime cannot reproduce the= > error. > > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > slapd.conf > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > listener-threads 50 include=A0=A0=A0=A0=A0=A0 /xxx/etc/openldap/schema/c= > ore.schema > pidfile=A0=A0=A0=A0=A0=A0=A0=A0 /xxx/var/run/slapd.pid > argsfile=A0=A0=A0=A0=A0=A0 /xxx/var/run/slapd.args > > database=A0=A0=A0=A0=A0=A0=A0 bdb > suffix=A0=A0=A0=A0=A0=A0=A0=A0=A0 "dc=3Dxxx,dc=3Dxxx" > rootdn=A0=A0=A0=A0=A0=A0=A0=A0=A0 "cn=3Dxxx,dc=3Dxxx,dc=3Dxxx"<br= >> > rootpw=A0=A0=A0=A0=A0=A0=A0=A0=A0 secret > directory=A0=A0=A0=A0=A0=A0 /xxx/var/openldap-data > index=A0=A0 objectClass=A0=A0=A0=A0 eq > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D The stack traces are:= > Thread 3 (Thread 0x7ffff4f2c700 (LWP 24897)): #0=A0 0x00007ffff6= > d40481 in clone () from /lib/x86_64-linux-gnu/libc.so.6 #1=A0 0x00007fff= > f7012dc0 in ?? () from /lib/x86_64-linux-gnu/libpthread.so.0 > #2=A0 0x00007ffff4f2c700 in ?? () #3=A0 0x0000000000000000 in ?? () <= > br>Thread 2 (Thread 0x7ffff572d700 (LWP 24896)): #0=A0 0x000000000042543= > f in slapd_add (s=3D10, isactive=3D0, sl=3D0x0, id=3D0) at daemon.c:857 = > #1=A0 0x0000000000429afc in slapd_daemon_task (ptr=3D0xaa8ed0) at daemon.c:= > 2137 > #2=A0 0x00007ffff7012e9a in start_thread () from /lib/x86_64-linux-gnu/libp= > thread.so.0 #3=A0 0x00007ffff6d404bd in clone () from /lib/x86_64-linux-= > gnu/libc.so.6 #4=A0 0x0000000000000000 in ?? () Thread 1 (Thread = > 0x7ffff7fe1700 (LWP 24893)): > #0=A0 0x00007ffff6d40481 in clone () from /lib/x86_64-linux-gnu/libc.so.6<b= > r>#1=A0 0x00007ffff7011f70 in do_clone.constprop.4 () from /lib/x86_64-linu= > x-gnu/libpthread.so.0 #2=A0 0x00007ffff70138ba in pthread_create@@GLIBC_= > 2.2.5 () from /lib/x86_64-linux-gnu/libpthread.so.0 > #3=A0 0x000000000058ccbb in ldap_pvt_thread_create (thread=3D0xaa8ed8, deta= > ch=3D0, start_routine=3D0x429a7c <slapd_daemon_task>, arg=3D0xaa8ed8\= > ) at thr_posix.c:165 #4=A0 0x000000000042bf28 in slapd_daemon () at = > daemon.c:2918 > #5=A0 0x00000000004087b8 in main (argc=3D7, argv=3D0x7fffffffe008) at main.= > c:1012 The GDB stopped at the following statement: assert( S= > LAP_SOCK_NOT_ACTIVE(id, s) ); which is in slapd_add, daemon.c:857.<b= > r> > Best regards, Jackie <div class=3D"gmail_quote">On Su= > n, Nov 25, 2012 at 6:29 AM, Michael Str=F6der <<a href= > =3D"mailto:michael@stroeder.com" target=3D"_blank">michael(a)stroeder.com</a>= > > wrote: > <blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p= > x #ccc solid;padding-left:1ex"><a href=3D"mailto:jackie.qq.zhang@gmail.com"= >> jackie.qq.zhang(a)gmail.com</a> wrote: > > The default configuration does not have this problem. So I checked eve= > ry > > configuration setting I made and finally found it's caused by the = > following > > setting: > > > > listener-threads 8 > > I tried to reproduce this by adding the line above to my local config. But<= > br> > slapd still works on my system. > > Could you please provide a canned config which reproduces the seg fault and= > > preferrably a full stack trace? > > <a href=3D"http://www.openldap.org/faq/data/cache/59.html" target=3D"_blank= > ">http://www.openldap.org/faq/data/cache/59.html</a> > > Make sure you have installed slapd with debug symbols (make install STRIP= > =3D""). > > Ciao, Michael. > </blockquote></div> > > --20cf300faffd868e6d04cf5a0c62-- > > > -- -- 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#7450) segfault with listener-threads=8
by jackie.qq.zhang＠gmail.com 25 Nov '12

25 Nov '12

--20cf300faffd868e6d04cf5a0c62 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi, Michael, This is my simplified configuration file which can reproduce the segfault. For the purpose of replay, I use "50" instead of "8" because using "8" sometime cannot reproduce the error. =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D slapd.conf =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D listener-threads 50 include /xxx/etc/openldap/schema/core.schema pidfile /xxx/var/run/slapd.pid argsfile /xxx/var/run/slapd.args database bdb suffix "dc=3Dxxx,dc=3Dxxx" rootdn "cn=3Dxxx,dc=3Dxxx,dc=3Dxxx" rootpw secret directory /xxx/var/openldap-data index objectClass eq =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D The stack traces are: Thread 3 (Thread 0x7ffff4f2c700 (LWP 24897)): #0 0x00007ffff6d40481 in clone () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x00007ffff7012dc0 in ?? () from /lib/x86_64-linux-gnu/libpthread.so.0 #2 0x00007ffff4f2c700 in ?? () #3 0x0000000000000000 in ?? () Thread 2 (Thread 0x7ffff572d700 (LWP 24896)): #0 0x000000000042543f in slapd_add (s=3D10, isactive=3D0, sl=3D0x0, id=3D0= ) at daemon.c:857 #1 0x0000000000429afc in slapd_daemon_task (ptr=3D0xaa8ed0) at daemon.c:21= 37 #2 0x00007ffff7012e9a in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #3 0x00007ffff6d404bd in clone () from /lib/x86_64-linux-gnu/libc.so.6 #4 0x0000000000000000 in ?? () Thread 1 (Thread 0x7ffff7fe1700 (LWP 24893)): #0 0x00007ffff6d40481 in clone () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x00007ffff7011f70 in do_clone.constprop.4 () from /lib/x86_64-linux-gnu/libpthread.so.0 #2 0x00007ffff70138ba in pthread_create@@GLIBC_2.2.5 () from /lib/x86_64-linux-gnu/libpthread.so.0 #3 0x000000000058ccbb in ldap_pvt_thread_create (thread=3D0xaa8ed8, detach=3D0, start_routine=3D0x429a7c <slapd_daemon_task>, arg=3D0xaa8ed8\ ) at thr_posix.c:165 #4 0x000000000042bf28 in slapd_daemon () at daemon.c:2918 #5 0x00000000004087b8 in main (argc=3D7, argv=3D0x7fffffffe008) at main.c:= 1012 The GDB stopped at the following statement: assert( SLAP_SOCK_NOT_ACTIVE(id, s) ); which is in slapd_add, daemon.c:857. Best regards, Jackie On Sun, Nov 25, 2012 at 6:29 AM, Michael Str=F6der <michael(a)stroeder.com>wr= ote: > jackie.qq.zhang(a)gmail.com wrote: > > The default configuration does not have this problem. So I checked ever= y > > configuration setting I made and finally found it's caused by the > following > > setting: > > > > listener-threads 8 > > I tried to reproduce this by adding the line above to my local config. Bu= t > slapd still works on my system. > > Could you please provide a canned config which reproduces the seg fault a= nd > preferrably a full stack trace? > > http://www.openldap.org/faq/data/cache/59.html > > Make sure you have installed slapd with debug symbols (make install > STRIP=3D""). > > Ciao, Michael. > --20cf300faffd868e6d04cf5a0c62 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi, Michael, This is my simplified configuration file which can repr= oduce the segfault. For the purpose of replay, I use "50" instead= of "8" because using "8" sometime cannot reproduce the= error. =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D slapd.conf =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D listener-threads 50 include=A0=A0=A0=A0=A0=A0 /xxx/etc/openldap/schema/c= ore.schema pidfile=A0=A0=A0=A0=A0=A0=A0=A0 /xxx/var/run/slapd.pid argsfile=A0=A0=A0=A0=A0=A0 /xxx/var/run/slapd.args database=A0=A0=A0=A0=A0=A0=A0 bdb suffix=A0=A0=A0=A0=A0=A0=A0=A0=A0 "dc=3Dxxx,dc=3Dxxx" rootdn=A0=A0=A0=A0=A0=A0=A0=A0=A0 "cn=3Dxxx,dc=3Dxxx,dc=3Dxxx"<br= > rootpw=A0=A0=A0=A0=A0=A0=A0=A0=A0 secret directory=A0=A0=A0=A0=A0=A0 /xxx/var/openldap-data index=A0=A0 objectClass=A0=A0=A0=A0 eq =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D The stack traces are:= Thread 3 (Thread 0x7ffff4f2c700 (LWP 24897)): #0=A0 0x00007ffff6= d40481 in clone () from /lib/x86_64-linux-gnu/libc.so.6 #1=A0 0x00007fff= f7012dc0 in ?? () from /lib/x86_64-linux-gnu/libpthread.so.0 #2=A0 0x00007ffff4f2c700 in ?? () #3=A0 0x0000000000000000 in ?? () <= br>Thread 2 (Thread 0x7ffff572d700 (LWP 24896)): #0=A0 0x000000000042543= f in slapd_add (s=3D10, isactive=3D0, sl=3D0x0, id=3D0) at daemon.c:857 = #1=A0 0x0000000000429afc in slapd_daemon_task (ptr=3D0xaa8ed0) at daemon.c:= 2137 #2=A0 0x00007ffff7012e9a in start_thread () from /lib/x86_64-linux-gnu/libp= thread.so.0 #3=A0 0x00007ffff6d404bd in clone () from /lib/x86_64-linux-= gnu/libc.so.6 #4=A0 0x0000000000000000 in ?? () Thread 1 (Thread = 0x7ffff7fe1700 (LWP 24893)): #0=A0 0x00007ffff6d40481 in clone () from /lib/x86_64-linux-gnu/libc.so.6<b= r>#1=A0 0x00007ffff7011f70 in do_clone.constprop.4 () from /lib/x86_64-linu= x-gnu/libpthread.so.0 #2=A0 0x00007ffff70138ba in pthread_create@@GLIBC_= 2.2.5 () from /lib/x86_64-linux-gnu/libpthread.so.0 #3=A0 0x000000000058ccbb in ldap_pvt_thread_create (thread=3D0xaa8ed8, deta= ch=3D0, start_routine=3D0x429a7c <slapd_daemon_task>, arg=3D0xaa8ed8\= ) at thr_posix.c:165 #4=A0 0x000000000042bf28 in slapd_daemon () at = daemon.c:2918 #5=A0 0x00000000004087b8 in main (argc=3D7, argv=3D0x7fffffffe008) at main.= c:1012 The GDB stopped at the following statement: assert( S= LAP_SOCK_NOT_ACTIVE(id, s) ); which is in slapd_add, daemon.c:857.<b= r> Best regards, Jackie <div class=3D"gmail_quote">On Su= n, Nov 25, 2012 at 6:29 AM, Michael Str=F6der <<a href= =3D"mailto:michael@stroeder.com" target=3D"_blank">michael(a)stroeder.com</a>= > wrote: <blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p= x #ccc solid;padding-left:1ex"><a href=3D"mailto:jackie.qq.zhang@gmail.com"= >jackie.qq.zhang(a)gmail.com</a> wrote: > The default configuration does not have this problem. So I checked eve= ry > configuration setting I made and finally found it's caused by the = following > setting: > > listener-threads 8 I tried to reproduce this by adding the line above to my local config. But<= br> slapd still works on my system. Could you please provide a canned config which reproduces the seg fault and= preferrably a full stack trace? <a href=3D"http://www.openldap.org/faq/data/cache/59.html" target=3D"_blank= ">http://www.openldap.org/faq/data/cache/59.html</a> Make sure you have installed slapd with debug symbols (make install STRIP= =3D""). Ciao, Michael. </blockquote></div> --20cf300faffd868e6d04cf5a0c62--

1 0

Re: (ITS#7450) segfault with listener-threads=8
by michael＠stroeder.com 25 Nov '12

25 Nov '12

jackie.qq.zhang(a)gmail.com wrote: > The default configuration does not have this problem. So I checked every > configuration setting I made and finally found it's caused by the following > setting: > > listener-threads 8 I tried to reproduce this by adding the line above to my local config. But slapd still works on my system. Could you please provide a canned config which reproduces the seg fault and preferrably a full stack trace? http://www.openldap.org/faq/data/cache/59.html Make sure you have installed slapd with debug symbols (make install STRIP=""). Ciao, Michael.

1 0

(ITS#7450) segfault with listener-threads=8
by jackie.qq.zhang＠gmail.com 24 Nov '12

24 Nov '12

Full_Name: Jackie Zhang Version: 2.4.33 OS: Ubuntu 10.04 URL: Submission from: (NULL) (2607:f720:1300:1241:9502:8240:b2b5:ba3f) When I start the server, I saw the following error messages: 50b1ca90 bdb_db_open: warning - no DB_CONFIG file found in directory /xxx/openldap-2.4.33/var/openldap-data: (2). Expect poor performance for suffix "dc=xxx,dc=xxx". 50b1ca90 bdb_monitor_db_open: monitoring disabled; configure monitor database to enable 50b1ca90 slapd starting Segmentation fault (core dumped) The default configuration does not have this problem. So I checked every configuration setting I made and finally found it's caused by the following setting: listener-threads 8 Is this a bug?

1 0

Re: (ITS#7431) seg fault in constraint_check_restrict at constraint.c:713
by michael＠stroeder.com 24 Nov '12

24 Nov '12

This is a cryptographically signed message in MIME format. --------------ms010608050607040608060204 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Michael Str=F6der wrote: > Michael Str=F6der wrote: >> Jan Synacek wrote: >>> On 11/08/2012 08:14 AM, michael(a)stroeder.com wrote: >>>> FYI: I sent output of bt full to Jan with some data stripped because= of >>>> privacy concerns. >>>> >>>> Note that the entry for which constraint checking is done is added t= o the >>>> database. So something might be wrong *after* the check. >>> >>> Can you please try the attached patch? >> >> It seems to work. But I will test it during the next days more thoroug= hly. >=20 > No more seg faults so far in my setup which uses slapo-constraints quit= e > heavily. So I'd appreciate if Jan's patch lands in RE24 branch. What's the status of this? Is a more formal submission of Jan's patch needed to get this in? Ciao, Michael. --------------ms010608050607040608060204 Content-Type: application/pkcs7-signature; name="smime.p7s" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="smime.p7s" Content-Description: S/MIME Cryptographic Signature MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIILHzCC BT8wggQnoAMCAQICDwCmSwABAAIAivjZQ8SBvzANBgkqhkiG9w0BAQUFADB8MQswCQYDVQQG EwJERTEcMBoGA1UEChMTVEMgVHJ1c3RDZW50ZXIgR21iSDElMCMGA1UECxMcVEMgVHJ1c3RD ZW50ZXIgQ2xhc3MgMSBMMSBDQTEoMCYGA1UEAxMfVEMgVHJ1c3RDZW50ZXIgQ2xhc3MgMSBM MSBDQSBJWDAeFw0xMjA2MDYxOTAyMTZaFw0xMzA2MDcxOTAyMTZaMCgxCzAJBgNVBAYTAkRF MRkwFwYDVQQDDBBNaWNoYWVsIFN0csO2ZGVyMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIB CgKCAQEAxXZGav40rnGNLxEggBW94MILWHlfC8a23Jew5U1gPlfRTXOjjzmoaZ1uCyGdgF6M VvuO9T1aTQNGH+OdeGe3P7Tfc/NsLJFJ2wtd8blvhmodUgse2eypiWjNOd4gZuhalBhgsQ0K b5D6/1foghII4E264iZlJ7AJ+UYcO+GxvFWT0YMTbLckgDkZk7c3qwTozdhYvXarvqx+8Ou/ kuxpQQhac/ebzxpu0N+RHSf2KIUS0g0tEGnPtGv6iL+9QNHc4JKo9Y9KKVw3tQy+Re+FQLxB 1fPE5F+qxuD3AUENpOwkMsqWLM94ohtx3CFqLpxfUPrnKFLAHOhHEbByYGvFPwIDAQABo4IC EDCCAgwwgaUGCCsGAQUFBwEBBIGYMIGVMFEGCCsGAQUFBzAChkVodHRwOi8vd3d3LnRydXN0 Y2VudGVyLmRlL2NlcnRzZXJ2aWNlcy9jYWNlcnRzL3RjX2NsYXNzMV9MMV9DQV9JWC5jcnQw QAYIKwYBBQUHMAGGNGh0dHA6Ly9vY3NwLml4LnRjY2xhc3MxLnRjdW5pdmVyc2FsLWkudHJ1 c3RjZW50ZXIuZGUwHwYDVR0jBBgwFoAU6bgoHUbP/M34TpvF7ktg69g7P9EwDAYDVR0TAQH/ BAIwADBKBgNVHSAEQzBBMD8GCSqCFAAsAQEBATAyMDAGCCsGAQUFBwIBFiRodHRwOi8vd3d3 LnRydXN0Y2VudGVyLmRlL2d1aWRlbGluZXMwDgYDVR0PAQH/BAQDAgTwMB0GA1UdDgQWBBS2 KAWfTfgJ/JQ63qLGwTXYLnI+LzBiBgNVHR8EWzBZMFegVaBThlFodHRwOi8vY3JsLml4LnRj Y2xhc3MxLnRjdW5pdmVyc2FsLWkudHJ1c3RjZW50ZXIuZGUvY3JsL3YyL3RjX0NsYXNzMV9M MV9DQV9JWC5jcmwwMwYDVR0lBCwwKgYIKwYBBQUHAwIGCCsGAQUFBwMEBggrBgEFBQcDBwYK KwYBBAGCNxQCAjAfBgNVHREEGDAWgRRtaWNoYWVsQHN0cm9lZGVyLmNvbTANBgkqhkiG9w0B AQUFAAOCAQEAQ3bvVUpEq+cQrLpcogyt5BJNk/WvUvOHqhzyj28M9pg9hcDl1+MYl5qqj6tR GSTLPQZyf287pcmbMwbcTGZO/gbW9v7RYcut6RauWdwKMCUmKC3J4fVfDq9ZETA2WOV68ef4 B3Gzdhghsbp3Rhp5dDmrCVKAHlafm6ZwJrEQ9P76fxnQZzRLgeKpZep5ePH5YHUB3+YaOQvJ FG0bOXvfHhRiRG7/HW2G+yDgjHSxDz8AFzMWL/RFePqZ4pn6T/SM/qU6WEpW39MWyJNoH/Kx QDYK8gGYuesn1ciMCTnjrvZQj0fonGTO4SfWekJRkuGrJ7dYSZRjYbDcWBBkdFLWzzCCBdgw ggTAoAMCAQICDgboAAEAAkqWLSQM/sXJMA0GCSqGSIb3DQEBBQUAMHkxCzAJBgNVBAYTAkRF MRwwGgYDVQQKExNUQyBUcnVzdENlbnRlciBHbWJIMSQwIgYDVQQLExtUQyBUcnVzdENlbnRl ciBVbml2ZXJzYWwgQ0ExJjAkBgNVBAMTHVRDIFRydXN0Q2VudGVyIFVuaXZlcnNhbCBDQSBJ MB4XDTA5MTEwMzE0MDgxOVoXDTI1MTIzMTIxNTk1OVowfDELMAkGA1UEBhMCREUxHDAaBgNV BAoTE1RDIFRydXN0Q2VudGVyIEdtYkgxJTAjBgNVBAsTHFRDIFRydXN0Q2VudGVyIENsYXNz IDEgTDEgQ0ExKDAmBgNVBAMTH1RDIFRydXN0Q2VudGVyIENsYXNzIDEgTDEgQ0EgSVgwggEi MA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQC75pBuz2Lp6QuqthDVR+V8XSsncZpozVVt 5KLv5P7yemMRwleKyH3PjmYfZUVL64Biab1GjovFblqVGCrep/EfdRonq20yU+P7TVhiLP8Z 5cegDZotIYhZhM0d8cPIij6w5d4IJM/8QCy6QSOUu4ASiTVItoYE4AFPjLqpmPwcie0fiqHH hpgmHnJla/7PZdkMZEsaCfVDEWBmJuMzVprJPT40anjG5VBLyM2I5DlsUCaeQCy2O3w3sqf1 3dyzUcv03IICuNc63towXA31Qt0TaVNU6YAmQjMepdfMbspmCZ+G8D2+xophEPPR/1vkstst smUMqX0XrLonTUJczglPAgMBAAGjggJZMIICVTCBmgYIKwYBBQUHAQEEgY0wgYowUgYIKwYB BQUHMAKGRmh0dHA6Ly93d3cudHJ1c3RjZW50ZXIuZGUvY2VydHNlcnZpY2VzL2NhY2VydHMv dGNfdW5pdmVyc2FsX3Jvb3RfSS5jcnQwNAYIKwYBBQUHMAGGKGh0dHA6Ly9vY3NwLnRjdW5p dmVyc2FsLUkudHJ1c3RjZW50ZXIuZGUwHwYDVR0jBBgwFoAUkqR1LKSevoFE63n8isWVpesQ dXMwEgYDVR0TAQH/BAgwBgEB/wIBADBSBgNVHSAESzBJMAYGBFUdIAAwPwYJKoIUACwBAQEB MDIwMAYIKwYBBQUHAgEWJGh0dHA6Ly93d3cudHJ1c3RjZW50ZXIuZGUvZ3VpZGVsaW5lczAO BgNVHQ8BAf8EBAMCAQYwHQYDVR0OBBYEFOm4KB1Gz/zN+E6bxe5LYOvYOz/RMIH9BgNVHR8E gfUwgfIwge+ggeyggemGRmh0dHA6Ly9jcmwudGN1bml2ZXJzYWwtSS50cnVzdGNlbnRlci5k ZS9jcmwvdjIvdGNfdW5pdmVyc2FsX3Jvb3RfSS5jcmyGgZ5sZGFwOi8vd3d3LnRydXN0Y2Vu dGVyLmRlL0NOPVRDJTIwVHJ1c3RDZW50ZXIlMjBVbml2ZXJzYWwlMjBDQSUyMEksTz1UQyUy MFRydXN0Q2VudGVyJTIwR21iSCxPVT1yb290Y2VydHMsREM9dHJ1c3RjZW50ZXIsREM9ZGU/ Y2VydGlmaWNhdGVSZXZvY2F0aW9uTGlzdD9iYXNlPzANBgkqhkiG9w0BAQUFAAOCAQEAOcjE m+6+mO5Icm+N53G2DpCM07LBFSGoRpBoX0oE8TrJaIQh2KXmBHVdn9LU8kt3QzLclctgvwJV 0KwcsMUUl5tlCsMPpR3s2Ek5lbWpvvr0HqtW56blAQiINV9nBd1EJFASIkRjefGbV2nOq9Yz UU+N8HA7jq1ROhd/NZZraGhjthwKyfjfHV7PKxGlY+3M0MbTIG+q/GhIfm0euDpFqhKG88e9 ALXr/uoSn3MzeOcoOWjTpW3adtFO4VWVgKbgG7jNrFbvRVlHmFLbOm4msjE5aXWxLiTwpJ2X iF4zKca1vAdAOgw9us90jEtOeiH6GzjNxEMvb7TfeO6Zkuc6HDGCA84wggPKAgEBMIGPMHwx CzAJBgNVBAYTAkRFMRwwGgYDVQQKExNUQyBUcnVzdENlbnRlciBHbWJIMSUwIwYDVQQLExxU QyBUcnVzdENlbnRlciBDbGFzcyAxIEwxIENBMSgwJgYDVQQDEx9UQyBUcnVzdENlbnRlciBD bGFzcyAxIEwxIENBIElYAg8ApksAAQACAIr42UPEgb8wCQYFKw4DAhoFAKCCAhMwGAYJKoZI hvcNAQkDMQsGCSqGSIb3DQEHATAcBgkqhkiG9w0BCQUxDxcNMTIxMTI0MTgzODM2WjAjBgkq hkiG9w0BCQQxFgQUhjp9n4t+TsTiZf/tl1jlQVW+7t0wbAYJKoZIhvcNAQkPMV8wXTALBglg hkgBZQMEASowCwYJYIZIAWUDBAECMAoGCCqGSIb3DQMHMA4GCCqGSIb3DQMCAgIAgDANBggq hkiG9w0DAgIBQDAHBgUrDgMCBzANBggqhkiG9w0DAgIBKDCBoAYJKwYBBAGCNxAEMYGSMIGP MHwxCzAJBgNVBAYTAkRFMRwwGgYDVQQKExNUQyBUcnVzdENlbnRlciBHbWJIMSUwIwYDVQQL ExxUQyBUcnVzdENlbnRlciBDbGFzcyAxIEwxIENBMSgwJgYDVQQDEx9UQyBUcnVzdENlbnRl ciBDbGFzcyAxIEwxIENBIElYAg8ApksAAQACAIr42UPEgb8wgaIGCyqGSIb3DQEJEAILMYGS oIGPMHwxCzAJBgNVBAYTAkRFMRwwGgYDVQQKExNUQyBUcnVzdENlbnRlciBHbWJIMSUwIwYD VQQLExxUQyBUcnVzdENlbnRlciBDbGFzcyAxIEwxIENBMSgwJgYDVQQDEx9UQyBUcnVzdENl bnRlciBDbGFzcyAxIEwxIENBIElYAg8ApksAAQACAIr42UPEgb8wDQYJKoZIhvcNAQEBBQAE ggEALrWnmZtYumwfT8BNjaBEw1Kmu02VjZNcQJk8xzfERqdKICA8Gza7VzhEdEIarBTO35C/ FCQsaPZN7jVYmfgBmneJrHKbqvQuOAjySvrvduoRJL0ZZkGQaMksnf/8rl6SW+hvMooNvbjR d7VYbYVRqSdCGrT+vmwarGG0pS6QY/vIc855hGHjUfQbPB3/dudo2BNyZy7L20L+83f1LPJv jw4sQqumL5cDlD8gFZdz7JfIQ1BmFbDgjchnMs4iidwZBjtHv1goM1SNUA2O79G7Ra1Tc+pD EGW9ePfiEhRCUM5xayjI4okWvtGu/z081/TGh+sYNszFcs6mRbbhJ/4l1QAAAAAAAA== --------------ms010608050607040608060204--

1 0

(ITS#7449) Signedness Conversion Issue
by tixu＠cs.ucsd.edu 21 Nov '12

21 Nov '12

Full_Name: Tianyin Xu Version: 2.4.33 OS: Ubuntu 12.04 (actually doesn't matter) URL: Submission from: (NULL) (2607:f720:1300:1241:512c:f07a:5efe:8eda) The data type of "index_substr_any_len" and "index_substr_any_step" are unsigned int. They should share the same flag ARG_UINT as "index_substr_if_{min,max}len" /* servers/slapd/schema_init.c */ 158 unsigned int index_substr_if_minlen = SLAP_INDEX_SUBSTR_IF_MINLEN_DEFAULT; 159 unsigned int index_substr_if_maxlen = SLAP_INDEX_SUBSTR_IF_MAXLEN_DEFAULT; 160 unsigned int index_substr_any_len = SLAP_INDEX_SUBSTR_ANY_LEN_DEFAULT; 161 unsigned int index_substr_any_step = SLAP_INDEX_SUBSTR_ANY_STEP_DEFAULT; In the current code, they are "ARG_INT" which convert -1 to be 4294967295. ==========================PATCH========================= @@ -399,13 +399,13 @@ { "index_substr_if_maxlen", "max", 2, 2, 0, ARG_UINT|ARG_NONZERO|ARG_MAGIC|CFG_SSTR_IF_MAX, &config_generic, "( OLcfgGlAt:21 NAME 'olcIndexSubstrIfMaxLen' " "SYNTAX OMsInteger SINGLE-VALUE )", NULL, NULL }, - { "index_substr_any_len", "len", 2, 2, 0, ARG_INT|ARG_NONZERO, + { "index_substr_any_len", "len", 2, 2, 0, ARG_UINT|ARG_NONZERO, &index_substr_any_len, "( OLcfgGlAt:22 NAME 'olcIndexSubstrAnyLen' " "SYNTAX OMsInteger SINGLE-VALUE )", NULL, NULL }, - { "index_substr_any_step", "step", 2, 2, 0, ARG_INT|ARG_NONZERO, + { "index_substr_any_step", "step", 2, 2, 0, ARG_UINT|ARG_NONZERO, &index_substr_any_step, "( OLcfgGlAt:23 NAME 'olcIndexSubstrAnyStep' " "SYNTAX OMsInteger SINGLE-VALUE )", NULL, NULL }, - { "index_intlen", "len", 2, 2, 0, ARG_INT|ARG_MAGIC|CFG_IX_INTLEN, + { "index_intlen", "len", 2, 2, 0, ARG_UINT|ARG_MAGIC|CFG_IX_INTLEN, &config_generic, "( OLcfgGlAt:84 NAME 'olcIndexIntLen' " "SYNTAX OMsInteger SINGLE-VALUE )", NULL, NULL }, { "lastmod", "on|off", 2, 2, 0, ARG_DB|ARG_ON_OFF|ARG_MAGIC|CFG_LASTMOD,

1 0

Re: (ITS#7448) "assertion failed" in MDB
by artemciy＠gmail.com 21 Nov '12

21 Nov '12

--047d7b10cce921f66204cf0610ec Content-Type: text/plain; charset=ISO-8859-1 On Wed, Nov 21, 2012 at 10:15 PM, Howard Chu <hyc(a)symas.com> wrote: > More information is needed than this. Your stack traces aren't even > complete. This isn't relevant. > What was the workload leading up to this? I can try to make an ltrace log, would that suffice? Give us a sample configuration that reproduces the assert. > Don't have time to make a test case now. > artemciy(a)gmail.com wrote: > >> Full_Name: Artem Grinblat >> Version: git, commit be781ab8081d7e9ad1eb89da81077c**7f936a5604 >> OS: Debian Wheezy >> URL: >> Submission from: (NULL) (213.108.212.44) >> >> >> MDB works okay for some time, then crashes with >> >> mdb.c:3778: mdb_page_search_root: Assertion `(((mp)->mp_pb.pb.pb_lower - >> ((unsigned) __builtin_offsetof (MDB_page, mp_ptrs))) >> 1) > 1' failed. >> >> (gdb) bt >> #0 WriteCoreDump (file_name=0x7f1f1f705fa0 "/tmp/tntnet.5541.core") at >> src/coredumper.c:192 >> #1 0x00007f1f4b163da9 in img2::writeCore (path=0x7f1f1f705fa0 >> "/tmp/tntnet.5541.core") at src/conf.cpp:49 >> #2 0x00007f1f4b16145d in img2::custom_sigaction (signum=6) at >> src/conf.cpp:89 >> #3 <signal handler called> >> #4 0x00007f1f469ba475 in *__GI_raise (sig=<optimized out>) at >> ../nptl/sysdeps/unix/sysv/**linux/raise.c:64 >> #5 0x00007f1f469bd6f0 in *__GI_abort () at abort.c:92 >> #6 0x00007f1f469b3621 in *__GI___assert_fail ( >> assertion=assertion@entry=**0x7f1f4155cdb0 >> "(((mp)->mp_pb.pb.pb_lower - >> ((unsigned) __builtin_offsetof (MDB_page, mp_ptrs))) >> 1) > 1", >> file=<optimized >> out>, >> file@entry=0x7f1f4155cb30 "mdb.c", line=line@entry=3778, >> function=function@entry=**0x7f1f4155d360 "mdb_page_search_root") at >> assert.c:81 >> #7 0x00007f1f41555ccd in mdb_page_search_root (mc=mc@entry >> =0x7f1f1f708500, >> key=key@entry=0x0, modify=modify@entry=0) at mdb.c:3778 >> #8 0x00007f1f4155467a in mdb_page_search (mc=mc@entry=0x7f1f1f708500, >> key=key@entry=0x0, flags=flags@entry=0) at mdb.c:3908 >> #9 0x00007f1f41554a07 in mdb_cursor_first (mc=0x7f1f1f708500, >> key=key@entry=0x7f1f1f7070f0, data=data@entry=0x0) at mdb.c:4354 >> #10 0x00007f1f4155517e in mdb_cursor_set (mc=mc@entry=0x7f1f1f708370, >> key=key@entry=0x7f1f1f708770, data=data@entry=**0x7f1f1f7070f0, >> op=op@entry=MDB_SET, >> exactp=exactp@entry=**0x7f1f1f7070d4) at mdb.c:4307 >> #11 0x00007f1f41559c8d in mdb_cursor_put (mc=0x7f1f1f708370, >> key=0x7f1f1f708770, >> data=0x7f1f1f708790, flags=0) at mdb.c:4672 >> #12 0x00007f1f4155bdc9 in mdb_put (txn=<optimized out>, dbi=<optimized >> out>, >> key=0x7f1f1f708770, data=0x7f1f1f708790, flags=<optimized out>) at >> mdb.c:6599 >> >> Also under Valgrind: >> ==7503== Warning: set address range perms: large range [0x3959d000, >> 0x7959d000) >> (defined) >> **7503** custom_sigaction, signal 6 at 0x51B6EEC: >> VALGRIND_PRINTF_BACKTRACE(char const*, ...) (valgrind.h:3771) >> ==7503== by 0x51B72A1: img2::custom_sigaction(int) (conf.cpp:77) >> ==7503== by 0x985B4EF: ??? (in /lib/x86_64-linux-gnu/libc-2.**13.so<http://libc-2.13.so> >> ) >> ==7503== by 0x985B474: raise (raise.c:64) >> ==7503== by 0x985E6EF: abort (abort.c:92) >> ==7503== by 0x9854620: __assert_fail (assert.c:81) >> ==7503== by 0xEDD9CCC: mdb_page_search_root (mdb.c:3778) >> ==7503== by 0xEDD8679: mdb_page_search (mdb.c:3908) >> ==7503== by 0xEDD8F78: mdb_cursor_set (mdb.c:4268) >> ==7503== by 0xEDD8EB0: mdb_cursor_set (mdb.c:4316) >> ==7503== by 0xEDDFCA8: mdb_del (mdb.c:6165) >> >> >> > > -- > -- Howard Chu > CTO, Symas Corp. http://www.symas.com > Director, Highland Sun http://highlandsun.com/hyc/ > Chief Architect, OpenLDAP http://www.openldap.org/**project/<http://www.openldap.org/project/> > --047d7b10cce921f66204cf0610ec Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable On Wed, Nov 21, 2012 at 10:15 PM, Howard Chu <<a href= =3D"mailto:hyc@symas.com" target=3D"_blank">hyc(a)symas.com</a>> wr= ote: <div><div class=3D"gmail_quote"><blockquote class=3D"gmail_quote" s= tyle=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> More information is needed than this. Your stack traces aren't even com= plete.</blockquote><div> </div><div>This isn't relevant.</div><div>= =A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;borde= r-left:1px #ccc solid;padding-left:1ex"> What was the workload leading up to this?</blockquote><div> </div><div>= I can try to make an ltrace log, would that suffice?</div><div> </div><b= lockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px = #ccc solid;padding-left:1ex"> Give us a sample configuration that reproduces the assert. </blockquote>= <div> </div><div>Don't have time to make a test case now.</div><div>= </div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;bord= er-left:1px #ccc solid;padding-left:1ex"> <a href=3D"mailto:artemciy@gmail.com" target=3D"_blank">artemciy(a)gmail.com<= /a> wrote: <blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p= x #ccc solid;padding-left:1ex"> Full_Name: Artem Grinblat Version: git, commit be781ab8081d7e9ad1eb89da81077c7f936a5604 OS: Debian Wheezy URL: Submission from: (NULL) (213.108.212.44) MDB works okay for some time, then crashes with mdb.c:3778: mdb_page_search_root: Assertion `(((mp)->mp_pb.pb.pb_lower -= ((unsigned) __builtin_offsetof (MDB_page, mp_ptrs))) >> 1) > 1&#39= ; failed. (gdb) bt #0 =A0WriteCoreDump (file_name=3D0x7f1f1f705fa0 "/tmp/tntnet.5541.core= ") at src/coredumper.c:192 #1 =A00x00007f1f4b163da9 in img2::writeCore (path=3D0x7f1f1f705fa0 "/tmp/tntnet.5541.core") at src/conf.cpp:49 #2 =A00x00007f1f4b16145d in img2::custom_sigaction (signum=3D6) at src/conf= .cpp:89 #3 =A0<signal handler called> #4 =A00x00007f1f469ba475 in *__GI_raise (sig=3D<optimized out>) at<br= > ../nptl/sysdeps/unix/sysv/linux/raise.c:64 #5 =A00x00007f1f469bd6f0 in *__GI_abort () at abort.c:92 #6 =A00x00007f1f469b3621 in *__GI___assert_fail ( =A0 =A0 =A0assertion=3Dassertion@entry=3D0x7f1f4155cdb0 "(((mp)= ->mp_pb.pb.pb_lower - ((unsigned) __builtin_offsetof (MDB_page, mp_ptrs))) >> 1) > 1&quo= t;, file=3D<optimized out>, =A0 =A0 =A0file@entry=3D0x7f1f4155cb30 "mdb.c", line=3Dline@entry= =3D3778, function=3Dfunction@entry=3D0x7f1f4155d360 "mdb_page_search_roo= t") at assert.c:81 #7 =A00x00007f1f41555ccd in mdb_page_search_root (mc=3Dmc@entry=3D0x7f1f1f7= 08500, key=3Dkey@entry=3D0x0, modify=3Dmodify@entry=3D0) at mdb.c:3778 #8 =A00x00007f1f4155467a in mdb_page_search (mc=3Dmc@entry=3D0x7f1f1f708500= , key=3Dkey@entry=3D0x0, flags=3Dflags@entry=3D0) at mdb.c:3908 #9 =A00x00007f1f41554a07 in mdb_cursor_first (mc=3D0x7f1f1f708500, key=3Dkey@entry=3D0x7f1f1f7070f0, data=3Ddata@entry=3D0x0) at mdb.c:4354<br= > #10 0x00007f1f4155517e in mdb_cursor_set (mc=3Dmc@entry=3D0x7f1f1f708370,<b= r> key=3Dkey@entry=3D0x7f1f1f708770, data=3Ddata@entry=3D0x7f1f1f7070f0= , op=3Dop@entry=3DMDB_SET, =A0 =A0 =A0exactp=3Dexactp@entry=3D0x7f1f1f7070d4) at mdb.c:4307 #11 0x00007f1f41559c8d in mdb_cursor_put (mc=3D0x7f1f1f708370, key=3D0x7f1f= 1f708770, data=3D0x7f1f1f708790, flags=3D0) at mdb.c:4672 #12 0x00007f1f4155bdc9 in mdb_put (txn=3D<optimized out>, dbi=3D<o= ptimized out>, key=3D0x7f1f1f708770, data=3D0x7f1f1f708790, flags=3D<optimized out>)= at mdb.c:6599 Also under Valgrind: =3D=3D7503=3D=3D Warning: set address range perms: large range [0x3959d000,= 0x7959d000) (defined) **7503** custom_sigaction, signal 6 =A0 at 0x51B6EEC: VALGRIND_PRINTF_BACKTRACE(char const*, ...) (valgrind.h:3771) =3D=3D7503=3D=3D =A0 =A0by 0x51B72A1: img2::custom_sigaction(int) (conf.cpp= :77) =3D=3D7503=3D=3D =A0 =A0by 0x985B4EF: ??? (in /lib/x86_64-linux-gnu/<a href= =3D"http://libc-2.13.so" target=3D"_blank">libc-2.13.so</a>) =3D=3D7503=3D=3D =A0 =A0by 0x985B474: raise (raise.c:64) =3D=3D7503=3D=3D =A0 =A0by 0x985E6EF: abort (abort.c:92) =3D=3D7503=3D=3D =A0 =A0by 0x9854620: __assert_fail (assert.c:81) =3D=3D7503=3D=3D =A0 =A0by 0xEDD9CCC: mdb_page_search_root (mdb.c:3778) =3D=3D7503=3D=3D =A0 =A0by 0xEDD8679: mdb_page_search (mdb.c:3908) =3D=3D7503=3D=3D =A0 =A0by 0xEDD8F78: mdb_cursor_set (mdb.c:4268) =3D=3D7503=3D=3D =A0 =A0by 0xEDD8EB0: mdb_cursor_set (mdb.c:4316) =3D=3D7503=3D=3D =A0 =A0by 0xEDDFCA8: mdb_del (mdb.c:6165) </blockquote> -- =A0 -- Howard Chu =A0 CTO, Symas Corp. =A0 =A0 =A0 =A0 =A0 <a href=3D"http://www.symas.com" t= arget=3D"_blank">http://www.symas.com</a> =A0 Director, Highland Sun =A0 =A0 <a href=3D"http://highlandsun.com/hyc/" = target=3D"_blank">http://highlandsun.com/hyc/</a> =A0 Chief Architect, OpenLDAP =A0<a href=3D"http://www.openldap.org/project= /" target=3D"_blank">http://www.openldap.org/project/</a> </blockquote></div> </div> --047d7b10cce921f66204cf0610ec--

1 0

Re: (ITS#7448) "assertion failed" in MDB
by hyc＠symas.com 21 Nov '12

21 Nov '12

More information is needed than this. Your stack traces aren't even complete. What was the workload leading up to this? Give us a sample configuration that reproduces the assert. artemciy(a)gmail.com wrote: > Full_Name: Artem Grinblat > Version: git, commit be781ab8081d7e9ad1eb89da81077c7f936a5604 > OS: Debian Wheezy > URL: > Submission from: (NULL) (213.108.212.44) > > > MDB works okay for some time, then crashes with > > mdb.c:3778: mdb_page_search_root: Assertion `(((mp)->mp_pb.pb.pb_lower - > ((unsigned) __builtin_offsetof (MDB_page, mp_ptrs))) >> 1) > 1' failed. > > (gdb) bt > #0 WriteCoreDump (file_name=0x7f1f1f705fa0 "/tmp/tntnet.5541.core") at > src/coredumper.c:192 > #1 0x00007f1f4b163da9 in img2::writeCore (path=0x7f1f1f705fa0 > "/tmp/tntnet.5541.core") at src/conf.cpp:49 > #2 0x00007f1f4b16145d in img2::custom_sigaction (signum=6) at src/conf.cpp:89 > #3 <signal handler called> > #4 0x00007f1f469ba475 in *__GI_raise (sig=<optimized out>) at > ../nptl/sysdeps/unix/sysv/linux/raise.c:64 > #5 0x00007f1f469bd6f0 in *__GI_abort () at abort.c:92 > #6 0x00007f1f469b3621 in *__GI___assert_fail ( > assertion=assertion@entry=0x7f1f4155cdb0 "(((mp)->mp_pb.pb.pb_lower - > ((unsigned) __builtin_offsetof (MDB_page, mp_ptrs))) >> 1) > 1", file=<optimized > out>, > file@entry=0x7f1f4155cb30 "mdb.c", line=line@entry=3778, > function=function@entry=0x7f1f4155d360 "mdb_page_search_root") at assert.c:81 > #7 0x00007f1f41555ccd in mdb_page_search_root (mc=mc@entry=0x7f1f1f708500, > key=key@entry=0x0, modify=modify@entry=0) at mdb.c:3778 > #8 0x00007f1f4155467a in mdb_page_search (mc=mc@entry=0x7f1f1f708500, > key=key@entry=0x0, flags=flags@entry=0) at mdb.c:3908 > #9 0x00007f1f41554a07 in mdb_cursor_first (mc=0x7f1f1f708500, > key=key@entry=0x7f1f1f7070f0, data=data@entry=0x0) at mdb.c:4354 > #10 0x00007f1f4155517e in mdb_cursor_set (mc=mc@entry=0x7f1f1f708370, > key=key@entry=0x7f1f1f708770, data=data@entry=0x7f1f1f7070f0, > op=op@entry=MDB_SET, > exactp=exactp@entry=0x7f1f1f7070d4) at mdb.c:4307 > #11 0x00007f1f41559c8d in mdb_cursor_put (mc=0x7f1f1f708370, key=0x7f1f1f708770, > data=0x7f1f1f708790, flags=0) at mdb.c:4672 > #12 0x00007f1f4155bdc9 in mdb_put (txn=<optimized out>, dbi=<optimized out>, > key=0x7f1f1f708770, data=0x7f1f1f708790, flags=<optimized out>) at mdb.c:6599 > > Also under Valgrind: > ==7503== Warning: set address range perms: large range [0x3959d000, 0x7959d000) > (defined) > **7503** custom_sigaction, signal 6 at 0x51B6EEC: > VALGRIND_PRINTF_BACKTRACE(char const*, ...) (valgrind.h:3771) > ==7503== by 0x51B72A1: img2::custom_sigaction(int) (conf.cpp:77) > ==7503== by 0x985B4EF: ??? (in /lib/x86_64-linux-gnu/libc-2.13.so) > ==7503== by 0x985B474: raise (raise.c:64) > ==7503== by 0x985E6EF: abort (abort.c:92) > ==7503== by 0x9854620: __assert_fail (assert.c:81) > ==7503== by 0xEDD9CCC: mdb_page_search_root (mdb.c:3778) > ==7503== by 0xEDD8679: mdb_page_search (mdb.c:3908) > ==7503== by 0xEDD8F78: mdb_cursor_set (mdb.c:4268) > ==7503== by 0xEDD8EB0: mdb_cursor_set (mdb.c:4316) > ==7503== by 0xEDDFCA8: mdb_del (mdb.c:6165) > > -- -- 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#7428) libldap: use non-blocking IO during TLS handshake
by rhafer＠suse.de 21 Nov '12

21 Nov '12

I just pushed latest incarnation of my patch to master. The code in currently hidden behind #ifdefs (mainly for the NSS issues outlined on -devel) and I switch back again to using LDAP_OPT_NETWORK_TIMEOUT for TLS handshake timeouts. regards, Ralf On Thu, Nov 01, 2012 at 05:22:42PM +0000, rhafer(a)suse.de wrote: > > Currently libldap is using blocking IO when performing the SSL handshake for > ldaps:// connections (and when performing the StartTLS operation). The can lead > to the client blocking forever in the ssl lib (in SSL_connect in case of > openssl) if e.g. the server for whatever reason stops responding. It would be > very helpful if libldap would use non-blocking IO during the handshake at least > when LDAP_OPT_NETWORK_TIMEOUT (or LDAP_OPT_TIMEOUT?) are set.

1 0

(ITS#7448) "assertion failed" in MDB
by artemciy＠gmail.com 20 Nov '12

20 Nov '12

Full_Name: Artem Grinblat Version: git, commit be781ab8081d7e9ad1eb89da81077c7f936a5604 OS: Debian Wheezy URL: Submission from: (NULL) (213.108.212.44) MDB works okay for some time, then crashes with mdb.c:3778: mdb_page_search_root: Assertion `(((mp)->mp_pb.pb.pb_lower - ((unsigned) __builtin_offsetof (MDB_page, mp_ptrs))) >> 1) > 1' failed. (gdb) bt #0 WriteCoreDump (file_name=0x7f1f1f705fa0 "/tmp/tntnet.5541.core") at src/coredumper.c:192 #1 0x00007f1f4b163da9 in img2::writeCore (path=0x7f1f1f705fa0 "/tmp/tntnet.5541.core") at src/conf.cpp:49 #2 0x00007f1f4b16145d in img2::custom_sigaction (signum=6) at src/conf.cpp:89 #3 <signal handler called> #4 0x00007f1f469ba475 in *__GI_raise (sig=<optimized out>) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64 #5 0x00007f1f469bd6f0 in *__GI_abort () at abort.c:92 #6 0x00007f1f469b3621 in *__GI___assert_fail ( assertion=assertion@entry=0x7f1f4155cdb0 "(((mp)->mp_pb.pb.pb_lower - ((unsigned) __builtin_offsetof (MDB_page, mp_ptrs))) >> 1) > 1", file=<optimized out>, file@entry=0x7f1f4155cb30 "mdb.c", line=line@entry=3778, function=function@entry=0x7f1f4155d360 "mdb_page_search_root") at assert.c:81 #7 0x00007f1f41555ccd in mdb_page_search_root (mc=mc@entry=0x7f1f1f708500, key=key@entry=0x0, modify=modify@entry=0) at mdb.c:3778 #8 0x00007f1f4155467a in mdb_page_search (mc=mc@entry=0x7f1f1f708500, key=key@entry=0x0, flags=flags@entry=0) at mdb.c:3908 #9 0x00007f1f41554a07 in mdb_cursor_first (mc=0x7f1f1f708500, key=key@entry=0x7f1f1f7070f0, data=data@entry=0x0) at mdb.c:4354 #10 0x00007f1f4155517e in mdb_cursor_set (mc=mc@entry=0x7f1f1f708370, key=key@entry=0x7f1f1f708770, data=data@entry=0x7f1f1f7070f0, op=op@entry=MDB_SET, exactp=exactp@entry=0x7f1f1f7070d4) at mdb.c:4307 #11 0x00007f1f41559c8d in mdb_cursor_put (mc=0x7f1f1f708370, key=0x7f1f1f708770, data=0x7f1f1f708790, flags=0) at mdb.c:4672 #12 0x00007f1f4155bdc9 in mdb_put (txn=<optimized out>, dbi=<optimized out>, key=0x7f1f1f708770, data=0x7f1f1f708790, flags=<optimized out>) at mdb.c:6599 Also under Valgrind: ==7503== Warning: set address range perms: large range [0x3959d000, 0x7959d000) (defined) **7503** custom_sigaction, signal 6 at 0x51B6EEC: VALGRIND_PRINTF_BACKTRACE(char const*, ...) (valgrind.h:3771) ==7503== by 0x51B72A1: img2::custom_sigaction(int) (conf.cpp:77) ==7503== by 0x985B4EF: ??? (in /lib/x86_64-linux-gnu/libc-2.13.so) ==7503== by 0x985B474: raise (raise.c:64) ==7503== by 0x985E6EF: abort (abort.c:92) ==7503== by 0x9854620: __assert_fail (assert.c:81) ==7503== by 0xEDD9CCC: mdb_page_search_root (mdb.c:3778) ==7503== by 0xEDD8679: mdb_page_search (mdb.c:3908) ==7503== by 0xEDD8F78: mdb_cursor_set (mdb.c:4268) ==7503== by 0xEDD8EB0: mdb_cursor_set (mdb.c:4316) ==7503== by 0xEDDFCA8: mdb_del (mdb.c:6165)

1 0

Re: (ITS#7447) backsql and german umlaute
by metzdorf＠geograt.de 20 Nov '12

20 Nov '12

The umlaut's are gone while posting. So i will try to describe: The search expression is "search<lower umlaut a>o<lower umlaut o>u...". This is converted to "SEARCH<lower umlaut a>O<lower umlaut o>U" in the SELECT statement. The expected is "SEARCH<upper umlaut a>O<upper umlaut o>U". -- Herbert Metzdorf

1 0

(ITS#7447) backsql and german umlaute
by metzdorf＠geograt.de 20 Nov '12

20 Nov '12

Full_Name: Herbert Metzdorf Version: 2.4.30 OS: Windows 7 / 2008 URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (87.138.76.52) I am using thunderbird to query the openldap with the sql backend. Queries with german umlaut's give no result because of wrong lower/uppercase conversion. Look at the following log snippets: 50ab7cdb ==> limits_get: conn=1008 op=1 self="[anonymous]" this="ou=adressen,dc=geograt,dc=de" 50ab7cdb ==>backsql_search(): base="ou=adressen,dc=geograt,dc=de", filter="(|(?mail=*searchäoöuü*)(cn=*searchäoöuü*)(givenName=*searchäoöuü*)(sn=*searchäoöuü*))", scope=2,50ab7cdb deref=0, attrsonly=0, attributes to load: custom list 50ab7cdb ==>backsql_get_db_conn() ... 50ab7cdb <==backsql_srch_query() returns SELECT DISTINCT ldap_entries.id,ldap_persons.sysid,'inetOrgPerson' AS objectClass,ldap_entries.dn AS dn FROM ldap_entries,ldap_persons WHERE ldap_persons.sysid=ldap_entries.keyval AND ldap_entries.oc_map_id=? AND UPPER(ldap_entries.dn) LIKE CONCAT('%',UPPER(?)) AND (1=0 OR (UPPER(vorname||' '||nachname) LIKE '%SEARCHäOöUü%') OR (UPPER(vorname) LIKE '%SEARCHäOöUü%') OR (UPPER(nachname) LIKE '%SEARCHäOöUü%')) The search expression in converted to uppercase but this fails for the umlaut's. Is there a parameter to configure this behavior, or do you know a workaround? Thanks for your help Herbert

1 0

Re: (ITS#7446) slapadd OBSOLETE object class fails
by michael＠stroeder.com 19 Nov '12

19 Nov '12

masarati(a)aero.polimi.it wrote: > Maybe "manage" should be passed to > slap_tool_entry_check(), and write tools (slapadd, slapmodify) could have > an explicit '-o manage' option to enable handling of these cases. I'd regard slapadd to be in kind of a manage mode by default. E.g. it does not check constraints. And as said OBSOLETE attribute types are already accepted. Ciao, Michael.

1 0

Re: (ITS#7446) slapadd OBSOLETE object class fails
by masarati＠aero.polimi.it 19 Nov '12

19 Nov '12

> Full_Name: Michael Ströder > Version: HEAD > OS: > URL: > Submission from: (NULL) (79.227.170.198) > > > Importing an LDIF file with slapadd which contains entries with an object > class > marked as OBSOLETE in the schema fails. > > Importing entries with OBSOLETE attribute types seems to work just fine. > > If object classes are marked as OBSOLETE it's clear that it should be > impossible > to add new entries via LDAP based on such an object class. But it should > still > be possible to restore old entries from backup. Currently, slap_tool_entry_check() sets "manage" to 0 when calling entry_schema_check(); setting it to !0 would allow loading of OBSOLETE objectClasses. Maybe "manage" should be passed to slap_tool_entry_check(), and write tools (slapadd, slapmodify) could have an explicit '-o manage' option to enable handling of these cases. p. -- Pierangelo Masarati Associate Professor Dipartimento di Ingegneria Aerospaziale Politecnico di Milano

1 0

(ITS#7446) slapadd OBSOLETE object class fails
by michael＠stroeder.com 19 Nov '12

19 Nov '12

Full_Name: Michael Ströder Version: HEAD OS: URL: Submission from: (NULL) (79.227.170.198) Importing an LDIF file with slapadd which contains entries with an object class marked as OBSOLETE in the schema fails. Importing entries with OBSOLETE attribute types seems to work just fine. If object classes are marked as OBSOLETE it's clear that it should be impossible to add new entries via LDAP based on such an object class. But it should still be possible to restore old entries from backup.

1 0

(ITS#7445) slapo-deref: deref control should only be register when actually enabled
by rhafer＠suse.de 19 Nov '12

19 Nov '12

Full_Name: Ralf Haferkamp Version: HEAD, RE24 OS: SLES11 URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (92.252.81.246) This is similar to ITS#6647 (which was about sssvlv). Support for the deref control should only be advertised in rootDSE when at least one instance of the deref overlay is present. Patch is on the way.

1 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

openldap-bugs