Bug 229284

Summary: setroubleshoot crashes when syslog is unavailable
Product: [Fedora] Fedora Reporter: Davide Bolcioni <davide_bolcioni>
Component: setroubleshootAssignee: John Dennis <jdennis>
Status: CLOSED RAWHIDE QA Contact: Ben Levenson <benl>
Severity: medium Docs Contact:
Priority: medium    
Version: 6   
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2007-09-27 21:26:11 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Python traceback none

Description Davide Bolcioni 2007-02-19 22:35:53 UTC 
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 22:35:53 UTC 
Created attachment 148374 [details]
Python traceback
Comment 2 John Dennis 2007-09-27 21:26:11 UTC 
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.