My kernel update crashed this morning and I had to boot to an older kernel. I wanted to see the journal log for the crashed boot so used:
journalctl --list-boots
0 336aa03f15d3443d95e079ad17b6dc77 Fri 2018-02-02 05:49:03 MST—Fri 2018-02-02 17:57:50 MST
It's only showing the current reboot on the older kernel not the kernel update(s) that crashed a few times 10 minutes before.
How can I get persistence across reboots to view previous boot journals?
Reported as a bug that's an undocumented feature
There is a bug report filed on this topic. Because
rsyslog
already maintains multiple boot journals in/var/log/syslog
andsyslog.1
,.2.gz
,.3.gz
...syslog.7.gz
the developers felt keeping extrajournalctl
logs would waste disk space.The bug report states on January 3, 2018 that for new installs
rsyslog
will no longer be the default and thatjournalctl
will keep multiple boot data logs.Create multiple boot logs without reinstalling Ubuntu
Most of us won't do a new install so to enable multiple
journalctl
boot logs use:According to this github report the warning message on attributes can be ignored.
Interesting new flag
s
instead of the familiarx
(executable bit) in the file permissions of the newly created directory:Update 3 weeks later
lines 1-16/16 (END)