RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1649407 - PCP generating tons of SELinux violations
Summary: PCP generating tons of SELinux violations
Keywords:
Status: CLOSED DUPLICATE of bug 1647308
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: pcp
Version: 7.6
Hardware: All
OS: Linux
medium
medium
Target Milestone: rc
: ---
Assignee: pcp-maint
QA Contact: qe-baseos-tools-bugs
URL:
Whiteboard:
Depends On:
Blocks: 1122832
TreeView+ depends on / blocked
 
Reported: 2018-11-13 15:08 UTC by Oliver Falk
Modified: 2022-03-13 16:03 UTC (History)
17 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-03-04 00:48:34 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Oliver Falk 2018-11-13 15:08:40 UTC 
Description of problem:
With the default installation of PCP, we're observing a lot of avc: denied messages.


Version-Release number of selected component (if applicable): pcp-4.1.0-5.el7_6

How reproducible:
Always, however the exact deny messages depend on the applications installed. In this case it RHSAT 6.4.


Steps to Reproduce:
1. Install RHEL
2. Install PCP
3. Start pmcd

Actual results:

One machine:
Nov 11 03:13:14 xxx setroubleshoot: SELinux is preventing /var/lib/pcp/pmdas/linux/pmdalinux from unix_read access on the shared memory labeled postgresql_t. For complete SELinux messages run: sealert -l 2736eb3d-c900-40c3-8963-cccdd1bc8c09
Nov 11 03:13:14 xxx setroubleshoot: SELinux is preventing /var/lib/pcp/pmdas/linux/pmdalinux from unix_read access on the semaphore labeled postgresql_t. For complete SELinux messages run: sealert -l b731435c-ed5c-43ac-a4b3-4adc7d8d2b1b

Other machine:
Nov 12 15:36:17 xxy setroubleshoot: SELinux is preventing /var/lib/pcp/pmdas/linux/pmdalinux from unix_read access on the semaphore labeled rpm_script_t. For complete SELinux messages run: sealert -l 67029b6d-cc05-4115-ad59-14b8a2dd4b27
Nov 12 15:36:20 xxy setroubleshoot: SELinux is preventing /var/lib/pcp/pmdas/linux/pmdalinux from 'getattr, associate' accesses on the semaphore labeled rpm_script_t. For complete SELinux messages run: sealert -l e1ff56dd-0979-45b3-a2b3-b14f0a802ebb

Expected results:
No deny messages caused by PCP.


Additional info:
Customer case will be linked.
Comment 1 Ugo Bellavance 2019-02-18 04:53:25 UTC 
Any plans on fixing this issue?  I can see that no one from Red Hat commented and it's been 3 months now. Do you need more information?
Comment 2 Oliver Falk 2019-02-18 09:00:04 UTC 
Reassigning to selinux-policy.
Comment 5 Nathan Scott 2019-03-04 00:48:34 UTC 
Fixed by rebase in 7.7

*** This bug has been marked as a duplicate of bug 1647308 ***
Note You need to log in before you can comment on or make changes to this bug.