Logging & Journald

Stop your persistent logs from vanishing on every reboot

🧩 The Challenge

Dealing with a production crash is miserable when you go to check the logs only to find they disappeared because the journal is stored in volatile RAM. I spent half a day trying to debug a kernel panic that wiped the evidence the second the power cycled.

💡 The Fix

You need to tell systemd to keep these logs on disk, which keeps your boot history safe and makes post-mortem analysis actually possible.

mkdir -p /var/log/journal && systemd-tmpfiles --create --prefix /var/log/journal && systemctl restart systemd-journald

⚙️ Why It Works

Creating that directory forces the daemon to switch from its default volatile mode to persistent storage, ensuring every boot gets its own distinct journal file. It is a simple two-step handshake that stops the system from dumping your history into the bit bucket.

🚀 Pro-Tip: Use journalctl -b -1 to see the logs from your previous boot specifically.

Linux Tips & Tricks | © ngelinux.com | 7/22/2026