Debian 13 Journal Logs Grow Unbounded and Consume 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 usage rises rapidly and can trigger application outages due to low space.

Environment & Reproduction

Debian 13 nodes with verbose logging and no journal retention limits.

Root Cause Analysis

Persistent journal storage accumulates without configured size or time boundaries.

Quick Triage

Measure journal footprint and confirm whether persistent storage is enabled.

Step-by-Step Diagnosis

Identify noisy units and inspect log growth trends across recent boots.

Solution – Primary Fix

Apply journald limits, vacuum old entries, and restart journald safely.

Solution – Alternative Approaches

Forward logs to centralized collectors and use low local retention.

Verification & Acceptance Criteria

Journal size remains within policy and disk free space stabilizes.

Rollback Plan

Restore previous journald config if troubleshooting requirements need longer retention.

Prevention & Hardening

Set disk alerts and enforce log budget limits through baseline templates.

Related Errors & Cross-Refs

Related incidents include /var full and interrupted package transactions.

Related tutorial: View the step-by-step tutorial for Debian 13.

View all Debian 13 tutorials on the Tutorials Hub →

Browse all common problems & solutions on the Tutorials Hub.

References & Further Reading

systemd-journald man page and Debian operational logging recommendations.