Ubuntu 18.04 LTS – journald logs consume 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

Persistent journal files grow rapidly and pressure root filesystem capacity.

Environment & Reproduction

Common on noisy hosts where log retention defaults exceed available disk budget.

Root Cause Analysis

Unbounded journal retention and high event volume cause sustained disk expansion.

Quick Triage

Measure journal footprint and identify top noisy services emitting excessive events.

Step-by-Step Diagnosis

Inspect journald settings, vacuum opportunities, and service-level log rates.

Solution – Primary Fix

Set journal size caps, vacuum historical logs, and reduce noisy service output.

Solution – Alternative Approaches

Forward logs centrally and keep minimal local retention on constrained nodes.

Verification & Acceptance Criteria

Journal size remains within configured thresholds across several log cycles.

Rollback Plan

Revert journald caps if forensic retention requirements are temporarily unmet.

Prevention & Hardening

Track log volume baselines and enforce environment-specific retention policy.

Related Errors & Cross-Refs

Out of disk alerts correlated with /var/log/journal growth spikes.

Related tutorial: View the step-by-step tutorial for Ubuntu 18.04 LTS.

View all Ubuntu 18.04 LTS tutorials on the Tutorials Hub →

Browse all common problems & solutions on the Tutorials Hub.

References & Further Reading

systemd-journald storage controls and Ubuntu logging operations best practices.