XK0-004 · Question #276
An administrator is troubleshooting to determine why backups are failing on a particular server. The administrator runs the ps command and analyzes the following output. The administrator runs kill…
The correct answer is B. The backup process is a zombie process, and the system needs to be rebooted. A zombie (defunct) process has already exited but has not been reaped by its parent; because the process is no longer running, SIGKILL (kill -9) has no effect and a reboot is typically required to clear it.
Question
An administrator is troubleshooting to determine why backups are failing on a particular server. The administrator runs the ps command and analyzes the following output. The administrator runs kill -9 10112 yet the process remains. Which of the following BEST describes the issue and how to fix it?
Options
- AThe backup process is still running and needs to be killed with kill -9 --force 10112.
- BThe backup process is a zombie process, and the system needs to be rebooted.
- CThe backup process is out of memory, and more memory needs to be added to the system.
- DThe backup process is using 100% of system resources and needs to be rescheduled with renice.
How the community answered
(32 responses)- A16% (5)
- B72% (23)
- C3% (1)
- D9% (3)
Why each option
A zombie (defunct) process has already exited but has not been reaped by its parent; because the process is no longer running, SIGKILL (kill -9) has no effect and a reboot is typically required to clear it.
kill -9 --force is not a valid option for the kill command; additionally, SIGKILL is already the most forceful signal and cannot be caught or ignored, yet it still has no effect on zombie processes.
A zombie process appears in ps output with state 'Z' (defunct) - it has completed execution but its exit status has not been collected by the parent process via wait(). Because the process itself is no longer alive, sending any signal including SIGKILL does nothing; the process entry persists until the parent reaps it or the system is rebooted, which causes init/systemd to reparent and clean up orphaned zombies.
An out-of-memory condition would manifest as the OOM killer terminating processes, not as a process that ignores SIGKILL; memory pressure does not cause a process to become un-killable.
renice changes the scheduling priority of a running process to reduce CPU usage, but it does not address a zombie process that is already dead and consuming no CPU or memory resources.
Concept tested: Linux zombie process state and SIGKILL limitations
Source: https://man7.org/linux/man-pages/man5/proc.5.html
Topics
Community Discussion
No community discussion yet for this question.