[Date Prev][Date Next] [Chronological] [Thread] [Top]

Re: (ITS#5836) hung writers



Hi,

On Tue, Jul 7, 2009 at 6:40 PM, Quanah Gibson-Mount<quanah@zimbra.com> wrote:
>
> Hi Jorge,
>
> We're going to need more information from you than you are providing. Please
> make sure you:
>
> (a) build openldap without optimization (-O0)
> (b) are gdbing the process, not a core file
> (c) Send a full backtrace of everything: thr apply all bt full
>
> Also, please confirm what BDB version you are using, including if it has all
> patches applied and compile options for BDB, and which backend you are
> using.

The last testing was wrong due to an old slapd.conf without
writetimeout keyword, my apologies. We have been testing for 2 days to
reproduce this problem and we have not seen the problem again, even
though with debug symbols the assert ""assert( SLAP_SOCK_IS_ACTIVE( s
))"" still fails.

Reading symbols from /usr/lib64/sasl2/libanonymous.so...done.
Loaded symbols for /usr/lib64/sasl2/libanonymous.so
Core was generated by `/local/slapd_L5B8_17-7 -f
/home/cudb/dataAccess/ldapAccess/ldapFe/config/slapd.'.
Program terminated with signal 6, Aborted.
#0 0x00002b18e9dd5d45 in raise () from /lib64/libc.so.6
(gdb) bt
#0 0x00002b18e9dd5d45 in raise () from /lib64/libc.so.6
#1 0x00002b18e9dd7140 in abort () from /lib64/libc.so.6
#2 0x00002b18e9dcf286 in __assert_fail () from /lib64/libc.so.6
#3 0x00000000004641b0 in slapd_clr_write (s=410, wake=0) at daemon.c:939
#4 0x000000000046db7d in connection_write (s=410) at connection.c:1855
#5 0x00000000004688e0 in slapd_daemon_task (ptr=0x0) at daemon.c:2567
#6 0x00002b18e9264143 in start_thread () from /lib64/libpthread.so.0
#7 0x00002b18e9e66b8d in clone () from /lib64/libc.so.6
#8 0x0000000000000000 in ?? ()

Best regards.