Bug 740486

Summary:	setroubleshootd (setroubleshoot-server) segfault
Product:	Red Hat Enterprise Linux 5	Reporter:	Yoshifumi Kinoshita <ykinoshi>
Component:	setroubleshoot	Assignee:	Daniel Walsh <dwalsh>
Status:	CLOSED NOTABUG	QA Contact:	BaseOS QE Security Team <qe-baseos-security>
Severity:	low	Docs Contact:
Priority:	low
Version:	5.8	CC:	jamesodhunt, jdennis, mmalik, wburrows
Target Milestone:	rc
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:	456332	Environment:
Last Closed:	2011-10-24 15:34:16 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Bug Depends On:	456332
Bug Blocks:

Comment 1 Daniel Walsh 2011-09-22 12:59:38 UTC

Well this looks like a python issue, but I would have your customer clear out his setroubleshoot database in /var/lib/setroubleshoot/audit*.xml

Either remove the files or cat /dev/null into them and see if this fixes the problem.  One problem with RHEL5 setroubleshoot could be its handling of international lanquages.  Something in the XML database might be causing the python to crash.

Comment 2 RHEL Program Management 2011-09-23 00:34:12 UTC

This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated in the
current release, Red Hat is unfortunately unable to address this
request at this time. 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.