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:
New version of pcp 5.3.4-1.el9 is failing upon starting pmlogger service.
Version-Release number of selected component (if applicable):
pcp-5.3.4-1.el9
How reproducible:
# systemctl start pmlogger
Job for pmlogger.service failed because the service did not take the steps required by its unit configuration.
# systemctl status pmlogger
× pmlogger.service - Performance Metrics Archive Logger
Loaded: loaded (/usr/lib/systemd/system/pmlogger.service; disabled; vendor preset: enabled)
Active: failed (Result: protocol) since Mon 2021-10-11 04:25:21 UTC; 4s ago
Docs: man:pmlogger(1)
Process: 3953 ExecStart=/usr/libexec/pcp/lib/pmlogger start-systemd (code=exited, status=0/SUCCESS)
Main PID: 3953 (code=exited, status=0/SUCCESS)
CPU: 110ms
Oct 11 04:25:19 fedora-34-127-0-0-2-2201 systemd[1]: Starting Performance Metrics Archive Logger...
Oct 11 04:25:19 fedora-34-127-0-0-2-2201 pmlogger[3545]: /usr/libexec/pcp/lib/pmlogger: Warning: Performance Co-Pilot archive logger(s) not permanently enabled.
Oct 11 04:25:19 fedora-34-127-0-0-2-2201 pmlogger[3545]: To enable pmlogger, run the following as root:
Oct 11 04:25:19 fedora-34-127-0-0-2-2201 pmlogger[3545]: # /usr/bin/systemctl enable pmlogger.service
Oct 11 04:25:19 fedora-34-127-0-0-2-2201 systemd[1]: pmlogger.service: Failed with result 'protocol'.
Oct 11 04:25:19 fedora-34-127-0-0-2-2201 systemd[1]: Failed to start Performance Metrics Archive Logger.
Oct 11 04:25:19 fedora-34-127-0-0-2-2201 systemd[1]: pmlogger.service: Scheduled restart job, restart counter is at 1.
Additional info:
This is also broken in Fedora - https://bodhi.fedoraproject.org/updates/FEDORA-2021-83d1d8ec8a
But since it was shipped into rhel although the bodhi update was blocked and it seems it will take weeks to get the fix in, I am opening this so we can reasonably track this.
This is already fixed upstream (pcp-5.3.5 devel):
commit b9ff7d65b5e11cae35995495b4177443283c9a31
Author: Mark Goodwin <mgoodwin>
Date: Wed Oct 13 12:04:35 2021 +1100
services: remove run-level check in pmlogger systemd service config
Remove the run-level check (pmlogger_check -C flag) since systemd
uses targets for run-level checks. The run-level checks were causing
the pmlogger service to fail to manually start (via systemctl start
pmlogger) when the service is disabled.
New test qa/1889 checks pmlogger still starts even if disabled (on
systemd platforms only). qa/808 is also reworked since it was running
pmlogger_check directly and was failing every *second* run.
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 (new packages: pcp), 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-2022:2370
Description of problem: New version of pcp 5.3.4-1.el9 is failing upon starting pmlogger service. Version-Release number of selected component (if applicable): pcp-5.3.4-1.el9 How reproducible: # systemctl start pmlogger Job for pmlogger.service failed because the service did not take the steps required by its unit configuration. # systemctl status pmlogger × pmlogger.service - Performance Metrics Archive Logger Loaded: loaded (/usr/lib/systemd/system/pmlogger.service; disabled; vendor preset: enabled) Active: failed (Result: protocol) since Mon 2021-10-11 04:25:21 UTC; 4s ago Docs: man:pmlogger(1) Process: 3953 ExecStart=/usr/libexec/pcp/lib/pmlogger start-systemd (code=exited, status=0/SUCCESS) Main PID: 3953 (code=exited, status=0/SUCCESS) CPU: 110ms Oct 11 04:25:19 fedora-34-127-0-0-2-2201 systemd[1]: Starting Performance Metrics Archive Logger... Oct 11 04:25:19 fedora-34-127-0-0-2-2201 pmlogger[3545]: /usr/libexec/pcp/lib/pmlogger: Warning: Performance Co-Pilot archive logger(s) not permanently enabled. Oct 11 04:25:19 fedora-34-127-0-0-2-2201 pmlogger[3545]: To enable pmlogger, run the following as root: Oct 11 04:25:19 fedora-34-127-0-0-2-2201 pmlogger[3545]: # /usr/bin/systemctl enable pmlogger.service Oct 11 04:25:19 fedora-34-127-0-0-2-2201 systemd[1]: pmlogger.service: Failed with result 'protocol'. Oct 11 04:25:19 fedora-34-127-0-0-2-2201 systemd[1]: Failed to start Performance Metrics Archive Logger. Oct 11 04:25:19 fedora-34-127-0-0-2-2201 systemd[1]: pmlogger.service: Scheduled restart job, restart counter is at 1. Additional info: This is also broken in Fedora - https://bodhi.fedoraproject.org/updates/FEDORA-2021-83d1d8ec8a But since it was shipped into rhel although the bodhi update was blocked and it seems it will take weeks to get the fix in, I am opening this so we can reasonably track this.