Bug#804858: --list-boots: Failed to determine boots: No data available

[Michael Biebl]

Hi

Am 12.11.2015 um 14:34 schrieb Yaroslav Halchenko:
> for some reason stopped reporting previous boots (the only change might be that
> I booted 4.3.0-rc7 instead of default 4.3.0 kernel -- both are custom built,
> but previous boot was also into 4.3.0-rc7 according to kern.log), whenever
> worked before and it does see previous boots (although -1 reported seems to be
> not the last previous one, whenever most previous one might have been 4.3.0).
> Previous session was abrubtly ended with complete kernel stall (see
> #803087)
> 
> $> sudo journalctl --list-boots 
> [sudo] password for yoh: 
> Failed to determine boots: No data available
> 
> $> journalctl -b 0 | head      
> -- Logs begin at Sun 2015-11-01 20:00:40 EST, end at Thu 2015-11-12 08:26:59 EST. --
> Nov 12 08:24:25 hopa systemd-journald[325]: Runtime journal (/run/log/journal/) is currently using 8.0M.
>                                             Maximum allowed usage is set to 318.9M.
>                                             Leaving at least 478.4M free (of currently available 3.1G of space).
>                                             Enforced usage limit is thus 318.9M, of which 310.9M are still available.

Just to be sure:
Do you have persistent journal enabled?

-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: OpenPGP digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20151112/4094726c/attachment-0002.sig>