(ITS#6038) Write slapadd progress meter to stdout
by rein@OpenLDAP.org
Full_Name: Rein Tollevik
Version: CVS HEAD
OS: Irrelevant
URL:
Submission from: (NULL) (84.215.36.97)
Submitted by: rein
The slapadd progress meter is written to stderr, and the only way to get rid of
it is currently to redirect stderr. I don't want the meter in my small test
scripts, as it is not very useful on minimal input and clutters the test output.
It should be possible to disable the meter without loosing all error messages,
a fix that writes the meter to stdout instead is coming.
Options to enable/disable the meter would be nice, but the obvious candidates -q
and -v are both occupied...
Rein Tollevik
Basefarm AS
12 years
(ITS#6037) errno in signal handlers
by h.b.furuseth@usit.uio.no
Full_Name: Hallvard B Furuseth
Version: HEAD, RE24
OS:
URL:
Submission from: (NULL) (129.240.6.233)
Submitted by: hallvard
Signal handlers slapd/daemon.c:slap_sig_shutdown()/slap_sig_wake() need
to save/restore errno, since they call functions that can modify errno.
And/or possibly they need sock_errno() - sock_errset() from ac/socket.h,
since they use tcp_write()? I don't know if that's safe inside signal
handlers, or if Windows itself saves/restores this code around signal
handlers.
slapd/main.c:wait4child() can loop forever after EINTR, since it checks
for errno even when the waitpid returns 0. I don't know if there is
a good reason it does that. Some of the commits have my name on them
but I think I copied it from elsewhere.
Anyway, I'm doing the minimal changes now: save/restore errno, and
set errno=0 in each loop iteration instead of before the loop.
Anyone with better ideas can take it from there.
12 years
Re: (ITS#6035) slapd requires restart after modifying olcAuthzRegexp
by ando@sys-net.it
quanah(a)zimbra.com wrote:
> --On Thursday, March 26, 2009 4:14 PM +0000 hyc(a)symas.com wrote:
>
>> This is a known limitation in authz regexp support. There are no plans
>> to change this any time soon.
>
> Where's this limitation documented? What other parameters in the config
> backend have the same flaw? We've certainly fixed this for a number of
> other things.
Indeed, it has been finally, although rather inelegantly, fixed in
slapo-rwm(5), AFAIR.
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
Fax: +39 0382 476497
Email: ando(a)sys-net.it
-----------------------------------
12 years
Re: (ITS#6035) slapd requires restart after modifying olcAuthzRegexp
by quanah@zimbra.com
--On Thursday, March 26, 2009 4:14 PM +0000 hyc(a)symas.com wrote:
> This is a known limitation in authz regexp support. There are no plans
> to change this any time soon.
Where's this limitation documented? What other parameters in the config
backend have the same flaw? We've certainly fixed this for a number of
other things.
I don't even see authz-regexp/olcAuthzRegexp mentioned in chapters 5 or 6
in the admin guide, and the man pages don't note this limitation.
--Quanah
--
Quanah Gibson-Mount
Principal Software Engineer
Zimbra, Inc
--------------------
Zimbra :: the leader in open source messaging and collaboration
12 years
Re: (ITS#6035) slapd requires restart after modifying olcAuthzRegexp
by hyc@symas.com
This is a known limitation in authz regexp support. There are no plans
to change this any time soon.
On Thu, Mar 26, 2009 at 03:33:37AM +0000, dgbaley27(a)verizon.net wrote:
> Full_Name: Matthew Monaco
> Version: 2.4.11
> OS: GNU/Linux 2.6.27-7 (Ubuntu 8.10 Server JeOS)
> URL:
> Submission from: (NULL) (96.242.209.249)
>
>
> After modifying existing olcAuthzRegexp and/or adding/removing additional
> olcAuthzRegexp from cn=config, I needed to restart slapd for the changes to take
> effect.
>
> I'm not sure if it matters but I was using ldapvi to do the modification.
>
> I can however, confirm that the changes immediately appeared in various other
> ldap browsers (such as Apache Directory Studio).
12 years
(ITS#6036) Crash: UUIDNormalize doesn't clear output on error
by test.007@seznam.cz
Full_Name: Test Seven
Version: 2.4.15
OS: Windows
URL:
Submission from: (NULL) (195.39.55.20)
--- schema_init.orig 2009-01-22 01:01:03.000000000 +0100
+++ schema_init.c 2009-03-26 15:12:15.578125000 +0100
@@ -2814,6 +2814,7 @@ UUIDNormalize(
} else {
slap_sl_free( normalized->bv_val, ctx );
+ BER_BVZERO(normalized);
return LDAP_INVALID_SYNTAX;
}
I encountered a crash in str2entry2() final cleanup. It turned out that it
called ordered_value_normalize(), which called UUIDNormalize(), which left the
value nonzero but already free-d.
12 years
(ITS#6035) slapd requires restart after modifying olcAuthzRegexp
by dgbaley27@verizon.net
Full_Name: Matthew Monaco
Version: 2.4.11
OS: GNU/Linux 2.6.27-7 (Ubuntu 8.10 Server JeOS)
URL:
Submission from: (NULL) (96.242.209.249)
After modifying existing olcAuthzRegexp and/or adding/removing additional
olcAuthzRegexp from cn=config, I needed to restart slapd for the changes to take
effect.
I'm not sure if it matters but I was using ldapvi to do the modification.
I can however, confirm that the changes immediately appeared in various other
ldap browsers (such as Apache Directory Studio).
12 years
Re: (ITS#6034) Assert failure - connection_state_closing / send_ldap_ber / slap_send_search_entry / syncprov_sendresp
by hyc@symas.com
oskar(a)deckle.co.za wrote:
> Full_Name: Oskar Pearson
> Version: 2.4.15
> OS: Ubuntu hardy
> URL: ftp://ftp.openldap.org/incoming/slapd-configs-qualica-1.tar.gz
> Submission from: (NULL) (94.194.140.71)
>
>
> This is the same machine as ITS #6033. Details included here for easy
> reference:
>
> Openldap 2.4.15 (with no patches) was self-compiled with no patches
> (CFLAGS="-ggdb3 -O0" ./configure), linked against standard OS libraries (ubuntu
> hardy) for BDB etc. BDB is 4.6.21-6ubuntu1. Kernel is 2.6.24-19-server, libc is
> libc6-i686/2.7-10ubuntu3.
>
> I do not have a debug log of this crash as it occurred on a live server, which
> is too busy for that level of logging. I also do not have a replaceable
> example.
> I have core dumps and can print out whatever is necessary there - I appreciate
> your time and help.
This bug was fixed in CVS already and the fix will be out in 2.4.16 soon. The
fix is already in RE24...
> gdb --core=../core.29266 --directory=servers/slapd/
> --directory=servers/slapd/overlays servers/slapd/slapd
> (gdb) bt
> #0 0xb7ef8410 in __kernel_vsyscall ()
> #1 0xb7ad5085 in raise () from /lib/tls/i686/cmov/libc.so.6
> #2 0xb7ad6a01 in abort () from /lib/tls/i686/cmov/libc.so.6
> #3 0xb7ace10e in __assert_fail () from /lib/tls/i686/cmov/libc.so.6
> #4 0x0806d6c6 in connection_state_closing (c=0xb79c9644) at connection.c:686
> #5 0x08081bdd in send_ldap_ber (conn=0xb79c9644, ber=0xa143ab8c) at
> result.c:147
> #6 0x08085b20 in slap_send_search_entry (op=0xa143ae38, rs=0xa143acdc) at
> result.c:1246
> #7 0x0815dbcb in syncprov_sendresp (op=0xa143ae38, opc=0xa143adb8,
> so=0x9ab66dc8, e=0xa143ade8, mode=1) at syncprov.c:825
> #8 0x0815df12 in syncprov_qplay (op=0xa143ae38, rtask=0x9b303110) at
> syncprov.c:896
> #9 0x0815e1a7 in syncprov_qtask (ctx=0xa143b1f0, arg=0x9b303110) at
> syncprov.c:959
> #10 0x0817a99b in ldap_int_thread_pool_wrapper (xpool=0x829baf0) at tpool.c:663
> #11 0xb7db14fb in start_thread () from /lib/tls/i686/cmov/libpthread.so.0
> #12 0xb7b80e5e in clone () from /lib/tls/i686/cmov/libc.so.6
--
-- Howard Chu
CTO, Symas Corp. http://www.symas.com
Director, Highland Sun http://highlandsun.com/hyc/
Chief Architect, OpenLDAP http://www.openldap.org/project/
12 years
Re: (ITS#6033) Segmentation fault - somewhere below syncprov_matchops / test_filter
by oskar@deckle.co.za
Hi
Further to this - please note that we know the dbconfig values in the
config files are tiny - we use a DB_CONFIG file to override those,
created before the ldap database is initialised.
On master:
set_cachesize 0 268435456 1
set_lg_regionmax 262144
set_lg_bsize 2097152
set_lk_max_objects 5000
set_lk_max_locks 5000
set_lk_max_lockers 5000
On clients:
set_cachesize 0 16777216 0
set_lk_max_objects 1500
set_lk_max_locks 1500
set_lk_max_lockers 1500
Oskar
12 years
Re: (ITS#6034) Assert failure - connection_state_closing / send_ldap_ber / slap_send_search_entry / syncprov_sendresp
by oskar@deckle.co.za
Hi
Further to this - please note that we know the dbconfig values in the
config files are tiny - we use a DB_CONFIG file to override those,
created before the ldap database is initialised.
On master:
set_cachesize 0 268435456 1
set_lg_regionmax 262144
set_lg_bsize 2097152
set_lk_max_objects 5000
set_lk_max_locks 5000
set_lk_max_lockers 5000
On clients:
set_cachesize 0 16777216 0
set_lk_max_objects 1500
set_lk_max_locks 1500
set_lk_max_lockers 1500
Oskar
12 years