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:
Customer reports that since RHEL 7.7, the following is logged after a reboot:
Feb 11 08:38:07 xx-xx-xxxx pmie[17588]: # /usr/bin/systemctl enable pmie.service
Feb 11 08:38:08 xx-xx-xxxx systemd[1]: pmie.service: Supervising process 17800 which is not our child. We'll most likely not notice when it exits.
Feb 11 08:38:08 xx-xx-xxxx pmlogger[17919]: # /usr/bin/systemctl enable pmlogger.service
Feb 11 08:38:16 xx-xx-xxxx systemd[1]: pmlogger.service: Supervising process 23392 which is not our child. We'll most likely not notice when it exits.
Feb 11 08:38:16 xx-xx-xxxx systemd[1]: pmlogger.service: Supervising process 23392 which is not our child. We'll most likely not notice when it exits.
Feb 11 08:38:16 xx-xx-xxxx systemd[1]: pmlogger.service: Supervising process 23392 which is not our child. We'll most likely not notice when it exits.
Feb 11 09:01:23 xx-xx-xxxx systemd[1]: pmlogger.service: Supervising process 8202 which is not our child. We'll most likely not notice when it exits.
Version-Release number of selected component (if applicable): 4.3.2
How reproducible: Always
Steps to Reproduce:
1. # yum install pcp
2. # systemctl enable pmie pmlogger
3. # reboot
4. Check logs
Actual results:
Log is polluted with unnecessary log messages.
Expected results:
No pollution of the logs files.
Additional info:
* This didn't happen with RHEL 7.6 and therefore can be seen as a regression in RHEL 7.7.
* Customer case will be linked.
* Related RHBZ#1780003.
I've adapted the title of this BZ, since a second issue came in that is related. Therefore I'd suggest we try to generally improve the (system) logging of PCP.
The log messages do not contain *is not our child* or *does not belong to service* statements any more.
The current messages looks legit to me when starting/stopping pcp services.
Tested with pcp-5.1.1-1.el8
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-2020:4684
Description of problem: Customer reports that since RHEL 7.7, the following is logged after a reboot: Feb 11 08:38:07 xx-xx-xxxx pmie[17588]: # /usr/bin/systemctl enable pmie.service Feb 11 08:38:08 xx-xx-xxxx systemd[1]: pmie.service: Supervising process 17800 which is not our child. We'll most likely not notice when it exits. Feb 11 08:38:08 xx-xx-xxxx pmlogger[17919]: # /usr/bin/systemctl enable pmlogger.service Feb 11 08:38:16 xx-xx-xxxx systemd[1]: pmlogger.service: Supervising process 23392 which is not our child. We'll most likely not notice when it exits. Feb 11 08:38:16 xx-xx-xxxx systemd[1]: pmlogger.service: Supervising process 23392 which is not our child. We'll most likely not notice when it exits. Feb 11 08:38:16 xx-xx-xxxx systemd[1]: pmlogger.service: Supervising process 23392 which is not our child. We'll most likely not notice when it exits. Feb 11 09:01:23 xx-xx-xxxx systemd[1]: pmlogger.service: Supervising process 8202 which is not our child. We'll most likely not notice when it exits. Version-Release number of selected component (if applicable): 4.3.2 How reproducible: Always Steps to Reproduce: 1. # yum install pcp 2. # systemctl enable pmie pmlogger 3. # reboot 4. Check logs Actual results: Log is polluted with unnecessary log messages. Expected results: No pollution of the logs files. Additional info: * This didn't happen with RHEL 7.6 and therefore can be seen as a regression in RHEL 7.7. * Customer case will be linked. * Related RHBZ#1780003.