Bug 477235

Summary: setroubleshoot-server doesn't start
Product: [Fedora] Fedora Reporter: Horst H. von Brand <vonbrand>
Component: setroubleshootAssignee: Daniel Walsh <dwalsh>
Status: CLOSED RAWHIDE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: rawhideCC: dwalsh, jdennis, mgrepl
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: 2009-03-30 22:01:15 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:

Description Horst H. von Brand 2008-12-19 19:17:28 UTC 
Description of problem:
I just got:

  # service setroubleshoot start
  Starting setroubleshootd:                                  [  OK  ]
  # Exception RuntimeError: 'maximum recursion depth exceeded while calling a Python object' in <type 'exceptions.AttributeError'> ignored
  # service setroubleshoot status
  setroubleshootd dead but pid file exists

Version-Release number of selected component (if applicable):
setroubleshoot-server-2.0.12-2.fc11.noarch
python-2.6-2.fc11.x86_64

How reproducible:
Each time

Steps to Reproduce:
1. See above
2.
3.
  
Actual results:


Expected results:


Additional info:
I had seen the 'Exception RuntimeError' a few times on shutdown before, couldn't make sense where it came from.
Comment 1 Daniel Walsh 2009-02-11 14:46:35 UTC 
setroubelshoot has been updated several times since december are you still seeing this problem?