#48898 nunc-stans: ns-slapd killed by SIGABRT
Closed: wontfix Opened by mreynolds.

Ticket was cloned from Red Hat Bugzilla (product Red Hat Enterprise Linux 7): Bug 1272682

Description of problem:
During TET SSL acceptance run with nunc stans enabled a crash was observed.
crashes occurred during the test cleanup/startup phase, when server was restarted.
Version-Release number of selected component (if applicable):
389-ds-base-1.3.4.0-19.el7.x86_64

{{{
Thread 3 (Thread 0x7f8838799880 (LWP 31938)):

0 0x00007f8835ea4ef7 in pthread_join (threadid=140221915866880, thread_return=thread_return@entry=0x7ffc940d0d90)

at pthread_join.c:92

1 0x00007f8836503dc4 in PR_JoinThread (thred=0x7f883adab490) at ../../../nspr/pr/src/pthreads/ptthread.c:597

2 0x00007f883807abe3 in ns_thrpool_destroy (tp=tp@entry=0x7f883ad83b70) at ns_thrpool.c:979

3 0x00007f88388075c0 in slapd_daemon (ports=ports@entry=0x7ffc940d1150) at ldap/servers/slapd/daemon.c:1342

4 0x00007f88387f8103 in main (argc=5, argv=0x7ffc940d1788) at ldap/servers/slapd/main.c:1143

Thread 1 (Thread 0x7f87f57c2700 (LWP 32015)):

0 ns_handle_closure (job=0x7f87c0001260) at ldap/servers/slapd/daemon.c:1782

1 0x00007f88358a2a14 in event_base_loop () from /lib64/libevent-2.0.so.5

2 0x00007f883807b4fe in ns_event_fw_loop (ns_event_fw_ctx=) at ns_event_fw_event.c:311

3 0x00007f883807aa76 in event_loop_thread_func (arg=0x7f883ad83b70) at ns_thrpool.c:352

4 0x00007f883650396b in _pt_root (arg=0x7f883adab490) at ../../../nspr/pr/src/pthreads/ptthread.c:212

5 0x00007f8835ea3dc5 in start_thread (arg=0x7f87f57c2700) at pthread_create.c:308

6 0x00007f8835bd0e2d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:113

}}}

Thread 1 is crashing. The problem is that we freed the connection table in daemon.c before waiting for nunc-stans to clean itself up (ns_thrpool_destroy).

A good catch!!

6e862f3..02d8e0c master -> master
commit 02d8e0c0fc91750d2114b05afebdd457e4a04adf
Author: Mark Reynolds mreynolds@redhat.com
Date: Thu Jun 23 07:22:47 2016 -0400

769b1b2..8133eaf 389-ds-base-1.3.4 -> 389-ds-base-1.3.4
commit 8133eaf26589b0054a0407239bccd6552edd13c4

Metadata Update from @nhosoi:
- Issue assigned to mreynolds
- Issue set to the milestone: 1.3.4.11

389-ds-base is moving from Pagure to Github. This means that new issues and pull requests
will be accepted only in 389-ds-base's github repository.

This issue has been cloned to Github and is available here:
- https://github.com/389ds/389-ds-base/issues/1957

If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.

Thank you for understanding. We apologize for all inconvenience.

Metadata Update from @spichugi:
- Issue close_status updated to: wontfix (was: Fixed)

Metadata