Bug 1540941

Summary:	systemd doesn't reap zombies after it crashes
Product:	Red Hat Enterprise Linux 7	Reporter:	Michal Sekletar <msekleta>
Component:	systemd	Assignee:	systemd-maint
Status:	CLOSED ERRATA	QA Contact:	Frantisek Sumsal <fsumsal>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	7.4	CC:	fsumsal, systemd-maint-list, thozza
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	systemd-219-54.el7	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-04-10 11:25:34 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:

Description Michal Sekletar 2018-02-01 11:24:39 UTC

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

Comment 4 Lukáš Nykrýn 2018-02-06 14:26:10 UTC

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

Comment 9 errata-xmlrpc 2018-04-10 11:25:34 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-2018:0711