journalctl storage grows uncontrollably

📖 ~1 min read

Table of contents

1. Problem Summary
2. Symptoms
3. Diagnostics
4. Root Cause
5. Primary Fix
6. Verification
7. Prevention
8. Rollback
9. Automation
10. Command Reference
11. Escalation
12. Related Notes

Problem Summary

Systemd journal consumes excessive disk space under /var/log/journal.

Symptoms

Filesystem usage spikes and journalctl –disk-usage reports large values.

Diagnostics

Check journald.conf limits and high-volume units with journalctl –since.

Root Cause

No retention caps plus noisy services generating repetitive logs.

Primary Fix

Set SystemMaxUse and RuntimeMaxUse, then vacuum old journals.

Verification

Confirm new size policy and stable growth trend after restart.

Prevention

Tune service log levels and alert on journal growth.

Rollback

Revert journald.conf changes if troubleshooting requires longer retention.

Automation

Template journald config and reload via systemctl restart systemd-journald.

Command Reference

journalctl –disk-usage; journalctl –vacuum-size=1G

Escalation

Provide top noisy units and journald configuration.

Related Notes

Persistent logging may be required for compliance despite storage pressure.

Related tutorial: View the step-by-step tutorial for rhel-10.

View all rhel-10 tutorials on the Tutorials Hub →

Browse all common problems & solutions on the Tutorials Hub.