Hello all,

in [1] I just got a report that "journalctl --list-boots" (with
persistant journal) only shows a few old boots, but not current ones.
I checked this on my system (which has had persistant journal for a
while), and confirm that:

$ journalctl --list-boots
-2 81de6f2120224dfdb6ac7cc0bf67ee3c Fr 2015-02-20 10:40:16 CET—Fr 2015-02-20 
10:40:29 CET
-1 f1d0c5a906b241bda8637abc2eb7ac94 Fr 2015-02-20 10:40:39 CET—Fr 2015-02-20 
10:40:42 CET
 0 a91d941cddff405e8e3f8a2dc89ff14a Fr 2015-02-20 10:44:10 CET—Fr 2015-02-20 
10:44:22 CET

Curiously it's even different with --system:

$ ./journalctl --system --list-boots
-1 81de6f2120224dfdb6ac7cc0bf67ee3c Fr 2015-02-20 10:40:16 CET—Fr 2015-02-20 
10:40:29 CET
 0 f1d0c5a906b241bda8637abc2eb7ac94 Fr 2015-02-20 10:40:39 CET—Fr 2015-02-20 
10:40:42 CET

When I dump all data, it correctly starts at the top (oldest available
data), but stops in the middle again (although much later than the
above):

$ journalctl --no-pager | head -n 1
-- Logs begin at Fr 2015-02-20 10:40:16 CET, end at Fr 2015-03-27 11:28:19 CET. 
--
$ journalctl --no-pager | tail -n 1
Mär 06 09:26:30 donald systemd[2269]: Stopped target Basic System.
$ journalctl --system --no-pager | tail -n 1
Mär 15 11:35:02 donald acpid[1573]: client 32107[0:0] has disconnected

But "journalctl -b" is fine, i. e. the journal indeed has the current
data. This can also be seen on the dates in /var/log/journal/*/system*:

-rw-r-x---+ 1 root root             8388608 Feb 20 10:41 
system@00050f81daeb3450-01f8b5c07f5c685d.journal~
-rw-r-x---+ 1 root systemd-journal 16777216 Feb 20 10:44 
system@00050f81e6aae621-4cc822da2f4e5632.journal~
-rw-r-x---+ 1 root systemd-journal 50331648 Feb 23 14:51 
system@00050fc1b33c71d9-e5b4f504845fa973.journal~
-rw-r-x---+ 1 root systemd-journal 58720256 Feb 27 05:39 
system@0005100a72962dbf-87d746f79acfd368.journal~
-rw-r-x---+ 1 root systemd-journal 75497472 Mär  6 09:27 
system@0005109a742ac2de-ce57867db39fa7fe.journal~
-rw-r-x---+ 1 root systemd-journal 16777216 Mär  7 13:35 
system@000510b20aa96358-85c7ad2e2345c443.journal~
-rw-r-x---+ 1 root systemd-journal 16777216 Mär 10 06:30 
system@000510e87298e593-c2804ca231570417.journal~
-rw-r-x---+ 1 root systemd-journal 16777216 Mär 11 06:17 
system@000510fc61c2d25d-1dd07ebfd3198dcb.journal~
-rw-r-x---+ 1 root systemd-journal 16777216 Mär 13 05:10 
system@00051123ad5c2e0d-0321e65975016e97.journal~
-rw-r-x---+ 1 root systemd-journal 25165824 Mär 13 20:57 
system@00051130e8932ec1-464554bc60f0378a.journal~
-rw-r-x---+ 1 root systemd-journal 16777216 Mär 15 11:49 
system@000511517e2e104a-70afd23a22d58ceb.journal~
-rw-r-x---+ 1 root systemd-journal 25165824 Mär 27 06:53 
system@0005123ec10bcd08-2f94975a3c6b8a98.journal~
-rw-r-x---+ 1 root systemd-journal  8388608 Mär 27 11:31 system.journal

(Note that the gap between Mar 15 and Mar 27 is expected -- I've been
away on holidays)

"journalctl --system --header" output is at
http://paste.ubuntu.com/10688374/ in case that helps.

This happens with both 219 and current master. Any idea about this?

Thanks,

Martin

[1] https://launchpad.net/bugs/1430675
-- 
Martin Pitt                        | http://www.piware.de
Ubuntu Developer (www.ubuntu.com)  | Debian Developer  (www.debian.org)

Attachment: signature.asc
Description: Digital signature

_______________________________________________
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel

Reply via email to