Bug 1043257

Summary: No SELinux alerts, but SELinux interrupt starting MariaDB 10.0.6
Product: [Fedora] Fedora Reporter: Mikhail <mikhail.v.gavrilov>
Component: selinux-policyAssignee: Miroslav Grepl <mgrepl>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: dominick.grift, dwalsh, i, lvrabec, mgrepl, mikhail.v.gavrilov
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-12-21 07:34:32 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Mikhail 2013-12-15 13:15:57 UTC 
Description of problem:
[root@Z87M-D3H yum.repos.d]# service mysql start
Starting MySQL.The server quit without updating PID file (/[FAILED]mysql/Z87M-D3H.pid).
[root@Z87M-D3H yum.repos.d]# setenforce 0
[root@Z87M-D3H yum.repos.d]# service mysql start
Starting MySQL.                                            [  OK  ]
[root@Z87M-D3H yum.repos.d]# service mysql restart
Shutting down MySQL..                                      [  OK  ]
Starting MySQL.                                            [  OK  ]
[root@Z87M-D3H yum.repos.d]# setenforce 1
[root@Z87M-D3H yum.repos.d]# service mysql restart
Shutting down MySQL..                                      [  OK  ]
Starting MySQL.The server quit without updating PID file (/[FAILED]mysql/Z87M-D3H.pid).
[root@Z87M-D3H yum.repos.d]# ausearch -m avc -ts recent
<no matches>
[root@Z87M-D3H yum.repos.d]# service mysql restart
MySQL server PID file could not be found!                  [FAILED]
Starting MySQL.The server quit without updating PID file (/[FAILED]mysql/Z87M-D3H.pid).
[root@Z87M-D3H yum.repos.d]# ausearch -m avc -ts recent
<no matches>
[root@Z87M-D3H yum.repos.d]# 

Expected result:
I want to see SELinux alerts for my situation.
Comment 1 Miroslav Grepl 2013-12-16 09:50:17 UTC 
Is auditd running? Maybe you will need to run

# semodule -DB

to see dontaudit rules.
Comment 2 Christopher Meng 2013-12-21 07:34:32 UTC 

*** This bug has been marked as a duplicate of bug 1043258 ***