Bug 1366812 - SELinux is preventing systemd from 'read' accesses on the file armat1.home:1.pid.
Summary: SELinux is preventing systemd from 'read' accesses on the file armat1.home:1....
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: selinux-policy
Version: 24
Hardware: x86_64
OS: Unspecified
low
low
Target Milestone: ---
Assignee: Lukas Vrabec
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:1b0faaf9c45db33fbdb2ab4d803...
: 1366814 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-08-13 00:49 UTC by NM
Modified: 2016-09-25 14:43 UTC (History)
7 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2016-08-23 11:35:50 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)

Description NM 2016-08-13 00:49:57 UTC 
Description of problem:
Attempted to start TigerVNC server
systemctl start vncserver@:1
SELinux is preventing systemd from 'read' accesses on the file armat1.home:1.pid.

*****  Plugin catchall (100. confidence) suggests   **************************

If you believe that systemd should be allowed read access on the armat1.home:1.pid file by default.
Then you should report this as a bug.
You can generate a local policy module to allow this access.
Do
allow this access for now by executing:
# ausearch -c 'systemd' --raw | audit2allow -M my-systemd
# semodule -X 300 -i my-systemd.pp

Additional Information:
Source Context                system_u:system_r:init_t:s0
Target Context                system_u:object_r:user_home_t:s0
Target Objects                armat1.home:1.pid [ file ]
Source                        systemd
Source Path                   systemd
Port                          <Unknown>
Host                          (removed)
Source RPM Packages           
Target RPM Packages           
Policy RPM                    selinux-policy-3.13.1-191.8.fc24.noarch
Selinux Enabled               True
Policy Type                   targeted
Enforcing Mode                Enforcing
Host Name                     (removed)
Platform                      Linux (removed) 4.6.5-300.fc24.x86_64 #1 SMP Thu
                              Jul 28 01:10:12 UTC 2016 x86_64 x86_64
Alert Count                   3
First Seen                    2016-08-12 20:48:19 EDT
Last Seen                     2016-08-12 20:48:19 EDT
Local ID                      4cb8474c-779b-4f75-8cb3-33589f4082a8

Raw Audit Messages
type=AVC msg=audit(1471049299.148:819): avc:  denied  { read } for  pid=1 comm="systemd" name="armat1.home:1.pid" dev="dm-4" ino=28573909 scontext=system_u:system_r:init_t:s0 tcontext=system_u:object_r:user_home_t:s0 tclass=file permissive=0


Hash: systemd,init_t,user_home_t,file,read

Version-Release number of selected component:
selinux-policy-3.13.1-191.8.fc24.noarch

Additional info:
reporter:       libreport-2.7.2
hashmarkername: setroubleshoot
kernel:         4.6.5-300.fc24.x86_64
type:           libreport
Comment 1 Lukas Vrabec 2016-08-16 16:30:19 UTC 
NM, 

What is armat1.home:1.pid file?
Comment 2 Lukas Vrabec 2016-08-16 16:30:39 UTC 
*** Bug 1366814 has been marked as a duplicate of this bug. ***
Comment 3 NM 2016-08-23 02:38:26 UTC 
armat1.home:1.pid is the hostname:1.vnc_process_id_file 
After allowing access it works.
Thanks
Comment 4 Eric COUTURIER-GUILLAUME 2016-09-25 14:43:30 UTC 
Description of problem:
Start Xvnc

Version-Release number of selected component:
selinux-policy-3.13.1-191.16.fc24.noarch

Additional info:
reporter:       libreport-2.7.2
hashmarkername: setroubleshoot
kernel:         4.7.4-200.fc24.x86_64
type:           libreport
Note You need to log in before you can comment on or make changes to this bug.