Description of problem: I see this problem when I just boot the system. Somewhere in booting will hit this problem. SELinux is preventing pmcd from 'read' accesses on the lnk_file primary. ***** Plugin catchall (100. confidence) suggests ************************** If you believe that pmcd should be allowed read access on the primary lnk_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 'pmcd' --raw | audit2allow -M my-pmcd # semodule -X 300 -i my-pmcd.pp Additional Information: Source Context system_u:system_r:init_t:s0 Target Context system_u:object_r:pcp_var_lib_t:s0 Target Objects primary [ lnk_file ] Source pmcd Source Path pmcd Port <Unknown> Host (removed) Source RPM Packages Target RPM Packages Policy RPM selinux-policy-3.13.1-260.13.fc26.noarch Selinux Enabled True Policy Type targeted Enforcing Mode Enforcing Host Name (removed) Platform Linux (removed) 4.13.9-200.fc26.x86_64 #1 SMP Mon Oct 23 13:52:45 UTC 2017 x86_64 x86_64 Alert Count 1 First Seen 2017-11-08 19:37:13 JST Last Seen 2017-11-08 19:37:13 JST Local ID efb87f32-c8e0-4053-9f27-138cc69136d9 Raw Audit Messages type=AVC msg=audit(1510137433.948:3122): avc: denied { read } for pid=323 comm="pmcd" name="primary" dev="dm-2" ino=461569 scontext=system_u:system_r:init_t:s0 tcontext=system_u:object_r:pcp_var_lib_t:s0 tclass=lnk_file permissive=0 Hash: pmcd,init_t,pcp_var_lib_t,lnk_file,read Version-Release number of selected component: selinux-policy-3.13.1-260.13.fc26.noarch Additional info: component: selinux-policy reporter: libreport-2.9.3 hashmarkername: setroubleshoot kernel: 4.14.16-300.fc27.x86_64 type: libreport
pmcd is running with the wrong label. Is this the standard pmcd? restorecon -v /usr/bin/pmcd Now restart it and the problem should go away.
This message is a reminder that Fedora 27 is nearing its end of life. On 2018-Nov-30 Fedora will stop maintaining and issuing updates for Fedora 27. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '27'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 27 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 27 changed to end-of-life (EOL) status on 2018-11-30. Fedora 27 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.