Red Hat Bugzilla – Bug 1286361
SELinux is preventing pmcd from 'read' accesses on the file pmlogger_daily.pid.
Last modified: 2016-04-06 10:55:01 EDT
Description of problem: probably a dupe of the F22 Bug 1259127 SELinux is preventing pmcd from 'read' accesses on the file pmlogger_daily.pid. ***** Plugin catchall (100. confidence) suggests ************************** If you believe that pmcd should be allowed read access on the pmlogger_daily.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: # grep pmcd /var/log/audit/audit.log | audit2allow -M mypol # semodule -i mypol.pp Additional Information: Source Context system_u:system_r:pcp_pmcd_t:s0 Target Context system_u:object_r:cron_var_run_t:s0 Target Objects pmlogger_daily.pid [ file ] Source pmcd Source Path pmcd Port <Unknown> Host (removed) Source RPM Packages Target RPM Packages Policy RPM selinux-policy-3.13.1-154.fc23.noarch Selinux Enabled True Policy Type targeted Enforcing Mode Enforcing Host Name (removed) Platform Linux (removed) 4.2.6-300.fc23.x86_64 #1 SMP Tue Nov 10 19:32:21 UTC 2015 x86_64 x86_64 Alert Count 5 First Seen 2015-11-09 00:10:12 CET Last Seen 2015-11-28 00:10:12 CET Local ID 8beccc5e-9cd6-4776-940e-178fc9355de2 Raw Audit Messages type=AVC msg=audit(1448665812.838:1908): avc: denied { read } for pid=1773 comm="pmcd" name="pmlogger_daily.pid" dev="tmpfs" ino=16490635 scontext=system_u:system_r:pcp_pmcd_t:s0 tcontext=system_u:object_r:cron_var_run_t:s0 tclass=file permissive=0 Hash: pmcd,pcp_pmcd_t,cron_var_run_t,file,read Version-Release number of selected component: selinux-policy-3.13.1-154.fc23.noarch Additional info: reporter: libreport-2.6.3 hashmarkername: setroubleshoot kernel: 4.2.6-300.fc23.x86_64 type: libreport Potential duplicate: bug 1259127
Is "pmlogger_daily.pid" created by cron?
pcp folks, Any help here?
(In reply to Miroslav Grepl from comment #1) > Is "pmlogger_daily.pid" created by cron? cron runs a pmlogger admin/maintenance script (pmlogger_daily), which is what leads to this pmlogger_daily.pid file being created and (attempted to be) read. $ cat /etc/cron.d/pcp-pmlogger # Performance Co-Pilot crontab entries for a monitored site # with one or more pmlogger instances running # # daily processing of archive logs (with compression enabled) 10 0 * * * pcp /usr/libexec/pcp/bin/pmlogger_daily -X xz -x 3 # every 30 minutes, check pmlogger instances are running 25,55 * * * * pcp /usr/libexec/pcp/bin/pmlogger_check -C
*** Bug 1259127 has been marked as a duplicate of this bug. ***
I believe this will be coming from pmdapmcd which lives as a DSO inside pmcd, and the "pmcd.services" PCP metric. We can restrict evaluation of those PID files to a subset of core services for that metric - we don't really need to report on pmlogger_daily.pid, so its not a problem that the access fails here (other than the AVC denial warnings its generating of course). I'll fix this up in PCP.
pcp-3.11.1-1.fc24 has been submitted as an update to Fedora 24. https://bodhi.fedoraproject.org/updates/FEDORA-2016-90112fb9ca
pcp-3.11.1-1.fc23 has been submitted as an update to Fedora 23. https://bodhi.fedoraproject.org/updates/FEDORA-2016-e687eabad0
pcp-3.11.1-1.fc22 has been submitted as an update to Fedora 22. https://bodhi.fedoraproject.org/updates/FEDORA-2016-4969de37e5
pcp-3.11.1-1.el5 has been submitted as an update to Fedora EPEL 5. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2016-5b519318e0
pcp-3.11.1-1.fc24 has been pushed to the Fedora 24 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2016-90112fb9ca
pcp-3.11.1-1.el5 has been pushed to the Fedora EPEL 5 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2016-5b519318e0
pcp-3.11.1-1.fc22 has been pushed to the Fedora 22 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2016-4969de37e5
pcp-3.11.1-1.fc23 has been pushed to the Fedora 23 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2016-e687eabad0
pcp-3.11.1-1.fc24 has been pushed to the Fedora 24 stable repository. If problems still persist, please make note of it in this bug report.
pcp-3.11.1-1.fc23 has been pushed to the Fedora 23 stable repository. If problems still persist, please make note of it in this bug report.
pcp-3.11.1-1.fc22 has been pushed to the Fedora 22 stable repository. If problems still persist, please make note of it in this bug report.
pcp-3.11.1-1.el5 has been pushed to the Fedora EPEL 5 stable repository. If problems still persist, please make note of it in this bug report.