- openldap-bugs - openldap.org

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 <span dir=3D"ltr">&lt= ;<a href=3D"mailto:quanah@zimbra.com" target=3D"_blank">quanah(a)zimbra.com</= a>></span> wrote:<br><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:<br> <br> <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.<u></u>org.uk/~sgtatham/bugs.html</a><b= r> </blockquote> <br> 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><br></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 <span dir=3D"ltr"><<a href= =3D"mailto:hyc@symas.com" target=3D"_blank">hyc(a)symas.com</a>></span> wr= ote:<br><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"> <br></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/<u></u>i= ndex.cgi</a> that bugs<br> without a test case wouldn't be investigated so that people won't w= aste<br> their time.<br> </div></blockquote> <br> <a href=3D"http://www.openldap.org/faq/data/cache/1122.html" target=3D"_bla= nk">http://www.openldap.org/faq/<u></u>data/cache/1122.html</a></blockquote= ><div><br></div><div><span style=3D"font-family:'Times New Roman';f= ont-size:medium">"In case the first aim doesn't succeed, and the p= rogrammer=A0</span><em style=3D"font-family:'Times New Roman';font-= size:medium">can't</em><span style=3D"font-family:'Times New Roman&= #39;;font-size:medium">=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,=A0</span><em style=3D"font-family:'Times New Roman';f= ont-size:medium">especially</em><span style=3D"font-family:'Times New R= oman';font-size:medium">=A0if they have numbers in". -=A0</span><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></font></div> <div><br></div><div><font face=3D"Times New Roman" size=3D"3">Stack trace a= nd proposal to do ltrace is the best detail you've got in a normal bug = report.</font></div><div><font face=3D"Times New Roman" size=3D"3">Good luc= k.</font></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 27 Nov '12

27 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 <span dir=3D"ltr"><= <a href=3D"mailto:quanah@zimbra.com" target=3D"_blank">quanah(a)zimbra.com</a= >></span> 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.<br> </div></blockquote> <br> 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><br></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. :/<br> <br> --Quanah<br></blockquote><div><br></div></div> --f46d042fddcee1dc8704cf74ca2b--

1 0

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

27 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 27 Nov '12

27 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 <span dir=3D"ltr"><<a href= =3D"mailto:hyc@symas.com" target=3D"_blank">hyc(a)symas.com</a>></span> wr= ote:<br><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<br> endeavor that can be quite costly. IMO, refusing to investigate a bug<br> without a test case is not a sane support politics.<br> </div></blockquote> <br> 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><br></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 27 Nov '12

27 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 <span dir=3D"ltr"><= <a href=3D"mailto:quanah@zimbra.com" target=3D"_blank">quanah(a)zimbra.com</a= >></span> wrote:<br><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.<br> </div></blockquote> <br> 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. :/<br> <br> --Quanah<br></blockquote><div><br></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

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

openldap-bugs