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.

Bug 1698517

Summary: pmdaroot doesn't reap zombies
Product: Red Hat Enterprise Linux 7 Reporter: Renaud Métrich <rmetrich>
Component: pcpAssignee: Nathan Scott <nathans>
Status: CLOSED ERRATA QA Contact: Michal Kolar <mkolar>
Severity: medium Docs Contact:
Priority: urgent    
Version: 7.6CC: apathaka, fche, fkrska, lberk, mgoodwin, mkolar, nathans, patrickm
Target Milestone: rcKeywords: ZStream
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1703925 (view as bug list) Environment:
Last Closed: 2019-08-06 12:48:17 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1703925    

Description Renaud Métrich 2019-04-10 14:12:23 UTC
Description of problem:

A customer reported tons of "pmdalinux" and "pmdaproc" zombies on his system, with "pmdaroot" being the parent.
I do not see any code in "pmdaroot" to reap the zombies or ignore sigchild.


Version-Release number of selected component (if applicable):

pcp-4.1.0-5.el7_6.x86_64


How reproducible:

Always, with pmie.service disabled


Steps to Reproduce:
1. Start pcmd

  # systemctl start pmcd

2. Kill a child

  # pkill pmdaproc
  # ps -eaf | grep pmdaproc


Actual results:

root     12819 12818  0 15:29 ?        00:00:00 [pmdaproc] <defunct>


Expected results:

No zombie


Additional info:

Apparently enabling pmie.service makes pmdaroot reap somehow the zombies.

Comment 2 Nathan Scott 2019-04-11 00:54:50 UTC
Fixed upstream now, thanks Renaud.

commit c12aea5448810a4719f46a92a1c11f624311719e
Author: Nathan Scott <nathans>
Date:   Thu Apr 11 10:49:23 2019 +1000

    pmdaroot: ensure zombie PMDA processes are reaped
    
    PMDAs started by pmdaroot that exit unexpectedly (i.e.
    not usual pmdaroot mechanisms) were not being correctly
    waited for - add a non-blocking waitpid call into the
    pmdaroot main loop to harvest any children.
    
    QA test 1218 is added to expose the problem and also to
    exercise the fix.
    
    Resolves Red Hat BZ #1698517.

Comment 7 Michal Kolar 2019-06-06 08:23:52 UTC
Reproduced against pcp-4.1.0-4.el7 and verified against pcp-4.3.2-2.el7.

Comment 9 errata-xmlrpc 2019-08-06 12:48:17 UTC
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, 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-2019:2111