Bug 746253

Summary:	/usr/sbin/slapd segfault is not caught by abrt
Product:	Red Hat Enterprise Linux 6	Reporter:	Yogesh <ychavan>
Component:	abrt	Assignee:	Jiri Moskovcak <jmoskovc>
Status:	CLOSED NOTABUG	QA Contact:	qe-baseos-tools-bugs
Severity:	medium	Docs Contact:
Priority:	medium
Version:	6.1	CC:	dfediuck, kklic, mnowak, nc, nobody+abrt-devel-list, vgaikwad
Target Milestone:	rc
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2011-10-25 12:19:26 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Yogesh 2011-10-14 14:39:59 UTC

Description of problem:
If I run slapd as daemon and send sig 11 or sig 6 to slapd process, it is not caught by abrt.

Version-Release number of selected component (if applicable):
openldap-servers-2.4.23-15.el6_1.3.x86_64

How reproducible:
always

Steps to Reproduce:
1. service slapd stop ; service slapd stop ; ps aux | grep slapd
2.  kill -11 <pid of slapd>
  
Actual results:
abrt daemon does not detect this

Expected results:
abrt should detect this and this crash should be listed in abrt-cli -l

Comment 6 Karel Klíč 2011-10-20 12:43:04 UTC

When /usr/sbin/slapd is run via init scripts, it is run with argument -u user. This causes slapd to call setgid, setegid, setuid, and seteuid functions to change the daemon user.

Manual page core(5) says, that coredump is not produced if "The process is executing a set-user-ID (set-group-ID) program that is owned by a user (group) other than the real user (group) ID of the process."

This seems to be the issue in this case. A solution might be to change the user in the init script, before running the daemon.

Comment 7 RHEL Program Management 2011-10-25 05:47:32 UTC

Since RHEL 6.2 External Beta has begun, and this bug remains
unresolved, it has been rejected as it is not proposed as
exception or blocker.

Red Hat invites you to ask your support representative to
propose this request, if appropriate and relevant, in the
next release of Red Hat Enterprise Linux.