Process & Resource Monitoring (Top/Htop/Ps/Systemd)

Stop systemd from hiding the real reasons your services keep crashing

🧩 The Challenge

Dealing with a service that flaps or exits silently is a nightmare when journalctl just gives you a cryptic exit code instead of the actual error. You spend half the morning tracing files only to realize the process was killed for a reason that didn’t make it to the main log.

💡 The Fix

Crank up the logging level for that specific unit to catch the granular details you usually miss. It saves you from guessing why the binary keeps dumping core.

systemctl edit --full your-service-name.service
[Service]
Environment=SYSTEMD_LOG_LEVEL=debug

⚙️ Why It Works

Setting this environment variable forces the service to spit out internal diagnostic chatter directly into the systemd buffer before the process disappears. It turns those useless exit status messages into a readable play-by-play of the crash.

🚀 Pro-Tip: Don’t forget to remove that override after you find the bug, or your disk space will vanish into log files faster than you can blink.

Linux Tips & Tricks | © ngelinux.com | 8/12/2026