Logging & Journald

Get journald to spill the beans on specific boot sessions

🧩 The Challenge

Hunting for errors in a server that rebooted three days ago is a nightmare when you’re wading through thousands of lines of noise from the current uptime. I’ve wasted way too much time scrolling through logs trying to figure out which specific block of text belongs to the crash and which is just routine maintenance.

💡 The Fix

You can tell journald to only show you logs from a specific past boot using a simple offset index. It clears out the clutter so you can focus on the chaos that happened right before the box went down.

journalctl -b -1
journalctl --list-boots

⚙️ Why It Works

Negative numbers act as a relative pointer to previous boot cycles, where -1 is the last one and -2 is the one before that. Once you know the boot ID from list-boots, you can also just pass the hash directly if you need to go back weeks.

🚀 Pro-Tip: Pipe it into grep to ignore all the routine systemd noise and find that one segfault that actually matters.

Linux Tips & Tricks | © ngelinux.com | 11/15/2026