Selinux: Difference between revisions
Jump to navigation
Jump to search
| Line 29: | Line 29: | ||
=Troubleshooting= | =Troubleshooting= | ||
== | ==Diagnosing and Fixing SELinux Problems== | ||
If you have a suspicion that SELinux may be at the root of your problems, run: | If you have a suspicion that SELinux may be at the root of your problems, run: | ||
Revision as of 22:20, 8 January 2016
Internal
Overview
How to Find Out Whether SELinux is Enabled
getenforce
If SELinux is enabled, the command will return "Enforcing".
Configuration
Install Management and Troubleshooting Tools
yum provides /usr/sbin/semanage yum provides sealert
yum -y install policycoreutils-python yum -y install setroubleshoot-server
Troubleshooting
Diagnosing and Fixing SELinux Problems
If you have a suspicion that SELinux may be at the root of your problems, run:
sealert -a /var/log/audit/audit.log
You may get an output similar to the following one, which helps diagnose the problem:
[...] SELinux is preventing /usr/sbin/httpd from write access on the file manager.node.nodes.lock. [...]
The tools also suggest what to do to fix it.
Permission Denied when Trying to Write in a Directory
TODO, rationalize the following content: Media_Wiki_Installation#Fails_to_upload_images_with_.27Fatal_exception_of_type_.22MWException.22.27.