Control: tag -1 moreinfo Hi,
On Sat, Apr 22, 2017 at 12:47:19PM +0200, GALAMBOS Daniel wrote:
I created a core file from the stuck process. GDB backtrace attached as separate files.
Thanks for including the backtrace, that makes our job a lot easier. :)
Thread 2 (Thread 0x7f312f7fe700 (LWP 18913)): #0 0x00007f3271b28e46 in ?? () from /usr/lib/x86_64-linux-gnu/libsasl2.so.2 #1 0x00007f3271b29006 in sasl_client_add_plugin () from /usr/lib/x86_64-linux-gnu/libsasl2.so.2 #2 0x00007f3271b34e00 in ?? () from /usr/lib/x86_64-linux-gnu/libsasl2.so.2 #3 0x00007f3271b297b1 in sasl_client_init () from /usr/lib/x86_64-linux-gnu/libsasl2.so.2 #4 0x00007f327279fb3c in ldap_int_sasl_init () from /usr/lib/x86_64-linux-gnu/libldap_r-2.4.so.2 #5 0x00007f327279fbfc in ldap_int_sasl_open () from /usr/lib/x86_64-linux-gnu/libldap_r-2.4.so.2 #6 0x00007f32727a0384 in ldap_int_sasl_bind () from /usr/lib/x86_64-linux-gnu/libldap_r-2.4.so.2 #7 0x00007f32727a37f6 in ldap_sasl_interactive_bind () from /usr/lib/x86_64-linux-gnu/libldap_r-2.4.so.2 #8 0x00007f32727a39fd in ldap_sasl_interactive_bind_s () from /usr/lib/x86_64-linux-gnu/libldap_r-2.4.so.2 #9 0x00007f3272c2ec64 in slap_client_connect (ldp=0x7f32740b03f8, sb=0x7f32740b01d0) at ../../../../servers/slapd/config.c:2064 #10 0x00007f3272c9f5ec in do_syncrep1 (si=0x7f32740b01a0, op=0x7f312f7fd7f0) at ../../../../servers/slapd/syncrepl.c:613 #11 do_syncrepl (ctx=<optimized out>, arg=0x7f32740b0810) at ../../../../servers/slapd/syncrepl.c:1527 #12 0x00007f3272798c62 in ?? () from /usr/lib/x86_64-linux-gnu/libldap_r-2.4.so.2 #13 0x00007f3270b6b064 in start_thread (arg=0x7f312f7fe700) at pthread_create.c:309 #14 0x00007f32708a062d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111
This is a syncrepl client. I guess it's trying to connect to the other master. Any idea why it would be hanging?
If you install libldap-2.4-2-dbg and cyrus-sasl2-dbg, we should be able to get a better idea of what operation is stuck there.
