Journal persistent logging fails after reboot
Issue
-
This issue happens only if Persistent logging for the Journal is turned on in
/etc/systemd/journald.confor/var/log/journalexists on the root filesystem and/varor/var/logis on a dedicated filesystem# grep ^Storage /etc/systemd/journald.conf Storage=persistentor
# mount --bind / /mnt # test -d /mnt/var/log/journal; echo $? 0 # umount /mnt -
After a reboot,
systemd-journalddoesn't log to/var/log/messages -
After a reboot,
journalctl --list-bootsdoesn't find any journal# journalctl --list-boots No journal files were found. -
After a reboot,
journalctl -bdisplays no log# journalctl -b No journal files were found. -- No entries --
Environment
- Red Hat Enterprise Linux (RHEL) 7
systemd-journaldstorage set to Persistent/varor/var/logon a dedicated filesystem
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.
Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.
