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.
DescriptionAndreas Gerstmayr
2021-01-07 15:40:37 UTC
Description of problem:
Some metrics get logged twice every X seconds. This results in higher storage space requirements for pmlogger archives and for the redis database (if configured).
Version-Release number of selected component (if applicable):
pcp-5.1.1-3
How reproducible:
always
Steps to Reproduce:
1. dnf install -y pcp-zeroconf redis
2. systemctl start redis pmproxy
3. wait for some time to get logged metrics (few minutes)
Actual results:
Metrics are logged twice every 10 seconds:
[root@localhost ~]# pmseries "kernel.all.pswitch[count:10]"
300cd8fd0d9e258e68f309d9bbaad7e78392a2b5
[Thu Jan 7 10:34:19.656194000 2021] 203594
[Thu Jan 7 10:34:19.644994000 2021] 203579
[Thu Jan 7 10:34:09.738189000 2021] 201359
[Thu Jan 7 10:34:09.644312000 2021] 195104
[Thu Jan 7 10:33:59.732399000 2021] 187307
[Thu Jan 7 10:33:59.729557000 2021] 187295
[root@localhost ~]# pmval -U /var/log/pcp/pmlogger/host-10-0-136-73/20210107.10.33.0 kernel.all.pswitch
metric: kernel.all.pswitch
archive: /var/log/pcp/pmlogger/host-10-0-136-73/20210107.10.33.0
host: host-10-0-136-73
start: Thu Jan 7 10:33:49 2021
end: Thu Jan 7 10:35:19 2021
semantics: cumulative counter (converting to rate)
units: count (converting to count / sec)
samples: all
10:33:49.844 5.683E+04
10:33:50.148 Archive logging suspended
10:33:59.732 4222.
10:33:59.733 Archive logging suspended
10:34:09.738 6.663E+04
10:34:19.644 224.1
10:34:19.656 1339.
10:34:29.643 275.0
10:34:29.652 1381.
10:34:39.643 188.4
10:34:39.651 1257.
10:34:49.644 179.3
10:34:49.652 1601.
10:34:59.643 254.7
10:34:59.652 1511.
10:35:09.643 209.0
10:35:09.650 1806.
10:35:19.643 191.5
10:35:19.651 1715.
Expected results:
Metrics are logged once every X seconds.
Additional info:
This bug doesn't affect all metrics (for example mem.vmstat.pgfault is not affected by this bug in the test environment).
This issue is fixed in upstream since PCP 5.2.1. Requesting to backport this fix for RHEL 8.3.
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 (pcp bug fix and enhancement update), 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/RHBA-2021:1754
Description of problem: Some metrics get logged twice every X seconds. This results in higher storage space requirements for pmlogger archives and for the redis database (if configured). Version-Release number of selected component (if applicable): pcp-5.1.1-3 How reproducible: always Steps to Reproduce: 1. dnf install -y pcp-zeroconf redis 2. systemctl start redis pmproxy 3. wait for some time to get logged metrics (few minutes) Actual results: Metrics are logged twice every 10 seconds: [root@localhost ~]# pmseries "kernel.all.pswitch[count:10]" 300cd8fd0d9e258e68f309d9bbaad7e78392a2b5 [Thu Jan 7 10:34:19.656194000 2021] 203594 [Thu Jan 7 10:34:19.644994000 2021] 203579 [Thu Jan 7 10:34:09.738189000 2021] 201359 [Thu Jan 7 10:34:09.644312000 2021] 195104 [Thu Jan 7 10:33:59.732399000 2021] 187307 [Thu Jan 7 10:33:59.729557000 2021] 187295 [root@localhost ~]# pmval -U /var/log/pcp/pmlogger/host-10-0-136-73/20210107.10.33.0 kernel.all.pswitch metric: kernel.all.pswitch archive: /var/log/pcp/pmlogger/host-10-0-136-73/20210107.10.33.0 host: host-10-0-136-73 start: Thu Jan 7 10:33:49 2021 end: Thu Jan 7 10:35:19 2021 semantics: cumulative counter (converting to rate) units: count (converting to count / sec) samples: all 10:33:49.844 5.683E+04 10:33:50.148 Archive logging suspended 10:33:59.732 4222. 10:33:59.733 Archive logging suspended 10:34:09.738 6.663E+04 10:34:19.644 224.1 10:34:19.656 1339. 10:34:29.643 275.0 10:34:29.652 1381. 10:34:39.643 188.4 10:34:39.651 1257. 10:34:49.644 179.3 10:34:49.652 1601. 10:34:59.643 254.7 10:34:59.652 1511. 10:35:09.643 209.0 10:35:09.650 1806. 10:35:19.643 191.5 10:35:19.651 1715. Expected results: Metrics are logged once every X seconds. Additional info: This bug doesn't affect all metrics (for example mem.vmstat.pgfault is not affected by this bug in the test environment). This issue is fixed in upstream since PCP 5.2.1. Requesting to backport this fix for RHEL 8.3.