CentOS Stream 10 – Common Problem 115 – Diagnosis and Fix

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

/var/log/journal consumes excessive space and triggers free-space alerts.

Environment & Reproduction

Common on busy servers without SystemMaxUse or SystemKeepFree configured.

Root Cause Analysis

Persistent journal retention exceeds capacity policies.

Quick Triage

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

Step-by-Step Diagnosis

Identify chatty units with journalctl –no-pager –since for ranking.

Solution – Primary Fix

Set SystemMaxUse and SystemMaxFileSize, then vacuum with journalctl –vacuum-size.

Solution – Alternative Approaches

Disable persistent journal and rely on rsyslog forwarding instead.

Verification & Acceptance Criteria

Disk usage stays within budget and oldest journals rotate predictably.

Rollback Plan

Restore Storage=persistent if forensic retention is required.

Prevention & Hardening

Forward journal to remote syslog for compliance.

Related Errors & Cross-Refs

Related to rsyslog and SystemKeepFree thresholds.

Related tutorial: View the step-by-step tutorial for centos-stream-10.

View all centos-stream-10 tutorials on the Tutorials Hub →

Browse all common problems & solutions on the Tutorials Hub.

References & Further Reading

journald.conf and journalctl manuals.