Ubuntu 24.04 LTS Excessive systemd-journald Growth Causes Disk Pressure

📖 ~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 usage rises rapidly due to unbounded journal files under `/var/log/journal`.

Environment & Reproduction

Typical on noisy services emitting high-volume logs.

journalctl --disk-usage

Root Cause Analysis

Default journald retention may be too high for current disk sizing and workload.

Quick Triage

Inspect current journald configuration and storage mode.

grep -E 'SystemMaxUse|RuntimeMaxUse|Storage' /etc/systemd/journald.conf

Step-by-Step Diagnosis

Measure journal growth and noisy units.

journalctl --since -24h | wc -l && systemctl --failed

Solution – Primary Fix

Set size caps and vacuum existing journal files.

sudo sed -i 's/^#SystemMaxUse=.*/SystemMaxUse=500M/' /etc/systemd/journald.conf && sudo systemctl restart systemd-journald && sudo journalctl --vacuum-size=500M

Solution – Alternative Approaches

Forward logs to centralized storage and reduce local retention period.

Verification & Acceptance Criteria

Journal usage remains under configured cap during normal workload.

Rollback Plan

Revert journald.conf changes and restart journald if needed.

Prevention & Hardening

Monitor log volume by service and tune noisy application logging levels.

Related Errors & Cross-Refs

Related to `/var` saturation, log rotation delays, and service crash loops.

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

View all Ubuntu 24.04 LTS tutorials on the Tutorials Hub →

Browse all common problems & solutions on the Tutorials Hub.

References & Further Reading

systemd-journald limits and Ubuntu logging best practices.