Bug 770497

Summary: setroubleshootd is using +/-60% of processor; SELinux shows an invalid AVC message
Product: [Fedora] Fedora Reporter: Doug Hutcheson <owlbrudder>
Component: setroubleshootAssignee: Daniel Walsh <dwalsh>
Status: CLOSED NOTABUG QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 15CC: dwalsh, 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: 2011-12-27 06:27:37 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
'top' output
none
System Monitor screenshot with system idle
none
SELinux invalid AVC Denial report screen shot none

Description Doug Hutcheson 2011-12-27 05:35:42 UTC
Created attachment 549646 [details]
'top' output

Description of problem:
I have a dual-core Intel x86_64 processor (Lenovo T61 laptop). It has been responding slowly to user input since a recent software update. 'top' shows setroubleshootd is using between 55% and 70% in the '%CPU' column and 'System Monitor' is showing both cores being used 80% to 95% when the machine is supposedly standing idle.

In addition, 'SELinux Alert Browser' is popping up an alert which makes no sense: it has the following information:
The source process: label
Attempted this access: label
On this file: label
None of the buttons in the applet has any effect: I cannot delete, ignore, troubleshoot, notify admin or see details.  The applet shows zero alerts. 'List All Alerts' opens a window, but this has no content other than the headings. 

I am assuming the setroubleshootd CPU usage problem and the SELinux AVC report problem have the same cause, which is why I have made a single report.


Version-Release number of selected component (if applicable):
setroubleshoot-3.0.38-1.fc15.x86_64


How reproducible:
Normal use of system. I have tried killing the setroubleshoot process and rebooting, but the problems persist.


Steps to Reproduce:
1. Boot system
2.
3.
  
Actual results:
Heavy use of processor cores; invalid AVC denial report.


Expected results:
Cores should be showing low use at idle, AVC reports should be valid and reportable.


Additional info:
The problem started with a recent software update.

Comment 1 Doug Hutcheson 2011-12-27 05:37:12 UTC
Created attachment 549647 [details]
System Monitor screenshot with system idle

Comment 2 Doug Hutcheson 2011-12-27 05:40:39 UTC
Created attachment 549648 [details]
SELinux invalid AVC Denial report screen shot

Comment 3 Doug Hutcheson 2011-12-27 06:27:37 UTC
A subsequent reboot brought the SELinux AVC app back to life and it showed an ever-increasing list of 'search' access errors by boinc.Rather than deal with them at this time, I have killed boinc_client and deleted the seapplet reports. This has removed setroubleshootd from the 'top' list and has restored processor use to sensible levels.

Summary: It seems to be a boinc problem and I know there are issues with boinc, so I have shut it down for now.