openldap-bugs

openldap-bugs@openldap.org

1 participants
20996 discussions

(ITS#5020) configure needs -pthread to find pthread.h
by h.b.furuseth＠usit.uio.no 15 Jun '07

15 Jun '07

Full_Name: Hallvard B Furuseth Version: HEAD, RE23 OS: OSF1 V5.1 alpha URL: Submission from: (NULL) (129.240.202.105) Submitted by: hallvard /configure on OSF1 alpha finds no suitable threading library. config.log says: configure:19993: checking pthread.h usability configure:20005: cc -c -g -I/local/include -I/local/gnu/include conftest.c >&5 cc: Error: /usr/include/pthread.h, line 1251: #error "Please compile the module including pthread.h with -pthread" (errormessage) due to this snippet of pthread.h: # ifndef _REENTRANT # error "Please compile the module including pthread.h with -pthread" # endif ./configure CC="cc -pthread" works. Not sure how to deal with that one. Seems a bit excessive to run all the OL_PTHREAD_TRY()s _before_ detecting that the system has pthread. Maybe write a special case, like try for pthread.h with -D_REENTRANT if not found without that?

1 0

Re: (ITS#5016) slapd generates unjustified error 3 (Time Limit Exceeded) at checkpoint time
by ali.pouya＠free.fr 15 Jun '07

15 Jun '07

pierangelo.masarati(a)sys-net.it wrote : > Would it be possible to get, from the consumer's log, what was the > actually requested time limit in those cases? This means: track down > what connection/operation was concluded by a "Time Limit Exceeded" > response; then find out the corresponding request, and see what was the > requested time limit. You need "args" debug level for this purpose, and > you need to look at the second of the three numbers that end the SRCH > line in the logs; for example: Hi Pierangelo; The problem came from my LDAP client which specified timelimit=1. I repaired the client and everything works fine since several hours :-) Thanks for your help and sorry for wasting your time. For me the ITS is to be closed (the error "Time Limit Exceeded" produced for syncrepl connection every 3600 seconds does not bother me). Best regards Ali

1 0

Re: memory leak (ITS#5018)
by niloulili＠hotmail.com 15 Jun '07

15 Jun '07

OK,I've download release 2.3.32,after removing and test ,i'll report whether problem still exits. Thank you so much. best regards nina >From: Pierangelo Masarati <openldap-its(a)OpenLDAP.org> >To: niloulili(a)hotmail.com >Subject: Re: memory leak (ITS#5018) >Date: Thu, 14 Jun 2007 08:13:11 GMT > >OpenLDAP 2.2.19 (and OpenLDAP 2.2) has been abandoned long ago, so it is no >longer maintained. Please upgrade to a recent version and check if the problem >persists. Otherwise this ITS will be closed. > >p. _________________________________________________________________ ÓëÁª»úµÄÅóÓÑœøÐÐœ»Á÷£¬ÇëÊ¹ÓÃ MSN Messenger: http://messenger.msn.com/cn

1 0

Re: (ITS#4995) SampleLDAP.pm w/back_perl appears to be broken
by rra＠stanford.edu 15 Jun '07

15 Jun '07

Quanah Gibson-Mount <quanah(a)zimbra.com> writes: > --On Saturday, June 02, 2007 4:43 AM +0000 rra(a)stanford.edu wrote: >> While investigating another issue with back_perl, I tried to use the >> SampleLDAP.pm module that comes with the OpenLDAP source. I added the >> following to my slapd.conf: >> database perl >> suffix "o=AnyOrg,c=US" >> perlModulePath /home/eagle/SampleLDAP.pm >> perlModule SampleLDAP [...] > database perl > suffix "o=AnyOrg,c=US" > perlModulePath /usr/local/etc/openldap > perlModule SampleLDAP I detect an intriguing difference in our configurations. I was misled by this comment in SampleLDAP.pm: # Usage: Add something like this to slapd.conf: # # database perl # suffix "o=AnyOrg,c=US" # perlModulePath /path/to/this/file # perlModule SampleLDAP The man page is more accurate. This was apparently actually a minor bug in the comments. :) -- Russ Allbery (rra(a)stanford.edu) <http://www.eyrie.org/~eagle/>

1 0

Re: (ITS#4995) SampleLDAP.pm w/back_perl appears to be broken
by quanah＠zimbra.com 15 Jun '07

15 Jun '07

--On Saturday, June 02, 2007 4:43 AM +0000 rra(a)stanford.edu wrote: > Full_Name: Russ Allbery > Version: 2.3.35 > OS: Debian > URL: > Submission from: (NULL) (171.66.157.14) > > > While investigating another issue with back_perl, I tried to use the > SampleLDAP.pm module that comes with the OpenLDAP source. I added the > following to my slapd.conf: > > moduleload back_perl > ># ... > > database perl > suffix "o=AnyOrg,c=US" > perlModulePath /home/eagle/SampleLDAP.pm > perlModule SampleLDAP > > The result of slapd -d 1 is: > ... > WARNING: No dynamic config support for database perl. > config_build_entry: "olcDatabase={2}perl" > backend_startup_one: starting "dc=Stanford,dc=EDU" > bdb_db_open: unclean shutdown detected; attempting recovery. > bdb_db_open: dbenv_open(/var/lib/ldap) > backend_startup_one: starting "o=AnyOrg,c=US" > Can't call method "init" on an undefined value. Using the SampleLDAP perl module supplied with the OpenLDAP source works just fine for me on Stanford's LDAP servers. ldap-uat00:/usr/local/etc/openldap# more slapd.conf # # See slapd.conf(5) for details on configuration options. # This file should NOT be world readable. # include /usr/local/etc/openldap/schema/core.schema include /usr/local/etc/openldap/schema/cosine.schema include /usr/local/etc/openldap/schema/inetorgperson.schema loglevel 0 threads 8 password-hash {CLEARTEXT} # Define global ACLs to disable default read access. pidfile /var/run/slapd.pid argsfile /var/run/slapd.args # # Load dynamic backend modules: # Note: back-null is statically-linked. modulepath /usr/local/lib/openldap moduleload back_perl.la access to dn="" by * read access to * by anonymous read by users read by self write # if no access controls are present, the default policy is: # Allow read by all # # rootdn can always write! tool-threads 2 ####################################################################### # perl database definitions ####################################################################### database perl suffix "o=AnyOrg,c=US" perlModulePath /usr/local/etc/openldap perlModule SampleLDAP Output from slapd -d -1 slapd startup: initiated. backend_startup_one: starting "cn=config" config_back_db_open config_build_entry: "cn=config" config_build_entry: "cn=include{0}" config_build_entry: "cn=include{1}" config_build_entry: "cn=include{2}" config_build_entry: "cn=module{0}" config_build_entry: "cn=schema" config_build_entry: "cn={0}core" config_build_entry: "cn={1}cosine" config_build_entry: "cn={2}inetorgperson" config_build_entry: "olcDatabase={-1}frontend" config_build_entry: "olcDatabase={0}config" WARNING: No dynamic config support for database perl. config_build_entry: "olcDatabase={1}perl" backend_startup_one: starting "o=AnyOrg,c=US" slapd starting daemon: added 4r listener=(nil) daemon: added 7r listener=0x6010e0 daemon: epoll: listen=7 active_threads=0 tvp=NULL daemon: activity on 1 descriptor daemon: activity on: daemon: epoll: listen=7 active_threads=0 tvp=NULL So I am unable to reproduce this issue. --Quanah -- Quanah Gibson-Mount Principal Software Engineer Zimbra, Inc -------------------- Zimbra :: the leader in open source messaging and collaboration

1 0

Re: (ITS#4943) tpool.c pause vs. finish
by hyc＠symas.com 15 Jun '07

15 Jun '07

h.b.furuseth(a)usit.uio.no wrote: > Howard Chu writes: >> Hallvard B Furuseth wrote: >>> hyc(a)symas.com writes: >>>> h.b.furuseth(a)usit.uio.no wrote: >>>>> * When a thread is finishing, make it go active for context_reset(). >>>>> Should make slapi module destructors safer, and I don't see that it >>>>> can hurt. >>>> I don't understand this. >>> Let me dig a bit back in the ITS... >>> "context_reset() can call connection_fake_destroy(), which via >>> slapi_int_free_object_extensions() calls slapi module destructors, >>> which can do who-knows-what." >> context_reset() can only be called from the main thread. It can (must) >> never be called by anything running from the pool. > > It's called from pool_wrapper(). pool_wrapper() could go active so > there can be no pause while that context_reset() call is running. Oh, ok. This is pretty much a non-issue because threads in the pool stay live until slapd shuts down. The one exception is for a cn=config modify that decreases the size of the pool to below the number of currently active threads, in which case some number of threads will exit immediately. I don't see any potential for conflict here. >>>>> * Scheduling: If several threads call pool_pause(), (...) > > (need to check out how it should work...) > >>>>> - pool_context() breaks if several ldap_pvt_thread_t bit patterns can >>>>> represent the same thread ID: TID_HASH() would give different hashes >>>>> for the same thread, and pool_context() stops searching when it hits >>>>> a slot with ctx == NULL. (My previous bug report was a bit wrong.) >>>> How can a single thread ID be represented by multiple bit patterns? >>> A struct/union with padding bytes seems the least unlikely possibility. > > Note that I did say "least unlikely" rather than "most likely": > It's not that I expect to encounter it, more that I'd prefer not to be > surprised in the form of a slapd malfuntion. > > So in that respect, my preference (not for RE23) is to cast to an > integer for the hash, and also to add pthread_<set/get>specific() so > thread_keys[] and its hash will only be a fallback solution. Casting to an int only works with simple types, the point of using the hash was to provide a solution that works for both simple and structured thread IDs. If you want to #ifdef the code so the two cases are handled differently, then just get rid of TID_HASH for the integral case. I'm still leary of the pthread TLS support, and making that change will require us to update all of the other thread package support, some of which I don't have access to build/test any more (e.g. SunOS4 LWP). >>>> The best fix may be to just use the address of the thread's stack as the >>>> thread ID. That's actually perfect for our purpose. >>> How does a function called from somewhere inside the thread know that >>> address? That's almost what the user context is, and thus what >>> thread_keys[] maps the thread ID to. >> It requires some degree of machine-dependence, which is why I never >> bothered to code it. The principle is simple though - all of our thread >> stacks are some multiple of 1MB in size. Take the address of any local >> variable, mask off the low 20 bits, and you have a unique thread ID (+/- >> some additional masking/shifting based on the actual thread stack size). > > I'm not sure how to determine _which_ multiple of 1MB - start two > threads and compare their stack addresses, maybe? In any case, I > agree it sounds rather more machine-dependent than the current code. That's what the LDAP_PVT_THREAD_STACK_SIZE macro tells you. It's really not hard. If we were to disallow increasing the number of threads at runtime, we could simply allocate a block of thread stacks all at once, which would then allow our thread IDs to be simple integers from 0-N. -- -- Howard Chu Chief Architect, 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#5019) slapd: ldbm/gdbm, cache.c core dump
by quanah＠zimbra.com 15 Jun '07

15 Jun '07

--On Thursday, June 14, 2007 8:59 PM +0000 asedlack(a)mailfoundry.com wrote: > Full_Name: Aron Sedlack > Version: 2.3.35 > OS: Linux > URL: ftp://ftp.openldap.org/incoming/ > Submission from: (NULL) (66.18.18.14) > LDBM is deprecated, and has been removed from the source tree. Bugs against LDBM will not be fixed, because of its inherent flaws. Upgrade your configuration to use one of the supported database mechanisms, back-bdb or back-hdb. :) --Quanah -- Quanah Gibson-Mount Principal Software Engineer Zimbra, Inc -------------------- Zimbra :: the leader in open source messaging and collaboration

1 0

Re: (ITS#5019) slapd: ldbm/gdbm, cache.c core dump
by hyc＠symas.com 15 Jun '07

15 Jun '07

asedlack(a)mailfoundry.com wrote: > Full_Name: Aron Sedlack > Version: 2.3.35 > OS: Linux > URL: ftp://ftp.openldap.org/incoming/ > Submission from: (NULL) (66.18.18.14) > > > Platform: Linux, OpenLDAP-2.3.35 > Compiled with: ./configure --enable-dynamic --enable-wrappers --enable-bdb=no > --enable-hdb=no --enable-ldbm --enable-ldbm-api=gdbm --with-threads --with-tls > --with-threads=no > gcc version 3.3.4, gdbm 1.8.3, OpenSSL 0.9.8e > > slapd core dumps with a corrupted stack, SIGABRT. > slapd: cache.c:111: cache_return_entry_rw: Assertion `e->e_private != (( void > *)0)' failed.. > > Happens every time ldif is loaded... > $ ldapmodify -a -f ./mf.ldif -D "cn=Root,dc=mf" -w secret > adding new entry "dc=mf" > > adding new entry "dc=iana,dc=mf" > ldap_result: Can't contact LDAP server (-1) 1) ldbm is deprecated, don't use it. 2) if you insist on using it, get a debug stack trace for the abort 3) note that ldbm is still tested regularly in the 2.3 builds, and no one else has reported this occurrence, so there's probably something odd in your configuration. Providing your slapd.conf might help. But the ldbm code has been removed for 2.4; support for it is disappearing fast. -- -- Howard Chu Chief Architect, 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#4837) SunLDAP to OpenLDAP migration problem
by quanah＠zimbra.com 15 Jun '07

15 Jun '07

--On Thursday, June 14, 2007 10:02 PM +0000 h.b.furuseth(a)usit.uio.no wrote: > Quanah Gibson-Mount writes: >> It should be as simple as changing: >> passwd.c:#define SALT_SIZE 4 >> to >> passwd.c:#define SALT_SIZE 8 > > I don't get this. I don't know ssha1, but... Right, see my follow-up. I had the wrong string in my data when I did a cut and paste. ;) It actually works as it should. --Quanah -- Quanah Gibson-Mount Principal Software Engineer Zimbra, Inc -------------------- Zimbra :: the leader in open source messaging and collaboration

1 0

Re: (ITS#4837) SunLDAP to OpenLDAP migration problem
by h.b.furuseth＠usit.uio.no 15 Jun '07

15 Jun '07

Quanah Gibson-Mount writes: > It should be as simple as changing: > passwd.c:#define SALT_SIZE 4 > to > passwd.c:#define SALT_SIZE 8 I don't get this. I don't know ssha1, but... That's for generating ssha1 hashes in hash_ssha1(), it is not used for decoding them in chk_ssha1() - which I assume is what he needs when moving _to_ OpenLDAP. chk_ssha1() looks independent of salt size - it base64-decodes the provided salt+hash and finds expects the salt to start at position LUTIL_SHA1_BYTES (from include/lutil_sha1.h) in that string. -- Regards, Hallvard

1 0

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

openldap-bugs