On Wed, Oct 14, 2015 at 10:34 AM, Lennart Poettering <[email protected]> wrote: > On Wed, 14.10.15 18:18, Lars Noschinski ([email protected]) wrote: > >> On 14.10.2015 17:33, Lennart Poettering wrote: >> > On Thu, 08.10.15 13:04, Lars Noschinski ([email protected]) wrote: >> >> [please CC me on answers] >> >> $ sudo journalctl --list-boots >> >> Failed to determine boots: No data available >> [...] >> > Any chance you can provide us with the precise set of journal files >> > you have when this happens, so that I can reproduce this here? If you >> > don't want to put this onine, feel free to send this to me >> > personally. >> >> Which files do you need, everything under /var/log/journal? Does it make >> sense if I try to minimize this set of files? > > Well, sure, I don't really care about the complete set, but only only > *a* set where you get the error you mention above. The smaller more > minimal it is, the better, of course. As long as it results in the > error above...
Resurrecting this thread. I've filed a bug with attached minimal journal files that reproduce it. It's actually a complete set of journals, nothing thinned out. It was relatively new, but then I had a crash and now journalctl -b-1 says it failed to look up boot and that there's no such boot ID in journal. And yet --list-boots lists what I'm after including an ID. https://bugzilla.redhat.com/show_bug.cgi?id=1294002 --- Chris Murphy _______________________________________________ systemd-devel mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/systemd-devel
