Simo Sorce wrote:

now I am not sure if abtrd would work better in a properly labeled
system, it is possible the labeling issue prevented proper abrtd
functionality, so close it, and if I notice another segfault and abrtd
again not being able to catch the segfault I will open a better ticket ?

Simo.

https://access.redhat.com/site/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Deployment_Guide/ch-abrt.html

abrtd does capture a ns-slapd crash, and the backtrace, etc is correctly gathered.

abrt-2.2.1-2.fc20.x86_64

{{{

abrt-cli list

id 41ba1d0c6da30bd89f0997d8cdf441f38273aabb
Directory: /var/tmp/abrt/ccpp-2014-05-23-11:50:05-19711
count: 1
executable: /usr/sbin/ns-slapd
package: 389-ds-base-1.3.2.16-1.fc20
time: Fri 23 May 2014 11:50:05 AM EDT
uid: 0

ls /var/tmp/abrt/ccpp-2014-05-23-11:50:05-19711

abrt_version count limits pkg_epoch time
analyzer dso_list maps pkg_name type
architecture environ open_fds pkg_release uid
cgroup executable os_info pkg_version username
cmdline exploitable os_release proc_pid_status uuid
component hostname package pwd var_log_messages
core_backtrace kernel pid reason
coredump last_occurrence pkg_arch runlevel
}}}

Closing ticket.

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/1108

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.