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.
Description of problem:
When pmie is configured to connect to a remote pmcd, it still needs a locally run pmcd to start. Not having locally running pmcd leads to fail of pmie.service start.
Version-Release number of selected component (if applicable):
* pcp-5.2.5-3.el8
How reproducible:
Always
Steps to Reproduce:
1. Install a pcp-5.2.5-3.el8 on RHEL-8.4 on two machines
2. Start pmcd on one of those machines
3. On the second machine configure pmie in /etc/pcp/pmie/control to use the pmcd on the first machine
4. Start pmie service on the second machine
Actual results:
The start of pmie on the second machine fails after 60 seconds:
# systemctl start pmie
Job for pmie.service failed because the control process exited with error code.
See "systemctl status pmie.service" and "journalctl -xe" for details.
Expected results:
The pmie service starts successfully.
Additional info:
Diving into the /usr/libexec/pcp/lib/pmie script, used by pmie unit file to start the pmie service, shows the issue is with "pmcd_wait" which tries to connect pmcd via "unix:" socket instead of connecting to the remote pmcd. The "pmcd_wait" imo needs to be run with "--host" switch pointing to the remote pmcd as configured in /etc/pcp/pmie/control file.
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