Journal persistent logging fails after reboot

Solution Verified - Updated -

Issue

  • This issue happens only if Persistent logging for the Journal is turned on in /etc/systemd/journald.conf or /var/log/journal exists on the root filesystem and /var or /var/log is on a dedicated filesystem

    # grep ^Storage /etc/systemd/journald.conf 
    Storage=persistent
    

    or

    # mount --bind / /mnt
    # test -d /mnt/var/log/journal; echo $?
    0
    # umount /mnt
    
  • After a reboot, systemd-journald doesn't log to /var/log/messages

  • After a reboot, journalctl --list-boots doesn't find any journal

    # journalctl --list-boots 
    No journal files were found.
    
  • After a reboot, journalctl -b displays no log

    # journalctl -b
    No journal files were found.
    -- No entries --
    

Environment

  • Red Hat Enterprise Linux (RHEL) 7
  • systemd-journald storage set to Persistent
  • /var or /var/log on a dedicated filesystem

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