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.
Created attachment 1447846[details]
Patch against 3.12.2
Hello,
this is a backport request into RHEL 7.5:
pmdammv: resolve an instance domain setup problem
Several people (marko, lzap, tallpaul) have reported this
one, finally got to the bottom of it. The symptoms are
"Unknown or illegal instance domain identifier" errors on
indom lookups, sometimes. Root cause was a logic error
in pmdammv indom setup code incorrectly overwriting count
and offset local variables while parsing mappings.
To exercise the fix I've modernized qa/src/indom.c and
used it in new test qa/1422 to tickle the problem using
a canned MMV mapping which is known to expose it.
The original bug report (against Parfait) is this one:
https://github.com/performancecopilot/parfait/issues/53
Upstream patch:
https://github.com/performancecopilot/pcp/commit/816c9cd75a2cad0dc64323897bd811cfd8725810
I have successfully backported the patch and made a build:
https://copr.fedorainfracloud.org/coprs/lzap/pcp/
I am currently testing it. Attaching the patch:
qa/1422 | 68 ++++++++++
qa/1422.out | 33 +++++
qa/GNUmakefile | 4 +-
qa/GNUmakefile.install | 3 +-
qa/group | 1 +
qa/mmv/GNUmakefile | 16 +++
qa/mmv/GNUmakefile.install | 6 +
qa/mmv/KeyboardReader.xz | Bin 0 -> 1220 bytes
qa/mmv/pytest.xz | Bin 0 -> 416 bytes
qa/src/indom.c | 253 +++++++++----------------------------
src/pmdas/mmv/src/mmv.c | 48 ++++---
11 files changed, 216 insertions(+), 216 deletions(-)
The binary files are not part of the patch.
installing pcp-zeroconf makes some logging configuration changes:
- changing the default PMLOGGER_INTERVAL to 10 seconds in /etc/sysconfig/pmlogger
- making more pmlogconf clauses included in default logs (esp: proc metrics)
I don't think any of the default logger configurations record mmv.* metrics though, so that part would have come from somewhere. As far as I know, your pmlc instruction would -add- new mmv logging rather than modify a previous mmv logging. You may need to first send a 'log mandatory off mmv' to kill that ... not sure.