openldap-bugs

openldap-bugs@openldap.org

1 participants
20959 discussions

(ITS#4960) the memory increase quickly and not can be released sometime.
by hoverwf＠126.com 14 May '07

14 May '07

Full_Name: wang fei Version: OpenLDAP 2.3.21 OS: slackware URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (220.167.25.214) descirption: i use the following code to get the info of the entry whose DN matches "search dn". the problem: when i call this function many times(eg: more then 1000 times), the result will be correct, but for about one or two times, after i call ldap_search_ext_s(). the memory will increase dramitically (usually 128K, i use system("ps aux | grep /myprogram") to find the memory it is used). and when i ldap_msgfree(res). it only 4K memory is released. but the other 998 times does not has this problem(the memory will not increase). All these nodes have similar attribute except dn and cn. when i disable the code of the inner for loop. this problem appear less frequently. when i disable the code which get the attribute value of entry, in other word, both the for loop. this problem seems disappeared, but it maybe it will appear again if it is runed more times. // portion code of the program static int search_node_bydn(char *search_dn) { int ret; char *a = NULL, *attrs[10], *dn; char filter[1024]; LDAPMessage *e=NULL, *res = NULL; LDAP *ld = NULL; struct timeval timeout; // open the connection... // bind ... // then search the node.... attrs[0] = "objectGUID"; attrs[1] = "modifyTimeStamp"; attrs[2] = "cn"; attrs[3] = "sAMAccountName"; attrs[4] = "objectClass"; attrs[5] = "name"; attrs[6] = NULL; snprintf(filter, 1024, "(objectClass=*)"); timeout.tv_sec = 1000; system("ps aux | grep /myprogram"); ret = ldap_search_ext_s(ld, search_dn, LDAP_SCOPE_BASEOBJECT,filter, attrs, 0, NULL, NULL, &timeout, 0, &res); if (ret != LDAP_SUCCESS) { printf("search node %s error: %s\n", search_dn, ldap_err2string(ret)); ldap_msgfree(res); ldap_unbind_ext(ld, NULL, NULL); return (-1); } system("ps aux | grep /myprogram"); #if 1 // get the attribute value of entry. for (e = ldap_first_entry(ld, res); e != NULL; e = ldap_next_entry(ld, e)) { #if 1 BerElement *ptr = NULL; for (a = ldap_first_attribute(ld, e, &ptr); a != NULL; a = ldap_next_attribute(ld, e, ptr)) { // do sth with the attribute. }// inner for loop if(ptr != NULL) { ber_free(ptr,0); } #endif }// outer for loop #endif system("ps aux | grep /myprogram"); ldap_msgfree(res); res = NULL; system("ps aux | grep /myprogram"); ldap_unbind_ext(ld, NULL, NULL); return OK; }

1 0

(ITS#4959) replica seg faults if syncrepl searchbase =""
by ali.pouya＠free.fr 14 May '07

14 May '07

Full_Name: Ali Pouya Version: 2.4.4alpha OS: Linux RedHat AS4 (kernel 2.6) URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (145.242.3.30) I'm testing OpenLdap 2.4.4alpha for future use. I have a master and a replica. In the replica's syncrepl configuration has searchbase="" then the replica seg faults after connecting to the master. The core backtrace shows very little information : (gdb) bt #0 0x00179d5a in strcmp () from /lib/tls/libc.so.6 #1 0x08068ede in ?? () #2 0x098c0d50 in ?? () #3 0x00000000 in ?? () (gdb) Below I add the end of the slapd detailed log. I can send any other information required. Thanks and best regards Ali Pouya Log extract : ** ld 0x991dcf8 Outstanding Requests: * msgid 1, origid 1, status InProgress outstanding referrals 0, parent count 0 ld 0x991dcf8 request count 1 (abandoned 0) ** ld 0x991dcf8 Response Queue: Empty ld 0x991dcf8 response count 0 ldap_chkResponseList ld 0x991dcf8 msgid 1 all 1 ldap_chkResponseList returns ld 0x991dcf8 NULL ldap_int_select read1msg: ld 0x991dcf8 msgid 1 all 1 ber_get_next ldap_read: want=8, got=8 0000: 30 0c 02 01 01 61 07 0a 0....a.. ldap_read: want=6, got=6 0000: 01 00 04 00 04 00 ...... ber_get_next: tag 0x30 len 12 contents: ber_dump: buf=0x099270b8 ptr=0x099270b8 end=0x099270c4 len=12 0000: 02 01 01 61 07 0a 01 00 04 00 04 00 ...a........ read1msg: ld 0x991dcf8 msgid 1 message type bind ber_scanf fmt ({eAA) ber: ber_dump: buf=0x099270b8 ptr=0x099270bb end=0x099270c4 len=9 0000: 61 07 0a 01 00 04 00 04 00 a........ read1msg: ld 0x991dcf8 0 new referrals read1msg: mark request completed, ld 0x991dcf8 msgid 1 request done: ld 0x991dcf8 msgid 1 res_errno: 0, res_error: <>, res_matched: <> ldap_free_request (origid 1, msgid 1) ldap_free_connection 0 1 ldap_free_connection: refcnt 1 ldap_parse_result ber_scanf fmt ({iAA) ber: ber_dump: buf=0x099270b8 ptr=0x099270bb end=0x099270c4 len=9 0000: 61 07 0a 01 00 04 00 04 00 a........ ber_scanf fmt (}) ber: ber_dump: buf=0x099270b8 ptr=0x099270c4 end=0x099270c4 len=0 ldap_msgfree Erreur de segmentation (core dumped)

1 0

(ITS#4958) slapd segfaults when overlay rwm, suffixmassage is used in conjunction with empty suffix
by nvoutsin＠noc.uoa.gr 14 May '07

14 May '07

Full_Name: Nikos Voutsinas Version: 2.3.35 OS: Solaris URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (195.134.100.39) As ando already said: .....it tries to lookup a database to relay for when unbinding, but unbind has no DN, so a strcmp on NULL is performed. This does not happen when using the "relay" directive because relay database selection does not occur for each operation.... configuration example: database bdb suffix "dc=real,dc=naming,dc=context" .... .... .... database relay suffix "" overlay rwm suffixmassage "dc=real,dc=naming,dc=context"

1 0

Re: (ITS#4930) slaptest should be quiet on success
by jsafrane＠redhat.com 14 May '07

14 May '07

On Fri, 2007-05-11 at 22:07 +0200, Pierangelo Masarati wrote: > jsafranek(a)redhat.com wrote: > > > The 'slaptest' tool is a bit verbose, it sends 'config file testing succeeded' > > to stderr. IMHO it should do not output anything, especially to stderr, if > > everything is all right. > > > > Here is a small patch, causing the slaptest to display the aforementioned > > message only if -v switch is used: > > Your issue may make sense in some cases, but I'd rather reverse its > logic and avoid printing any message only when explicitly requested to > be "quiet" (e.g. adding a -Q switch?) Why not, I have basically nothing against -Q switch, but it would require a bit more changes in the current sources. I just needed something quick-and-not-so-dirty. Jan

1 0

Re: (ITS#4951) [contrib] RADIUS password module fixes
by ando＠sys-net.it 13 May '07

13 May '07

richton(a)nbcs.rutgers.edu wrote: > * libradius makes use of MT-Unsafe calls, so a protecting mutex is added. applied to HEAD > * config_filename could be passed to rad_config without initialization (when > accepting the default). rejected: global variables are always zeroed. Please test. Thanks, p. Ing. Pierangelo Masarati OpenLDAP Core Team SysNet s.r.l. via Dossi, 8 - 27100 Pavia - ITALIA http://www.sys-net.it --------------------------------------- Office: +39 02 23998309 Mobile: +39 333 4963172 Email: pierangelo.masarati(a)sys-net.it ---------------------------------------

1 0

Re: (ITS#4957) destroying uninitialized mutexed after failed startup
by ando＠sys-net.it 13 May '07

13 May '07

h.b.furuseth(a)usit.uio.no wrote: > (I haven't committed to non-HEAD for ages, I don't rememer if I > just commit it or if there are more formalities involved?) Commit; if appropriate, note in CHANGES. Someone else (the Chief Architect) will move tags. p. Ing. Pierangelo Masarati OpenLDAP Core Team SysNet s.r.l. via Dossi, 8 - 27100 Pavia - ITALIA http://www.sys-net.it --------------------------------------- Office: +39 02 23998309 Mobile: +39 333 4963172 Email: pierangelo.masarati(a)sys-net.it ---------------------------------------

1 0

(ITS#4957) destroying uninitialized mutexed after failed startup
by h.b.furuseth＠usit.uio.no 13 May '07

13 May '07

Full_Name: Hallvard B Furuseth Version: RE23 OS: URL: http://www.openldap.org/devel/cvsweb.cgi/servers/slapd/schema_init.c.diff?r… Submission from: (NULL) (129.240.202.105) Submitted by: hallvard If RE23 startup fails, ad_undef_mutex and oc_undef_mutex can be destroyed without having been initialized. Thus slapd can crash. Fix: schema_init.c rev 1.388. (I haven't committed to non-HEAD for ages, I don't rememer if I just commit it or if there are more formalities involved?)

1 0

Re: (ITS#4943) tpool.c pause vs. finish
by h.b.furuseth＠usit.uio.no 12 May '07

12 May '07

hyc(a)symas.com writes: > h.b.furuseth(a)usit.uio.no wrote: >> - TID_HASH() fails if several ldap_pvt_thread_t bit patterns can >> represent the same thread ID, e.g. if it is a struct/integer type with >> padding bytes/bits. >> > That doesn't matter, since the table will use linear probing to compare > thread IDs. Ah, it works when creating new threads. But not in pool_context(), which stops searching when it hits an unused slot (thread ID tid_zero). -- Regards, Hallvard

1 0

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

12 May '07

h.b.furuseth(a)usit.uio.no wrote: > h.b.furuseth(a)usit.uio.no writes: >> Howard Chu writes: >>> Since there is only one thread pool in use, it is impossible for another >>> thread to be active. >> No. Though it's true that my concern above was wrong. >> >> It is "ltp_active_count--" which triggers the start of a pause. (...) > > Sorry again, I was confusing 3 problems after two long days. It's the > active (unpaused) thread which would be calling _context() of course. > > In any case, thank you for the reply. I know what to test now... > > > Another problem, which I think I'm repeating from an earlier discussion: > > - TID_HASH() fails if several ldap_pvt_thread_t bit patterns can > represent the same thread ID, e.g. if it is a struct/integer type with > padding bytes/bits. > That doesn't matter, since the table will use linear probing to compare thread IDs. -- -- 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#4943) tpool.c pause vs. finish
by h.b.furuseth＠usit.uio.no 12 May '07

12 May '07

h.b.furuseth(a)usit.uio.no writes: >Howard Chu writes: >> Since there is only one thread pool in use, it is impossible for another >> thread to be active. > > No. Though it's true that my concern above was wrong. > > It is "ltp_active_count--" which triggers the start of a pause. (...) Sorry again, I was confusing 3 problems after two long days. It's the active (unpaused) thread which would be calling _context() of course. In any case, thank you for the reply. I know what to test now... Another problem, which I think I'm repeating from an earlier discussion: - TID_HASH() fails if several ldap_pvt_thread_t bit patterns can represent the same thread ID, e.g. if it is a struct/integer type with padding bytes/bits. It might be better to let TID_HASH cast the ID to an unsigned integer type and hash that. Then it won't compile if ldap_pvt_thread_t is a struct, so we get a warning in _some_ cases when it can break. -- 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