Bug 1224507
| Summary: | radvd cannot be started by systemd due to selinux errors | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Marek Greško <marek.gresko> |
| Component: | radvd | Assignee: | Pavel Šimerda (pavlix) <psimerda> |
| Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 22 | CC: | jpopelka, psimerda |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2015-06-05 10:02:05 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: | |
| Embargoed: | |||
I found out the bug caused by incorrect ownership of /var/run/radvd. When I change owner of the directory to root, the pid file is created successfully and radvd is running when started by systemctl. Otherwise the startup is blocked by selinux, because it block root to write to directory owned by radvd. *** This bug has been marked as a duplicate of bug 1224403 *** |
Description of problem: radvd cannot be started by systemd due to selinux errors. Version-Release number of selected component (if applicable): radvd-2.8-1.fc22.x86_64 How reproducible: start radvd using systemd Steps to Reproduce: 1. systemct start radvd (or restart) Actual results: radvd fails to start. Yielding: avc: denied { dac_override } for pid=16534 comm="radvd" capability=1 scontext=system_u:system_r:radvd_t:s0 tcontext=system_u:system_r:radvd_t:s0 tclass=capability permissive=0....... Expected results: radvd is run. Additional info: