Logging & Journald

Catch systemd boot loops before they bury your logs

🧩 The Challenge

Dealing with a service that crashes immediately on boot is a special kind of hell because the logs rotate before you can even SSH in. You end up staring at a blank screen wondering if the system is even trying to start your app.

💡 The Fix

Use the journald boot offset flag to grab the logs from the previous failed attempt. It keeps you from having to frantically grep through a thousand lines of boot noise.

journalctl -b -1 -u your-service-name.service

⚙️ Why It Works

Passing the negative integer to the boot flag tells journald to ignore the current session and look back at the most recent finished boot cycle. It saves you from having to remember exactly when the crash happened.

🚀 Pro-Tip: Use -n 50 to tack on the last few lines so you don’t get hit with a wall of text.

Linux Tips & Tricks | © ngelinux.com | 10/28/2026