Bug 140635
| Summary: | SELinux Targeted prevents Syslog from starting properly | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Ed Holden <ed> | ||||
| Component: | selinux-policy-targeted | Assignee: | Daniel Walsh <dwalsh> | ||||
| Status: | CLOSED RAWHIDE | QA Contact: | |||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | medium | ||||||
| Version: | 3 | CC: | djuran | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | i386 | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2004-11-29 14:10:44 UTC | Type: | --- | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
Could you attach the dmesg output when syslog fails? Dan Created attachment 107391 [details]
dmesg output when SELinux is enabled with a targeted policy
Here it is: I re-enabled SELinux, which is set to use the targeted poliy, in
/etc/selinux/config. This is the resulting dmesh file.
touch /.autorelabel and then a reboot solved things for me. Is this really a duplicate of bug 140100? Both are labeling problems. |
From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5) Gecko/20041111 Firefox/1.0 Description of problem: When the SELinux targeted policy is enabled, the syslog daemon does not properly start. I noticed this because log messages that should have appeared in /var/log/messages or /var/log/secure were appearing on the console, though syslog was not configured to send them there. I tried reinstalling the sysklogd RPM with no joy. In the end, disabling SELinux fixed the problem. Whether this is an issue with syslogd accessing the log files or simply starting is unclear. Version-Release number of selected component (if applicable): selinux-policy-targeted-1.17.30-2.19 How reproducible: Always Steps to Reproduce: 1. Enable Targeted policy in SELinux. 2. Reboot. Actual Results: syslogd does not start, and the init script hangs Expected Results: syslogd should start and log events with clear enthusiasm. Additional info: