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 systemd crashes it enters a state in which it is still running but not doing anything. It is desirable for PID1 to at least keep taking care of zombie processes that would otherwise accumulate on the system.

Version-Release number of selected component (if applicable):
systemd-219-42.el7_4.7

How reproducible:
always after systemd crash

Steps to Reproduce:
1. Create simple unit file (test.service) that spawns sleep 5, and crash-pid1.service that spawns only /bin/true
2. Patch systemd so it crashes when user attempts to start crash-pid1.service
3. systemctl --no-block start test.service
4. systemctl start crash-pid1.service
5. Wait for sleep from test.service to finish
6. Check process list using ps for any defunct processes

Actual results:
See sleep process in defunct state

Expected results:
No processes on the system are in defunct state for considerable amount of time

Additional info:
https://github.com/systemd/systemd/pull/7862

fix merged to staging branch -> https://github.com/lnykryn/systemd-rhel/pull/192 -> post

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-2018:0711