How can I fix this error?

I am trying to understand why journalctl -b -1 sometimes returns the following error.

Data from the specified boot (-1) is not available: No such boot ID in journal

I noticed that, when it happens, the start job for the Journal Service and the stop job for flushing the journal to the persistent storage take more time than the usual. (Only in one case, they took about three minutes before completing or being interrupted.)

I decided to manually flush the journal, to see which error would be thrown.

sudo journalctl --flush doesn’t return any error. sudo journalctl --sync returns this error, after a minute.

Failed to execute varlink call: Connection reset by peer

How can I fix this error?

First of all, you need to configure the saving of logs:

$ sudo nano /etc/systemd/journald.conf

You can use any other text editor instead of nano

You also need to familiarize yourself with

This has been fixed when I added pci=noaer to the boot settings, which was suggested in Is there a way to avoid some messages are logged in the journal?

Once I did that, journalctl -b -1 stopped to return errors.

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.