Ubuntu 16.04 LTS Journald Log Growth Consumes Disk

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

Disk fills unexpectedly and core services degrade due to lack of writable space.

Environment & Reproduction

Seen on noisy workloads with verbose logging and default retention settings.

Root Cause Analysis

Unbounded journal growth accumulates large binary log files over time.

Quick Triage

Measure journal size and identify top chatty services generating excessive events.

Step-by-Step Diagnosis

Inspect journald disk usage, retention config, and service-level log verbosity settings.

Solution – Primary Fix

Vacuum old journal files, enforce size and time retention limits, and reduce noisy log sources.

Solution – Alternative Approaches

Forward logs centrally and keep local journal minimal for troubleshooting windows.

Verification & Acceptance Criteria

Disk usage stabilizes and journal retention remains within configured boundaries.

Rollback Plan

Restore previous retention policy if shorter history impacts incident investigations.

Prevention & Hardening

Set default log limits in base images and monitor log growth anomalies.

Related Errors & Cross-Refs

Related to root filesystem exhaustion and service startup failures due to ENOSPC.

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

View all Ubuntu 16.04 LTS tutorials on the Tutorials Hub →

Browse all common problems & solutions on the Tutorials Hub.

References & Further Reading

See journald configuration manuals and Linux logging architecture references.