openldap-bugs

openldap-bugs@openldap.org

1 participants
20953 discussions

Re: (ITS#4773) syncrepl segfault with incorrect config
by adrian＠smop.co.uk 10 Dec '06

10 Dec '06

On Sat, Dec 9, 2006 at 22:29:50 +0100 (+0100), Pierangelo Masarati wrote: > It is already fixed in HEAD; fixing it in re23 might be too > difficult to consider, so, since the correct behavior is clearly > documented, it might be not worth the effort. Fair enough, I'm sure I searched through the bugs for syncrepl items and didn't see anything, but I guess it was fixed outside of a bug report which would explain it. Many thanks, Adrian -- Adrian Bridgett - adrian(a)smop.co.uk GPG key available on public key servers

1 0

Re: (ITS#4773) syncrepl segfault with incorrect config
by ando＠sys-net.it 09 Dec '06

09 Dec '06

adrian(a)smop.co.uk wrote: > Trying to add or delete entries with syncrepl overlay I was getting segfaults. > > I couldn't check against my test box (remote location, no power), but eventually > came across: > http://www.mail-archive.com/openldap-software@openldap.org/msg06772.html > > This was in fact the problem I had too - I had specified syncrepl early on > rather than after the database definition. Moving syncrepl into the correct > place fixed it. > > Two hours wasted trying to figure out what was wrong, it would be good to have > some error message in this case :-) > It is already fixed in HEAD; fixing it in re23 might be too difficult to consider, so, since the correct behavior is clearly documented, it might be not worth the effort. p.

1 0

(ITS#4773) syncrepl segfault with incorrect config
by adrian＠smop.co.uk 08 Dec '06

08 Dec '06

Full_Name: Adrian Bridgett Version: 2.3.29 OS: Linux (Debian) URL: Submission from: (NULL) (81.5.177.202) Trying to add or delete entries with syncrepl overlay I was getting segfaults. I couldn't check against my test box (remote location, no power), but eventually came across: http://www.mail-archive.com/openldap-software@openldap.org/msg06772.html This was in fact the problem I had too - I had specified syncrepl early on rather than after the database definition. Moving syncrepl into the correct place fixed it. Two hours wasted trying to figure out what was wrong, it would be good to have some error message in this case :-) The stack traces I got out weren't terribly helpful to me (from a debug build of 2.3.27 running on Debian sarge all up to date): #0 0xa7f3501f in lutil_debug (debug=255, level=4, fmt=0x4 <Address 0x4 out of bounds>) at /home/autobuild/builds/openldap2.3/openldap-2.3.27/libraries/liblber/debug.c:63 #1 0x0807f71b in fe_op_modify () #2 0x0807f0f5 in fe_op_modify () (repeat of #2) #939 0x0807f0f5 in fe_op_modify () #940 0x0807f0f5 in fe_op_modify () #941 0x0807f0f5 in fe_op_modify () #942 0x080bf2fa in overlay_op_walk () #943 0x080bf3fd in overlay_op_walk () #944 0x080bf531 in overlay_op_walk () #945 0x0807e900 in do_modify () #946 0x0806960f in connection_done () #947 0xa7f46c28 in ldap_int_thread_pool_wrapper (xpool=0x24) at /home/autobuild/builds/openldap2.3/openldap-2.3.27/libraries/libldap_r/tpool.c:478 #948 0xa7d51b63 in start_thread () from /lib/tls/libpthread.so.0 #949 0xa7ce018a in clone () from /lib/tls/libc.so.6 #0 0x0806fca8 in fe_op_add () #1 0x0806ff58 in fe_op_add () (repeat of #1) #11378 0x0806ff58 in fe_op_add () #11379 0x080bf2fa in overlay_op_walk () #11380 0x080bf3fd in overlay_op_walk () #11381 0x080bf591 in overlay_op_walk () #11382 0x0806f7af in do_add () #11383 0x0806960f in connection_done () #11384 0xa7f23c28 in ldap_int_thread_pool_wrapper (xpool=0x26) at /home/autobuild/builds/openldap2.3/openldap-2.3.27/libraries/libldap_r/tpool.c:478 #11385 0xa7d2eb63 in start_thread () from /lib/tls/libpthread.so.0 #11386 0xa7cbd18a in clone () from /lib/tls/libc.so.6 Please shout if you want any more info. Thanks for a great product, Adrian

1 0

(ITS#4772) SEGV during DEL/syncprov_qtask
by richton＠nbcs.rutgers.edu 07 Dec '06

07 Dec '06

Full_Name: Aaron Richton Version: 2.3.30 OS: Solaris 9 URL: https://www.nbcs.rutgers.edu/~richton/richton-20061208-segv.txt Submission from: (NULL) (68.196.250.61) I realize I've already got #4723 open as "no idea why this is SEGV," but this trace looked notably different, so I'm filing separate. I'm going to continue debugging along the lines of #4723, which was leaning towards OpenSSL. But if anything jumps out at somebody from this trace, feel free to speak up. As it turns out, this was near a batch of a large number of DELs. Might be good to take a glance through slog or similar and see if a memory debugger comes up clean, especially with deletes...

1 0

Re: (ITS#4770) monitoringslapd.sdf patch
by ghenry＠suretecsystems.com 07 Dec '06

07 Dec '06

<quote who="Howard Chu"> > ghenry(a)suretecsystems.com wrote: >> Full_Name: Gavin Henry >> Version: 2.3.30 >> OS: FC6 >> URL: http://www.suretecsystems.com/our_docs/admin-guide-monitoring.patch >> Submission from: (NULL) (212.159.59.85) >> >> >> Hi all, >> >> Monitoring section updated. Please review and provide feedback. >> >> Thanks, >> >> Gavin. >> >> (http://www.suretecsystems.com/our_docs/admin-guide-monitoring.patch) >> > At the moment the only comment I have is regarding back-monitor itself, > not the doc: I question the decision to define the monitor info > attributes as operational instead of user attributes. Requiring the use > of "+" to return all of the monitored info seems pretty unfriendly, > particularly since it causes the return of actual operational attributes > that are completely irrelevant to the purpose of monitoring. I.e., the > monitor info should be considered to be dynamically generated user > attributes, not operational attributes. OK. So what would be the next step, re-work it? Just let me know the changes so I can document them. There's nothing like documenting a moving target! ;-) Gavin. -- Kind Regards, Gavin Henry. Managing Director. T +44 (0) 1224 279484 M +44 (0) 7930 323266 F +44 (0) 1224 824887 E ghenry(a)suretecsystems.com Open Source. Open Solutions(tm). http://www.suretecsystems.com/

1 0

Re: (ITS#4770) monitoringslapd.sdf patch
by hyc＠symas.com 07 Dec '06

07 Dec '06

ghenry(a)suretecsystems.com wrote: > Full_Name: Gavin Henry > Version: 2.3.30 > OS: FC6 > URL: http://www.suretecsystems.com/our_docs/admin-guide-monitoring.patch > Submission from: (NULL) (212.159.59.85) > > > Hi all, > > Monitoring section updated. Please review and provide feedback. > > Thanks, > > Gavin. > > (http://www.suretecsystems.com/our_docs/admin-guide-monitoring.patch) > At the moment the only comment I have is regarding back-monitor itself, not the doc: I question the decision to define the monitor info attributes as operational instead of user attributes. Requiring the use of "+" to return all of the monitored info seems pretty unfriendly, particularly since it causes the return of actual operational attributes that are completely irrelevant to the purpose of monitoring. I.e., the monitor info should be considered to be dynamically generated user attributes, not operational attributes. -- -- Howard Chu Chief Architect, Symas Corp. http://www.symas.com Director, Highland Sun http://highlandsun.com/hyc OpenLDAP Core Team http://www.openldap.org/project/

1 0

(ITS#4771) Memory Leak in connection.c
by marco.dettorre＠sys-net.it 07 Dec '06

07 Dec '06

Full_Name: Marco D'Ettorre Version: HEAD OS: Linux URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (212.214.117.67) There is a memory leak in connection_op_queue (servers/slapd/connection.c +1821). A fix for this: --- servers/slapd/connection.c.orig 2006-12-07 18:30:14.000000000 +0100 +++ servers/slapd/connection.c 2006-12-07 19:07:09.000000000 +0100 @@ -1751,6 +1751,9 @@ { op->o_conn->c_sasl_bindop = NULL; + ch_free( op->o_callback ); + op->o_callback = NULL; + return SLAP_CB_CONTINUE; } Regards Marco

1 0

(ITS#4770) monitoringslapd.sdf patch
by ghenry＠suretecsystems.com 07 Dec '06

07 Dec '06

Full_Name: Gavin Henry Version: 2.3.30 OS: FC6 URL: http://www.suretecsystems.com/our_docs/admin-guide-monitoring.patch Submission from: (NULL) (212.159.59.85) Hi all, Monitoring section updated. Please review and provide feedback. Thanks, Gavin. (http://www.suretecsystems.com/our_docs/admin-guide-monitoring.patch) -- Kind Regards, Gavin Henry. Managing Director. T +44 (0) 1224 279484 M +44 (0) 7930 323266 F +44 (0) 1224 824887 E ghenry(a)suretecsystems.com Open Source. Open Solutions(tm). http://www.suretecsystems.com/

1 0

freeing mem from ldap_parse_result
by Dale Moore 06 Dec '06

06 Dec '06

I'm trying to write exceptionally correct code with no memory leaks. I'm calling ldap_parse_result(3). And of course one of the parameters is char ***referalsp; The documentation says to free the memory allocated to this data structure by calling the routine ldap_value_free(). But the routine ldap_value_free() is deprecated. My options are - Compile with -DLDAP_DEPRECATED = I hate to create software using deprecated API - Call ber_memvfree((void **)) instead of ldap_value_free() - Use a different mechanism to parse the message The bug I'm reporting here is - a problem with the documentation or - in the premature deprecation of ldap_value_free or - the lack of deprecation of ldap_parse_ressult() I'm not sure which. Looking for advice. Dale Moore

2 1

Re: ITS#3812 database config documentation
by raphael.ouazana＠linagora.com 06 Dec '06

06 Dec '06

On Jeu 16 novembre 2006 12:09, hyc(a)symas.com wrote: > I've committed a preliminary slapd-config.5 manpage to HEAD. In > anticipation of deleting slurpd from RE24, I have commented out all of > the slurpd-related keywords. Most of the text is the same as in > slapd.conf(5) but I've changed the organization to better reflect the > actual implementation. > > There may be options that I've missed. Please review and send patches / > corrections / comments. Thank you very much for this work. I've only some comments. Even if it is shown in the Examples part, I think the use of slapd.conf and slapd.d at the same time should be explained as it is in slapd(8). Furthermore slapd-config(5) make references to slapd-bdb(5), slapd-ldap(5) and others but these pages use old config style. Maybe you could add in a first time a note to indicate that users should add olc prefix to use these directives in cn=config branch. Of course I hope every pages will be updated one day... Raphael Ouazana. PS: I'm not able to see slapd-config(5) with man.cgi on the website (even if I use OpenLDAP 2.X-Devel). Is it normal ?

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