Logging & Journald

Stop systemd from hiding your boot-time log spew

🧩 The Challenge

You know that feeling when a server reboots and the SSH connection drops, but the logs from the early boot process vanish before you can even log back in? It is a nightmare when you’re trying to hunt down a race condition that only triggers while the system is coming up.

💡 The Fix

Change the persistent storage setting in the journald config file to force it to keep everything on disk instead of memory. You will finally have a history that survives a hard power cycle.

sed -i 's/#Storage=auto/Storage=persistent/' /etc/systemd/journald.conf
systemctl restart systemd-journald

⚙️ Why It Works

Setting this to persistent tells the service to write logs directly to /var/log/journal, which ensures they aren’t volatile. Making this change essentially locks in your debugging trail for the next time things go south.

🚀 Pro-Tip: Create the directory first if it’s missing, or the service might just ignore you.

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