Journald Disk Usage Growing Too Fast

📖 ~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

/var grows quickly and journal files consume unexpected space.

Environment & Reproduction

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

Root Cause Analysis

Check if growth is due to one noisy service or broad system logging.

Quick Triage

No size limits set, high verbosity, or repeated service crash loops.

Step-by-Step Diagnosis

Set SystemMaxUse and RuntimeMaxUse, then restart systemd-journald.

Solution – Primary Fix

Vacuum old logs with journalctl –vacuum-size or –vacuum-time.

Solution – Alternative Approaches

systemctl status systemd-journald should stay active without errors.

Verification & Acceptance Criteria

No direct dependency, but remote log forwarding may add volume.

Rollback Plan

If journal path was customized, verify SELinux labels on storage path.

Prevention & Hardening

Use journalctl -p err..alert to isolate noisy failure sources.

Related Errors & Cross-Refs

Set explicit retention defaults in baseline RHEL 9 images.

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

Revert journald.conf edits and restart journald if limits are too strict.