Bug 703163

Summary: SELINUX_ERR message not captured when readahead-collector is running instead of auditd
Product: Red Hat Enterprise Linux 6 Reporter: Jan Hutař <jhutar>
Component: readaheadAssignee: Harald Hoyer <harald>
Status: CLOSED CANTFIX QA Contact: qe-baseos-daemons
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.1CC: mitr
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-07-04 12:20:23 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On:    
Bug Blocks: 545868    

Description Jan Hutař 2011-05-09 14:09:55 UTC
Description of problem:
I'm running script which causes SELINUX_ERR failure, but it is not reported in ~50% of cases.

After some debugging, when I have added `sleep 3m` to the beginning of the script, I have found out, that when the script is started, there is:

 * running "readahead-collector"
 * not running "auditd"

and 3 minutes later:

 * not running "readahead-collector"
 * running "auditd"

When script is started after these 3 minutes, SELINUX_ERR nicely appears in /var/log/audit/audit.log.

I have discussed it with Miroslav Trmac, and he said, that in the boot-time, readahead-collector replaces auditd and that readahead-collector might just drop messages he is not interested in.

If this is exact, should readahead-collector be fixed, or should I keep mentioned workaround in my script (as I want that SELINUX_ERR to be reported)?

Comment 2 RHEL Program Management 2011-05-09 14:28:15 UTC
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unfortunately unable to
address this request at this time. Red Hat invites you to
ask your support representative to propose this request, if
appropriate and relevant, in the next release of Red Hat
Enterprise Linux. If you would like it considered as an
exception in the current release, please ask your support
representative.

Comment 3 Harald Hoyer 2012-07-04 12:20:23 UTC
(In reply to comment #0)
> Description of problem:
> I'm running script which causes SELINUX_ERR failure, but it is not reported
> in ~50% of cases.
> 
> After some debugging, when I have added `sleep 3m` to the beginning of the
> script, I have found out, that when the script is started, there is:
> 
>  * running "readahead-collector"
>  * not running "auditd"
> 
> and 3 minutes later:
> 
>  * not running "readahead-collector"
>  * running "auditd"
> 
> When script is started after these 3 minutes, SELINUX_ERR nicely appears in
> /var/log/audit/audit.log.
> 
> I have discussed it with Miroslav Trmac, and he said, that in the boot-time,
> readahead-collector replaces auditd and that readahead-collector might just
> drop messages he is not interested in.
> 
> If this is exact, should readahead-collector be fixed, or should I keep
> mentioned workaround in my script (as I want that SELINUX_ERR to be
> reported)?

You should just deinstall readahead.