Hide Forgot
Description of problem: SELinux is preventing systemd-logind from 'getattr' accesses on the file /dev/shm/lldpad.state. ***** Plugin restorecon (99.5 confidence) suggests ************************ If you want to fix the label. /dev/shm/lldpad.state default label should be lldpad_tmpfs_t. Then you can run restorecon. Do # /sbin/restorecon -v /dev/shm/lldpad.state ***** Plugin catchall (1.49 confidence) suggests ************************** If you believe that systemd-logind should be allowed getattr access on the lldpad.state 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: # grep systemd-logind /var/log/audit/audit.log | audit2allow -M mypol # semodule -i mypol.pp Additional Information: Source Context system_u:system_r:systemd_logind_t:s0 Target Context system_u:object_r:tmpfs_t:s0 Target Objects /dev/shm/lldpad.state [ file ] Source systemd-logind Source Path systemd-logind Port <Unknown> Host (removed) Source RPM Packages Target RPM Packages Policy RPM selinux-policy-3.13.1-168.fc24.noarch Selinux Enabled True Policy Type targeted Enforcing Mode Enforcing Host Name (removed) Platform Linux (removed) 4.5.0-0.rc0.git7.1.fc24.x86_64 #1 SMP Wed Jan 20 18:34:53 UTC 2016 x86_64 x86_64 Alert Count 1 First Seen 2016-01-21 15:27:39 EST Last Seen 2016-01-21 15:27:39 EST Local ID 2bfd5d44-596a-41d5-b29d-70e802e512d6 Raw Audit Messages type=AVC msg=audit(1453408059.455:592): avc: denied { getattr } for pid=1098 comm="systemd-logind" path="/dev/shm/lldpad.state" dev="tmpfs" ino=12603 scontext=system_u:system_r:systemd_logind_t:s0 tcontext=system_u:object_r:tmpfs_t:s0 tclass=file permissive=0 Hash: systemd-logind,systemd_logind_t,tmpfs_t,file,getattr Version-Release number of selected component: selinux-policy-3.13.1-168.fc24.noarch Additional info: reporter: libreport-2.6.3 hashmarkername: setroubleshoot kernel: 4.5.0-0.rc0.git7.1.fc24.x86_64 type: libreport Potential duplicate: bug 1190461
*** This bug has been marked as a duplicate of bug 1284293 ***