Bug 1224507 - radvd cannot be started by systemd due to selinux errors
Summary: radvd cannot be started by systemd due to selinux errors
Keywords:
Status: CLOSED DUPLICATE of bug 1224403
Alias: None
Product: Fedora
Classification: Fedora
Component: radvd
Version: 22
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Pavel Šimerda (pavlix)
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-05-23 20:20 UTC by Marek Greško
Modified: 2015-06-05 10:02 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-06-05 10:02:05 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Marek Greško 2015-05-23 20:20:44 UTC
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:

Comment 1 Marek Greško 2015-05-26 20:18:45 UTC
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.

Comment 2 Pavel Šimerda (pavlix) 2015-06-05 10:02:05 UTC

*** This bug has been marked as a duplicate of bug 1224403 ***


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