Process & Resource Monitoring (Top/Htop/Ps/Systemd)
Stop guessing why your systemd service keeps restarting
🧩 The Challenge
You know that feeling when a service keeps failing and systemd refuses to give you the actual exit code? I spent three hours last week chasing a segfault that turned out to be an OOM kill because the status logs were just showing a generic error code.
đź’ˇ The Fix
Just use systemd-analyze to pull the exact process exit status and signal information directly from the unit’s recent history. It stops the guessing game and tells you exactly which signal nuked your process.
systemd-analyze exit-status $(systemctl show -p ExecMainStatus --value your-service-name.service)⚙️ Why It Works
This command translates those cryptic exit codes from the service manager into human-readable signals, saving you from digging through header files or hoping you remember what signal 9 actually means. It’s a total lifesaver when the service crashes before it can even write a log line.
🚀 Pro-Tip: Run journalctl -u your-service-name -r to see the last fifty lines in reverse order, which usually shows the kernel’s final thoughts on the crash.
Linux Tips & Tricks | © ngelinux.com | 9/8/2026