Logging & Journald

Stop journald from dumping your logs to the ether

🧩 The Challenge

You finally have that production issue where the logs vanish the moment the server reboots because journald decided to store everything in volatile RAM. Trying to debug a crash that happened three hours ago is impossible when the logs don’t survive a power cycle.

💡 The Fix

Flip the storage setting in the config file to force persistent logging on disk. It takes five minutes and saves your hide when the audit trail is all you have left.

mkdir -p /var/log/journal && echo "Storage=persistent" >> /etc/systemd/journald.conf && systemctl restart systemd-journald

⚙️ Why It Works

By creating the directory manually, you signal systemd to stop using the volatile run-time directory and start writing to the permanent path. It’s a simple handshake that ensures your history stays put.

🚀 Pro-Tip: Run journalctl –vacuum-time=7d afterward so you don’t end up with ten years of useless logs eating your root partition.

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