Systemd journal missing kernel boot messages

I’m having a problem where systemd-journald is losing all of the kernel boot messages before the journal is started. Just wondering if anyone else has seen this and knows how to fix it.

Nov 07 09:28:55 bomba systemd-journald[370]: Journal started
Nov 07 09:28:55 bomba systemd-journald[370]: Runtime Journal (/run/log/journal/625eb56da3da4762ad9efd4e4c75d5df) is 8.0M, max 391.2M, 383.2M free.
Nov 07 09:28:55 bomba systemd[1]: Condition check resulted in Flush Journal to Persistent Storage being skipped.
Nov 07 09:28:55 bomba systemd[1]: Starting Flush Journal to Persistent Storage...
Nov 07 09:28:55 bomba systemd-journald[370]: Time spent on flushing to /var is 107.286ms for 4 entries.
Nov 07 09:28:55 bomba systemd-journald[370]: System Journal (/var/log/journal/625eb56da3da4762ad9efd4e4c75d5df) is 32.0M, max 32.0M, 0B free.
Nov 07 09:28:56 bomba systemd-journald[370]: Missed 769 kernel messages

I’m having a problem where systemd-journald is losing all of the kernel boot messages before the journal is started. Just wondering if anyone else has seen this and knows how to fix it.

Please do:

$ sudo mkdir -p /etc/kernel/cmdline.d/
$ echo "log_buf_len=1M" | sudo tee /etc/kernel/cmdline.d/log_buf_len.conf
$ sudo clr-boot-manager update

and reboot :wink:

This will increase the kernel buffer length to 1M.

2 Likes

Firstly, thanks for the fast response; that was impressive. I tried this already and increased the buffer to 4M. But just to be sure, I followed your instructions and rebooted. The behavior is the same — all messages prior to the journal starting are missing.

Please modify the journald.conf settings

$ sudo mkdir -p /etc/systemd/journald.conf.d
$ sudo cp /usr/lib/systemd/journald.conf.d/clear.conf  /etc/systemd/journald.conf.d

and edit /usr/lib/systemd/journald.conf.d/clear.conf and you need.

Example:

[Journal]
Storage=persistent
Compress=No
SystemMaxUse=100M
SystemMaxFileSize=20M
TTYPath=/dev/tty12

I tried the changes to the journald config and still have the same results with the missed kernel messages.