Hide Forgot
Description of problem: customer is having repeatedly this crash after update to release 28. "connection_table_move_connection_out_of_active_list" "ns_handle_closure_nomutex" "ns_handle_pr_read_ready" "work_job_execute" "event_cb" "event_base_loop" "ns_event_fw_loop" "event_loop_thread_func" "start_thread" "__clone" it was happening from time to time. Today the server is crashing non-stop showing this messages: Apr 12 11:35:25 <xxxx> systemd: Started 389 Directory Server xx.. Apr 12 11:36:06 <xxxx> ns-slapd: *** stack smashing detected ***: /usr/sbin/ns-slapd terminated Apr 12 11:36:06 <xxxx> kernel: traps: ns-slapd[5646] general protection ip:7f348ea15118 sp:7f343b6fcef0 error:0 in libgcc_s-4.8.5-20150702.so.1[7f348ea06000+15000] Apr 12 11:36:06 <xxxx> systemd: dirsrv@bv.service: main process exited, code=killed, status=11/SEGV Version-Release number of selected component (if applicable): 389-ds-base-1.3.6.1-28 I was told it's duplicated of 1517383 ns-slapd segfaults with ERR - connection_release_nolock_ext - conn=0 fd=0 Attempt to release connection that is not acquired but I prefer to report a new bug with high priority. I will add more information about the crashes of today.
Build tested: 389-ds-base-1.3.8.4-12.el7.x86_64 I haven't encountered crash in connection_table_move_connection_out_of_active_list with NS enabled (it's disabled by default) in our acceptance testing, hence marking as VERIFIED, SanityOnly.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2018:3127