I did: root@gepard:/root(11)# journalctl > ~rose/journalctl_complete.log root@gepard:/root(13)# qlist -Iv systemd sys-apps/gentoo-systemd-integration-4 sys-apps/systemd-218-r1 sys-apps/systemd-ui-3 root@gepard:/root(14)# tail ~rose/journalctl_complete.log Nov 03 10:44:27 gepard gnome-session[4450]: (tracker-miner-fs:4750): GLib-GIO-CRITICAL **: Error while sending AddMatch() message: Verbindung ist geschlossen Nov 03 10:44:27 gepard gnome-session[4450]: (tracker-miner-fs:4750): GLib-GIO-CRITICAL **: Error while sending AddMatch() message: Verbindung ist geschlossen Nov 03 10:44:27 gepard gnome-session[4450]: (tracker-miner-fs:4750): GLib-GIO-CRITICAL **: Error while sending AddMatch() message: Verbindung ist geschlossen Nov 03 10:44:27 gepard org.freedesktop.Tracker1[4587]: g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting. Nov 03 10:44:28 gepard gnome-session[4450]: OK Nov 03 10:44:28 gepard org.freedesktop.Tracker1[4587]: Received signal:15->'Beendet' Nov 03 10:44:28 gepard org.freedesktop.Tracker1[4587]: OK Nov 03 10:45:01 gepard cron[19025]: (root) CMD (/root/scripts/system_state.sh >> /var/log/system_state.log) Nov 03 10:46:02 gepard systemd-logind[2060]: Power key pressed. Nov 03 10:46:02 gepard systemd-logind[2060]: Powering Off... root@gepard:/root(15)# date Wed Jan 7 16:58:18 CET 2015 I expected, that the end of 'journalctl' shows information from today, i.e. Jan 7, but shown is Nov 03 10. 'journal -b' shows as expected the information from the last boot: root@gepard:/root(17)# journalctl -b | head -- Logs begin at Mon 2014-09-15 13:43:06 CEST, end at Wed 2015-01-07 17:00:01 CET. -- Jan 07 15:03:54 gepard systemd-journal[1658]: Runtime journal is using 8.0M (max allowed 391.7M, trying to leave 587.6M free of 3.8G available → current limit 391.7M). Jan 07 15:03:54 gepard systemd-journal[1658]: Runtime journal is using 8.0M (max allowed 391.7M, trying to leave 587.6M free of 3.8G available → current limit 391.7M). Jan 07 15:03:54 gepard kernel: Initializing cgroup subsys cpuset Jan 07 15:03:54 gepard kernel: Initializing cgroup subsys cpu Jan 07 15:03:54 gepard kernel: Initializing cgroup subsys cpuacct Jan 07 15:03:54 gepard kernel: Linux version 3.18.1-gentoo (root@gepard) (gcc version 4.8.3 (Gentoo 4.8.3 p1.1, pie-0.5.9) ) #1 SMP PREEMPT Wed Dec 17 19:47:31 CET 2014 Jan 07 15:03:54 gepard kernel: Command line: BOOT_IMAGE=/kernel-genkernel-x86_64-3.18.1-gentoo root=UUID=745535db-908e-446b-a6bb-a898813da29c ro dolvm real_init=/usr/lib/systemd/systemd rootfstype=ext4 Jan 07 15:03:54 gepard kernel: KERNEL supported cpus: Jan 07 15:03:54 gepard kernel: Intel GenuineIntel Any idea, what is happend here?
journalctl seems to be limiting how many total lines it will output, if you add a param like --since 2014-11-01 (so it gives everything from nov 1 to now) then I bet the last shown entry will either be current or at least a lot later
A couple of possibilities come to mind: 1. You ran out of disk space to hold the file. 2. journalctl crashed for some other reason. Maybe a corrupt journal file triggered a bug? Did you see any errors output on the terminal? Also, Ben's idea might be valid.
I tested on mine and saw the same behavior, FWIW... I didn't see any crash but "journalctl > journal.log" stopped writing after "only" ~470k lines. My log (output from plain "journalctl") cut off around Dec 6, but I could get journalctl to spit out later stuff if I either cleaned up old journal data, or gave it a later start date. Seems like there's something limiting just how much total data journalctl will spit out, I'm not sure if that's a bug or just a default option somewhere.
