Red Hat Bugzilla – Bug 1540941
systemd doesn't reap zombies after it crashes
Last modified: 2018-04-10 07:26:26 EDT
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