Bug 1043257 - No SELinux alerts, but SELinux interrupt starting MariaDB 10.0.6
Summary: No SELinux alerts, but SELinux interrupt starting MariaDB 10.0.6
Keywords:
Status: CLOSED DUPLICATE of bug 1043258
Alias: None
Product: Fedora
Classification: Fedora
Component: selinux-policy
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Miroslav Grepl
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-12-15 13:15 UTC by Mikhail
Modified: 2014-06-09 11:37 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-12-21 07:34:32 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

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 ***


Note You need to log in before you can comment on or make changes to this bug.