Affected versions: CentOS Stream 9

📖 ~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 grows beyond expected size on CentOS Stream 9.

Environment & Reproduction

Hosts with verbose application logging going to systemd journal.

cat /etc/os-release
uname -r
rpm -qa | grep 

Root Cause Analysis

SystemMaxUse not set or journal rotated less aggressively than expected.

Quick Triage

Confirm package, network, SELinux and firewall state.

journalctl --disk-usage
df -h /var
cat /etc/systemd/journald.conf

Step-by-Step Diagnosis

Drill into logging/journald state and recent journal entries to isolate the failure.

journalctl --vacuum-size=500M --dry-run
ls -lh /var/log/journal/
Illustrative mockup for centos-stream-9 — cs9-b02-p044-diag
Diagnosis console for journald consumes excess disk on CentOS Stream 9 — Illustrative mockup — Progressive Robot

Solution – Primary Fix

Apply the standard remediation for logging/journald on CentOS Stream 9.

Still having issues? Our IT Solutions & Services team can diagnose and resolve this for you. Get in touch for a free consultation.

sudo sed -i 's/^#SystemMaxUse.*/SystemMaxUse=500M/' /etc/systemd/journald.conf
sudo systemctl restart systemd-journald
sudo journalctl --vacuum-size=500M
Illustrative mockup for centos-stream-9 — cs9-b02-p044-fix
Remediation output for journald consumes excess disk on CentOS Stream 9 — Illustrative mockup — Progressive Robot

Solution – Alternative Approaches

Forward critical logs to rsyslog or remote SIEM.

Verification & Acceptance Criteria

Validate the fix with positive functional checks before closing.

journalctl --disk-usage
df -h /var

Rollback Plan

Revert to the previous known-good configuration if the fix regresses.

sudo sed -i '/SystemMaxUse=500M/d' /etc/systemd/journald.conf
sudo systemctl restart systemd-journald

Prevention & Hardening

Codify the fix in configuration management and add monitoring.

Manage journald.conf via Ansible role and template.

rsyslog imjournal stale state.

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

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

Browse all common problems & solutions on the Tutorials Hub.

References & Further Reading

systemd-journald.conf(5).

Need Expert Help?

If you cannot resolve this yourself, our team offers hands-on Server Management, Managed IT Services, and flexible Support Plans. Contact us today — we respond within one business day.