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

RE: (ITS#4562) slapd crash (syncrepl related?)



Howard Chu wrote:
> Looks like your main slapd binary is stripped, which makes this stack
> trace pretty misleading. Try copying in the unstripped binary and see
> if you can duplicate the problem.

Although I wasn't able to reproduce manually the same issue occurred
this morning.  Here is the gdb output...

[505]$ gdb -c core.slapd.15718 /usr/local/libexec/slapd
GNU gdb 6.4
Copyright 2005 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you
are
welcome to change it and/or distribute copies of it under certain
conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for
details.
This GDB was configured as "sparc-sun-solaris2.9"...
Core was generated by `/usr/local/libexec/slapd -u ldap -g ldap -h
ldap:// ldaps
://'.
Program terminated with signal 11, Segmentation fault.
Reading symbols from /usr/local/BerkeleyDB.4.2/lib/libdb-4.2.so...done.
<snip>
#0  0x000cfecc in glue_entry_release_rw (op=0x87f190, e=0x7661c0, rw=0)
    at backglue.c:588
588             int rc = -1;
#0  0x000cfecc in glue_entry_release_rw (op=0x87f190, e=0x7661c0, rw=0)
    at backglue.c:588
#1  0x000cff7c in glue_entry_release_rw (op=0x87f190, e=0x7661c0, rw=0)
    at backglue.c:596
#2  0x000cff7c in glue_entry_release_rw (op=0x87f190, e=0x7661c0, rw=0)
    at backglue.c:596
#3  0x000cff7c in glue_entry_release_rw (op=0x87f190, e=0x7661c0, rw=0)
    at backglue.c:596
#4  0x000cff7c in glue_entry_release_rw (op=0x87f190, e=0x7661c0, rw=0)
    at backglue.c:596
#5  0x000cff7c in glue_entry_release_rw (op=0x87f190, e=0x7661c0, rw=0)
    at backglue.c:596
#6  0x000cff7c in glue_entry_release_rw (op=0x87f190, e=0x7661c0, rw=0)
    at backglue.c:596
#7  0x000cff7c in glue_entry_release_rw (op=0x87f190, e=0x7661c0, rw=0)
    at backglue.c:596
#8  0x000cff7c in glue_entry_release_rw (op=0x87f190, e=0x7661c0, rw=0)
    at backglue.c:596
#9  0x000cff7c in glue_entry_release_rw (op=0x87f190, e=0x7661c0, rw=0)
    at backglue.c:596
#10 0x000cff7c in glue_entry_release_rw (op=0x87f190, e=0x7661c0, rw=0)
    at backglue.c:596

#10908 0x000cff7c in glue_entry_release_rw (op=0x87f190, e=0x7661c0,
rw=0)
    at backglue.c:596
#10909 0x000cff7c in glue_entry_release_rw (op=0x87f190, e=0x7661c0,
rw=0)
    at backglue.c:596
#10910 0x00057f8c in be_entry_release_rw (op=0x87f190, e=0x7661c0, rw=0)
    at backend.c:739
<snip>
#10911 0xfece4e84 in syncprov_matchops (op=0x87f190, opc=0x43df04,
saveit=0)
    at syncprov.c:1075
#10912 0xfece69dc in syncprov_op_response (op=0x87f190, rs=0xf8bffd30)
    at syncprov.c:1521
#10913 0x0005b7bc in send_ldap_response (op=0x87f190, rs=0xf8bffd30)
    at result.c:303
#10914 0x0005cabc in slap_send_ldap_result (op=0x87f190, rs=0xf8bffd30)
    at result.c:574

#10915 0x000dffa8 in bdb_modify (op=0x87f190, rs=0xf8bffd30) at
modify.c:591
#10916 0x000cec24 in glue_op_func (op=0x87f190, rs=0xf8bffd30)
    at backglue.c:200
#10917 0x000d1bd4 in overlay_op_walk (op=0x87f190, rs=0xf8bffd30,
    which=op_modify, oi=0x29fab8, on=0x29fbb0) at backover.c:491
#10918 0x000d1e98 in over_op_func (op=0x87f190, rs=0xf8bffd30,
which=op_modify)
    at backover.c:551
#10919 0x000d1fa8 in over_op_modify (op=0x87f190, rs=0xf8bffd30)
    at backover.c:585

#10920 0x00068a98 in fe_op_modify (op=0x87f190, rs=0xf8bffd30) at
modify.c:395
#10921 0x00067960 in do_modify (op=0x87f190, rs=0xf8bffd30) at
modify.c:200
#10922 0x000440ec in connection_operation (ctx=0xf8bffe08,
arg_v=0x87f190)
    at connection.c:1307
#10923 0x00164524 in ldap_int_thread_pool_wrapper (xpool=0x24fed8)
    at tpool.c:478
#10924 0xfed957bc in _lwp_start () from /usr/lib/libthread.so.1
#10925 0xfed957bc in _lwp_start () from /usr/lib/libthread.so.1
Previous frame identical to this frame (corrupt stack?)

=================================================================

_________________________________________________________________
This message (and any attachment) is intended only for the 
recipient and may contain confidential and/or privileged 
material.  If you have received this in error, please contact the 
sender and delete this message immediately.  Disclosure, copying 
or other action taken in respect of this email or in 
reliance on it is prohibited.  BMRB Limited accepts no liability 
in relation to any personal emails, or content of any email which 
does not directly relate to our business.
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++