Bug 513534

Summary: Crash(?) messages for setroubleshoot
Product: [Fedora] Fedora Reporter: Horst H. von Brand <vonbrand>
Component: serafettin-cartoon-fontsAssignee: Daniel Walsh <dwalsh>
Status: CLOSED CURRENTRELEASE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: low Docs Contact:
Priority: low    
Version: 12CC: dwalsh, fonts-bugs, jdennis, mgrepl, oget.fedora
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: 2010-01-19 20:24:28 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:
Bug Depends On:    
Bug Blocks: 517000    
Attachments:
Description Flags
One (humongous) line out of /var/log/messages
none
Requested setroubleshootd.log
none
Here is the patch none

Description Horst H. von Brand 2009-07-24 02:54:26 UTC
Description of problem:
In /var/log/messages (variations?) of the attachment show up each few seconds.
SELINUX=ENFORCING
SELINUXTYPE=targeted

Version-Release number of selected component (if applicable):
setroubleshoot-2.2.16-1.fc12.x86_64
selinux-policy-3.6.22-2.fc12.noarch
selinux-policy-targeted-3.6.22-2.fc12.noarch
kernel-2.6.31-0.86.rc3.git5.fc12.x86_64

How reproducible:
No idea, just booted after updating (for 20090722 and 20090723).

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


Expected results:


Additional info:

Comment 1 Horst H. von Brand 2009-07-24 02:55:56 UTC
Created attachment 354959 [details]
One (humongous) line out of /var/log/messages

Comment 2 Daniel Walsh 2009-07-27 15:52:45 UTC
John, do you have any idea on this?

Comment 3 John Dennis 2009-07-27 16:24:57 UTC
Sorry, not at the moment, unfortunately looks like the stack trace was truncated in /var/log/messages, but it should be in /var/log/setroubleshoot/setroubleshoot.log

Comment 4 Horst H. von Brand 2009-07-29 14:36:18 UTC
Created attachment 355555 [details]
Requested setroubleshootd.log

As of today (rawhide up to date), setroubleshoot-2.2.16-1.fc12.x86_64

Comment 5 John Dennis 2009-07-29 15:20:22 UTC
Hmm... this looks like the infinite recursion we fixed a while ago in the prune database code where marking an alert caused prune to be called again. Note, that's not the actual error reported, I'm not sure I can explain that error at the moment, but given the depth of the recursion stack I would not be totally surprised if the actual error reported wasn't the consequence of running out of a resource. My suggestion would be to fix the infinite recursion and then see if the other error goes away.

Comment 6 Daniel Walsh 2009-07-30 14:01:09 UTC
John, do you remember how we prevented the recursion.

I am coding prune to set a "prune" flag to true and then having delete_signature, mark_modified, save have a default flag falue true.

Finally save calls

if not prune:
    self.prune()

Comment 7 Daniel Walsh 2009-07-30 14:01:47 UTC
Created attachment 355677 [details]
Here is the patch

Comment 9 Bug Zapper 2009-11-16 11:05:04 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 12 development cycle.
Changing version to '12'.

More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 10 Daniel Walsh 2010-01-19 20:24:28 UTC
Fixed in setroubleshoot-2.2.52-1.fc12