Bug 229284 – setroubleshoot crashes when syslog is unavailable

Bug 229284 - setroubleshoot crashes when syslog is unavailable

Summary:	setroubleshoot crashes when syslog is unavailable

Status:	CLOSED RAWHIDE

Aliases:	None

Product:	Fedora
Classification:	Fedora
Component:	setroubleshoot (Show other bugs)
Sub Component:
Version:	6
Hardware:	x86_64 Linux

Priority	medium Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	John Dennis
QA Contact:	Ben Levenson
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2007-02-19 17:35 EST by Davide Bolcioni
Modified:	2007-11-30 17:11 EST (History)
CC List:	0 users

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2007-09-27 17:26:11 EDT
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Python traceback (1.48 KB, text/plain) 2007-02-19 17:35 EST, Davide Bolcioni	no flags	Details
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Davide Bolcioni 2007-02-19 17:35:53 EST

Description of problem: Under the circumstances described in bug #229283, 
setroubleshoot fails to start on boot and displays a traceback on the console.


Version-Release number of selected component (if applicable):
setroubleshoot-1.7.1-1.fc6

How reproducible:
always


Steps to Reproduce:
1. chcon -t rpm_script_tmp_t /etc/services
2. service syslog restart
3. setroubleshootd
  
Actual results:


Expected results:


Additional info:

Comment 1 Davide Bolcioni 2007-02-19 17:35:53 EST

Created attachment 148374 [details]
Python traceback

Comment 2 John Dennis 2007-09-27 17:26:11 EDT

cleaning out old bugs. This was fixed a while ago, not sure about the FC-6
version, but in current versions all that happens is this is written to stderr:

exception when creating syslog handler: (2, 'No such file or directory')

and then everything continues normally.

So I'm going to close this out, I'd close it as CURRENT RELEASE except it was
fixed so long ago I don't know the version number so I'm just closing it RAWHIDE.

Note You need to log in before you can comment on or make changes to this bug.