During nightly operations on a RHEL-based file-ingest server, the systemd status for ingest.service shows:
Main process exited, code=killed, status=9/KILL
The application's own log ends abruptly with the single line "Killed", and monitoring indicates that system memory was completely consumed at the same time. You need to verify whether the Linux kernel's OOM (out-of-memory) killer terminated the job. Which command will provide the most direct evidence?
The kernel writes OOM-killer decisions to the kernel log buffer. On systems that use systemd, those messages are persisted by journald and can be viewed with journalctl -k. Filtering for the well-known text that precedes an OOM event (for example, "Out of memory: Kill process …" or "Killed process …") confirms both that the OOM killer ran and which PID it chose. The other commands either show current scores (ps … oom_score), examine authentication messages (/var/log/secure), or analyze SELinux AVCs-all of which are unrelated to historical OOM-kill events.
Ask Bash
Bash is our AI bot, trained to help you pass your exam. AI Generated Content may display inaccurate information, always double-check anything important.
What is the OOM (Out-of-Memory) killer in Linux?
Open an interactive chat with Bash
How does `journalctl -k` help identify OOM killer events?
Open an interactive chat with Bash
What is the difference between `oom_score` and `oom_score_adj`?
Open an interactive chat with Bash
CompTIA Linux+ XK0-006 (V8)
Troubleshooting
Your Score:
Report Issue
Bash, the Crucial Exams Chat Bot
AI Bot
Loading...
Loading...
Loading...
IT & Cybersecurity Package Join Premium for Full Access