Journal Logs Consuming Excessive Disk on RHEL 9

📖 ~1 min read

Table of contents

1. Symptom & Impact
2. Environment & Reproduction
3. Root Cause Analysis
4. Quick Triage
5. Step-by-Step Diagnosis
6. Solution – Primary Fix
7. Solution – Alternative Approaches
8. Verification & Acceptance Criteria
9. Rollback Plan
10. Prevention & Hardening
11. Related Errors & Cross-Refs
12. References & Further Reading

Symptom & Impact

Root filesystem fills unexpectedly and /var/log/journal grows continuously.

Environment & Reproduction

systemd-journald retention defaults are too permissive for available disk size.

Root Cause Analysis

Run: journalctl –disk-usage and inspect /etc/systemd/journald.conf settings.

Quick Triage

Check noisy services generating high-volume logs with journalctl -u and rate patterns.

Step-by-Step Diagnosis

Capture journalctl –disk-usage output before cleanup.

Solution – Primary Fix

Capture vacuum command result and configured SystemMaxUse limits.

Solution – Alternative Approaches

Vacuum old logs: sudo journalctl –vacuum-size=1G or –vacuum-time=14d.

Verification & Acceptance Criteria

Set limits in journald.conf, e.g., SystemMaxUse=1G and RuntimeMaxUse=256M.

Rollback Plan

Restart daemon: sudo systemctl restart systemd-journald.

Prevention & Hardening

Re-run journalctl –disk-usage and verify stable growth profile over time.

Related Errors & Cross-Refs

Tune service verbosity and add monitoring alerts for journal usage thresholds.

Related tutorial: View the step-by-step tutorial for rhel-9.

View all rhel-9 tutorials on the Tutorials Hub →

Browse all common problems & solutions on the Tutorials Hub.

References & Further Reading

Restore previous journald.conf and restart systemd-journald if limits are too strict.