Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
+++ This bug was initially created as a clone of Bug #1456262 +++
As of pcp-3.11.10 in Fedora, the /var/lib/pcp/config/pmlogconf/zeroconf/* files are included in the base pcp package. These files cause frequent logging of high-churn proc.* metrics if one runs pmlogconf, even if one did not opt into the "pcp-zeroconf" subpackage. This could mean a large unintended & undocumented increase to the default amount of data being logged ... except that normal pmloggers run under uid pcp, thus can't fetch most of those proc metrics unless running with "pmdaproc -A"!
Please consider moving these pmlogconf/zeroconf/* files out of the pcp base package, and check their functionality vs. pmdaproc non-A.
--- Additional comment from Nathan Scott on 2017-05-28 18:01:57 EDT ---
Must be something specific to fedora.spec I guess, the ./Makepkgs build don't exhibit this problem - could you take a peek please Lukas?
Thanks.
--- Additional comment from Mark Goodwin on 2017-05-28 20:39 EDT ---
Attached patch (untested) should fix it by filtering all zeroconf files out of base.list. This would of course have to be pushed to fedora separately as a spec update.
--- Additional comment from Frank Ch. Eigler on 2017-05-29 10:45:39 EDT ---
Since these proc.* metrics are only available to -h local: type connections, not remote ones (in default pmdaproc configs), perhaps they should be somehow identified specially. That way, only a 'primary' pmlogger would see them, not remote-pmcd ones. Reminds me of the customized configuration of the 'primary' pmie.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHEA-2017:1968