journalctl --list-boots not showing boots

[kenjo]

 journalctl --list-boots
 0 dffe658761e04aeea07ed5114771b9fe ons 2015-03-18 15:50:29 CET—fre 2015-03-20 15:33:00 CET

I have done more boots than this. in fact I just rebooted 4 minutes ago.

~$ uptime
 20:41:42 up 4 min, 2 users, load average: 0,36, 0,94, 0,54
~$ date
ons 25 mar 2015 20:41:53 CET

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: systemd 219-4ubuntu10
Uname: Linux 3.19.2-031902-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.16.2-0ubuntu4
Architecture: amd64
CurrentDesktop: Unity
Date: Wed Mar 25 20:40:19 2015
InstallationDate: Installed on 2013-04-19 (705 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64+mac (20130419)
MachineType: Apple Inc. MacBookPro10,1
ProcKernelCmdLine: \vmlinuz-3.19.2-031902-generic root=/dev/sda6 rootflags=subvol=@ ro quiet splash vt.handoff=7 initrd=\initrd.img-3.19.2-031902-generic
SourcePackage: systemd
UpgradeStatus: Upgraded to vivid on 2015-03-14 (10 days ago)
dmi.bios.date: 01/07/2015
dmi.bios.vendor: Apple Inc.
dmi.bios.version: MBP101.88Z.00EE.B07.1501071031
dmi.board.asset.tag: Base Board Asset Tag#
dmi.board.name: Mac-C3EC7CD22292981F
dmi.board.vendor: Apple Inc.
dmi.board.version: MacBookPro10,1
dmi.chassis.type: 10
dmi.chassis.vendor: Apple Inc.
dmi.chassis.version: Mac-C3EC7CD22292981F
dmi.modalias: dmi:bvnAppleInc.:bvrMBP101.88Z.00EE.B07.1501071031:bd01/07/2015:svnAppleInc.:pnMacBookPro10,1:pvr1.0:rvnAppleInc.:rnMac-C3EC7CD22292981F:rvrMacBookPro10,1:cvnAppleInc.:ct10:cvrMac-C3EC7CD22292981F:
dmi.product.name: MacBookPro10,1
dmi.product.version: 1.0
dmi.sys.vendor: Apple Inc.

[Martin Pitt (pitti)]

This only works if you enable the persistant journal, see /usr/share/doc/systemd/README.Debian . Otherwise the journal is kept in memory and only applies to the current boot.

[kenjo (ken-kenjo)]

read again. the boot shown is NOT the current boot but one from 5 days ago.

I already made the changes to make the journal permanent.

 ls -l /var/log/journal/c74017b0325255418c0f7c3c51719c92/
total 188416
-rw-r-x---+ 1 root root 25165824 mar 20 15:34 [e-mail]~
-rw-r-x---+ 1 root root 8388608 mar 20 15:55 [e-mail]~
-rw-r-x---+ 1 root systemd-journal 8388608 mar 20 16:05 [e-mail]~
-rw-r-x---+ 1 root systemd-journal 33554432 mar 25 19:58 [e-mail]~
-rw-r-x---+ 1 root systemd-journal 16777216 mar 25 20:58 [e-mail]~
-rw-r-x---+ 1 root systemd-journal 16777216 mar 26 11:04 [e-mail]~
-rw-r-x---+ 1 root systemd-journal 8388608 mar 26 20:34 system.journal
-rw-r-x---+ 1 root root 8388608 mar 20 15:56 [e-mail]~
-rw-r-x---+ 1 root systemd-journal 8388608 mar 20 16:05 [e-mail]~
-rw-r-x---+ 1 root systemd-journal 16777216 mar 25 21:04 [e-mail]~
-rw-r-x---+ 1 root systemd-journal 8388608 mar 26 11:05 [e-mail]~
-rw-r-x---+ 1 root systemd-journal 8388608 mar 26 20:34 user-1000.journal
-rw-r-x---+ 1 root root 8388608 mar 20 15:35 [e-mail]~
-rw-r-x---+ 1 root systemd-journal 8388608 mar 26 11:05 [e-mail]~
-rw-r-x---+ 1 root systemd-journal 8388608 mar 26 20:34 user-65534.journal

hmm not sure why the group is root on some. maybe that is the issue

[Martin Pitt (pitti)]

Ah, sorry about that. Indeed I get this on my system as well.

I asked upstream about this on http://lists.freedesktop.org/archives/systemd-devel/2015-March/029890.html