journalctl --list-boots not showing boots

Bug #1436534 reported by kenjo on 2015-03-25
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
systemd (Ubuntu)
Low
Unassigned

Bug Description

 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.

kenjo (ken-kenjo) wrote :
Martin Pitt (pitti) wrote :

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.

Changed in systemd (Ubuntu):
status: New → Invalid
kenjo (ken-kenjo) on 2015-03-26
Changed in systemd (Ubuntu):
status: Invalid → New
kenjo (ken-kenjo) wrote :

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 system@000511b936496f8c-5ee29ef39c31f534.journal~
-rw-r-x---+ 1 root root 8388608 mar 20 15:55 system@000511b9813242f4-bc364491a3897cb3.journal~
-rw-r-x---+ 1 root systemd-journal 8388608 mar 20 16:05 system@000511b9a4b7149a-d30184484d8626f1.journal~
-rw-r-x---+ 1 root systemd-journal 33554432 mar 25 19:58 system@000512217d8dcaa7-4053b448133f4ff0.journal~
-rw-r-x---+ 1 root systemd-journal 16777216 mar 25 20:58 system@00051222511b5303-cff486902905fabe.journal~
-rw-r-x---+ 1 root systemd-journal 16777216 mar 26 11:04 system@0005122e25a74237-4ea15c9fc9a7e20a.journal~
-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 user-1000@000511b9859e9d25-387ac4d152669d0a.journal~
-rw-r-x---+ 1 root systemd-journal 8388608 mar 20 16:05 user-1000@000511b9a5f7447f-f7cfe2b3aa80a236.journal~
-rw-r-x---+ 1 root systemd-journal 16777216 mar 25 21:04 user-1000@0005122267b20842-b2be546977a9ecca.journal~
-rw-r-x---+ 1 root systemd-journal 8388608 mar 26 11:05 user-1000@0005122e26bd2f83-a49f7816c8a9b064.journal~
-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 user-65534@000511b93978ff4e-0a4928f7c94b1863.journal~
-rw-r-x---+ 1 root systemd-journal 8388608 mar 26 11:05 user-65534@0005122e2681bd31-06cf5763fc30e599.journal~
-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) wrote :

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

Changed in systemd (Ubuntu):
importance: Undecided → Low
status: New → Triaged
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers