Hello,

While collecting journalctl logs at our embedded box, we get to see the below warning message. Can someone please clarify the impacts of the same. mainly why it says "no data available"

root@lfs:~# journalctl -b > /tmp/Capture_journal.log
Error was encountered while opening journal files: No data available

But, the logs are getting collected properly.

at the journalctl.c, below is the code snippet which throws the error.

SET_FOREACH(code, j->errors, it) {
int err;

err = -PTR_TO_INT(code);
assert(err > 0);

if (err != EACCES)
log_warning("Error was encountered while opening journal files: %s",
strerror(err));
}

What does 'journalctl --list-boots' return?

Please find the output:

root@linux:~# journalctl --list-boots
0 0a2d13a2dd99425cad5cbb4102fb6f14 Sat 2013-01-05 21:12:00 UTC—Sat 2013-01-05 22:00:12 UTC
root@linux:~#

From the system where this issue was noticed:

root@linux:~# journalctl --list-boots
journalctl: unrecognized option '--list-boots'

It says the option unrecognized.

OK but how did you verify this was the case then?:

I did redirect the journalctl output to a file and verified. Please clarify on all the scenarios when journalctl will through "No Data Available" warning.

With all due respect but I won't: that piece of research is yours to perform, not mine. Find out when the "--list-boots" was added to the software and check your systemd version to match. Update if necessary I'd say.