Re: (ITS#7636) slapd crash when multi-master replication (syncrepl) enabled

[hyc@symas.com]

kb9vqf@pearsoncomputing.net wrote:
>> kb9vqf@pearsoncomputing.net wrote:
>>> Full_Name: Timothy Pearson
>>> Version: 2.4.31
>>> OS: Debian Wheezy
>>> URL: ftp://ftp.openldap.org/incoming/
>>> Submission from: (NULL) (131.156.2.26)
>>>
>>>
>>> The setup:
>>> Multi-master syncrepl on two servers
>>> Identical hardware and software between servers
>>> Self-signed TLS using common (private) CA certificate
>>>
>>> The problem:
>>> slapd on one server crashes repeatably within a minute of slapd
> starting on the
>>> other server.  slapd works reliably if and only if the other server is not
>>> running a slapd process.
>>
>> 1) 2.4.31 is ancient. Current is 2.4.35. Please provide a backtrace
> against a
>> current OpenLDAP release.
>>
>> 2) Your backtrace shows a crash in a slapi plugin. If the bug is in your
> plugin there's nothing we can do about it.
>>
>> 3) Don't touch the individual files inside the slapd configuration
> database.
>> Use "slapcat -n0".
>
> Thank you for your prompt response.  In the backtrace I posted, which
> portion suggests that the crash occurred in a plugin?  I would have
> expected to see at least one frame in something other than
> ../../../../servers/slapd.


Program received signal SIGABRT, Aborted.
[Switching to Thread 0x7fffe356c700 (LWP 10433)]
0x00007ffff5a32475 in *__GI_raise (sig=<optimized out>) at
../nptl/sysdeps/unix/sysv/linux/raise.c:64
64      ../nptl/sysdeps/unix/sysv/linux/raise.c: No such file or directory.
(gdb) bt
#0  0x00007ffff5a32475 in *__GI_raise (sig=<optimized out>) at
../nptl/sysdeps/unix/sysv/linux/raise.c:64
#1  0x00007ffff5a356f0 in *__GI_abort () at abort.c:92
#2  0x00007ffff5a6d52b in __libc_message (do_abort=<optimized out>,
fmt=<optimized out>) at ../sysdeps/unix/sysv/linux/libc_fatal.c:189
#3  0x00007ffff5a76d76 in malloc_printerr (action=3, str=0x7ffff5b4f170
"munmap_chunk(): invalid pointer", ptr=<optimized out>) at malloc.c:6283
#4  0x00007ffff63d214a in slapi_op_search_callback (op=0x7fffe3569fd0,
rs=<optimized out>, prc=<optimized out>) at
../../../../../servers/slapd/slapi/slapi_overlay.c:313
#5  slapi_op_search_callback (op=0x7fffe3569fd0, rs=<optimized out>,
prc=<optimized out>) at ../../../../../servers/slapd/slapi/slapi_overlay.c:296
#6  0x00007ffff63d304f in slapi_op_func (rs=0x7fffe3569f60, op=<optimized out>)
at ../../../../../servers/slapd/slapi/slapi_overlay.c:631
#7  slapi_op_func (op=0x7fffe3569fd0, rs=0x7fffe3569f60) at
../../../../../servers/slapd/slapi/slapi_overlay.c:556

The slapi_* functions would not be present in the stack trace unless you had 
configured a slapi plugin on this database.

-- 
   -- Howard Chu
   CTO, Symas Corp.           http://www.symas.com
   Director, Highland Sun     http://highlandsun.com/hyc/
   Chief Architect, OpenLDAP  http://www.openldap.org/project/