No I don’t.
How should I?
-- Logs begin at Wed 2014-10-15 13:23:35 BST, end at Sat 2014-10-25 20:47:52 BST. --
But this already says that the logs are not only for Oct. 15th, but upto Oct. 25th, i.e. today.
Oct 15 13:23:35 linux systemd-journal: Runtime journal is using 8.0M (max allowed 191.6M, trying to leave 287.5M free of 1.6G available → curren
Oct 15 13:26:35 linux.site dbus: [system] Activating via systemd: service name=‘org.freedesktop.UDisks2’ unit=‘udisks2.service’
Hm. And there’s nothing afterwards?
You have 2500 lines for only 3 minutes of logs? I have 19704 lines here for 26 hours, which would be about 38 lines for 3 minutes.
And that you only have 3 minutes of logs is definitely not normal I’d say.
Maybe there’s a problem with the hardware clock?
But then the “–list-boots” should be different as well probably.
What does “journalctl | wc -l” say exactly, btw?
Just out of curiosity.
Sending $>journalctl --list-boots gives (in reverse order):
-153 9534349ccd854b02b753abfaeb72d885 Wed 2014-10-15 13:23:35 BST—Wed 2014-10-15 13:24:04 BST
0 d5d63d94076a4033a9ff4f547a64dd3f Fri 2014-10-24 21:56:52 BST—Sat 2014-10-25 20:47:52 BST
As already hinted at in my previous post, this looks like the documentation states, I’d say.
But I would find it strange that every entry is doubled.
So my query is should journalctl without any options or flags only report a log from first boot?
Rather from the last, i.e. current boot.
But I think now that it should show all logs, you have to specify the '-b" option to see only the current boot.
I just noticed that I don’t even have the directory /var/log/journal/ here on this system, so the persistent on-disk journal is deactivated here (I have rsyslog running anyway). That’s the reason why I only see entries from the current boot.
Have you tried to use the “–since” option? Does that have any effect?
But I somehow have the feeling your logs are corrupted in some way.
If you don’t need them, delete them (they are located in /var/log/journal as mentioned, but do not delete the folder itself or you will disable the journal) and look whether the behaviour changes to something more sane.
Other than that I cannot say much about 13.2’s behaviour at the moment, cause I’m only having a 13.1 system here as mentioned, and no on-disk journal.
So I can’t neither confirm nor dismiss a general problem e.g.