Contents
When do you need to troubleshoot SELinux denials?
If you plan to enable SELinux on systems where it has been previously disabled or if you run a service in a non-standard configuration, you might need to troubleshoot situations potentially blocked by SELinux. Note that in most cases, SELinux denials are signs of misconfiguration. 5.1. Identifying SELinux denials
What to do when your scenario is blocked by SELinux?
When your scenario is blocked by SELinux, the /var/log/audit/audit.log file is the first place to check for more information about a denial. To query Audit logs, use the ausearch tool.
How to check if SELinux audit daemon is running?
If there are no matches, check if the Audit daemon is running. If it does not, repeat the denied scenario after you start auditd and check the Audit log again. In case auditd is running, but there are no matches in the output of ausearch, check messages provided by the systemd Journal:
What happens when nexus.service is shut down?
The service using nexus.service definition from that page starts up but the eventually reaches a timeout and is shutdown. The service type of forking Forking type waits some time for the parent process to exit but it this event apparently does not happen.
Which is the targeted policy in SELinux 4?
SELinux Contexts for Users 4. Targeted Policy 4.1. Confined Processes 4.2. Unconfined Processes 4.3. Confined and Unconfined Users 5. Working with SELinux 5.1. SELinux Packages 5.2. Which Log File is Used 5.3. Main Configuration File 5.4.
Which is the default context for SELinux 5.9?
Checking the Default SELinux Context 5.9.4. Archiving Files with tar 5.9.5. Archiving Files with star 5.10. Information Gathering Tools 5.11. Multi-Level Security (MLS) 5.11.1. MLS and System Privileges 5.11.2. Enabling MLS in SELinux 5.11.3. Creating a User With a Specific MLS Range 5.11.4.