Persistent journal takes more than maximum limit set and vacuum doesn't happen

Solution Verified - Updated -

Issue

  • Even though a limit for persistent journal is set (e.g. SystemMaxUse=2G), the journal takes more space

    # journalctl --disk-usage
    Archived and active journals take up 2.3G in the file system.
    
  • Vacuuming manually doesn't reduce the journal space usage

    # journalctl --vacuum-size=2G
    Vacuuming done, freed 0B of archived journals from /var/log/journal/<machineid>.
    

Environment

  • Red Hat Enterprise Linux 7, 8, 9
  • systemd-journald

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content