Description of problem: I noticed that slapd dumps core during mmrepl accept ( acceptance test ) cleanup phase. I tried atleast on rhel5 32bit and gathered this stack trace. Core was generated by `./ns-slapd -D /export/svrbld/DS8.1-18521/server/slapd-s2 -i /export/svrbld/DS8.'. Program terminated with signal 11, Segmentation fault. #0 0xb7e18fd8 in SVRCORE_StdPinGetPin () from /usr/lib/libsvrcore.so.0 (gdb) where #0 0xb7e18fd8 in SVRCORE_StdPinGetPin () from /usr/lib/libsvrcore.so.0 #1 0xb7ef573b in slapd_SSL_client_auth (ld=0x87dfe20) at ldap/servers/slapd/ssl.c:1173 #2 0xb7f00035 in slapi_ldap_bind (ld=0x87dfe20, bindid=0x87d7ca8 "cn=replication manager,o=fr", creds=0x87d6bf0 "", mech=<value optimized out>, serverctrls=0x0, returnedctrls=0xae3e11b0, timeout=0x0, msgidp=0x0) at ldap/servers/slapd/util.c:1150 #3 0xb6e99139 in conn_connect (conn=0x87ce8e8) at ldap/servers/plugins/replication/repl5_connection.c:1564 #4 0xb6ea28e6 in acquire_replica (prp=0x87ce9f8, prot_oid=0xb6ecb692 "2.16.840.1.113730.3.6.1", ruv=0xae3e134c) at ldap/servers/plugins/replication/repl5_protocol_util.c:168 #5 0xb6e9c3ba in repl5_inc_run (prp=0x87ce9f8) at ldap/servers/plugins/replication/repl5_inc_protocol.c:800 #6 0xb6ea1ec8 in prot_thread_main (arg=0x87d37f8) at ldap/servers/plugins/replication/repl5_protocol.c:313 #7 0x002766ed in PR_JoinThread () from /usr/lib/libnspr4.so #8 0x0088145b in start_thread () from /lib/libpthread.so.0 #9 0x007d8c4e in clone () from /lib/libc.so.6 (gdb)
Created attachment 328902 [details] diffs
Created attachment 328906 [details] cvs commit log Reviewed by: nkinder (Thanks!) Fix Description: Have to call ldapssl_set_option(ld, SSL_NO_CACHE, PR_TRUE) after setting up the connection for client auth Platforms tested: RHEL5 Flag Day: no Doc impact: no
fix verfied - as of January 29th - mmrepl acceptance tests are passing and no more core dumps.
An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on therefore solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHEA-2009-0455.html