journald Consumes Excessive Disk Space

📖 ~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 or var filesystem fills quickly while systemd-journald stores large log volumes.

Environment & Reproduction

Default journald limits are too high for disk size or noisy services flood logs.

Root Cause Analysis

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

Quick Triage

Vacuum old logs using journalctl –vacuum-time=7d or –vacuum-size=1G as policy allows.

Step-by-Step Diagnosis

Set SystemMaxUse and RuntimeMaxUse in journald.conf then restart systemd-journald.

Solution – Primary Fix

Reduce noisy unit verbosity and verify disk growth normalizes after changes.

Solution – Alternative Approaches

Confirm steady usage with repeated journalctl –disk-usage checks over time.

Verification & Acceptance Criteria

Revert aggressive retention settings if incident forensics require longer local history.

Rollback Plan

Define retention policy per server class and centralize long-term logs externally.

Prevention & Hardening

Alert on journald growth rate and filesystem thresholds for /var/log/journal.

Related Errors & Cross-Refs

Deploy journald defaults through configuration management with environment-specific caps.

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

Use journald.conf and journalctl man pages with RHEL 9 logging recommendations.