i am new to journactl, so this might be perfectly normal… I am reading this page to try to get some clues:
http://www.freedesktop.org/software/systemd/man/journalctl.html
If I send
$>journactl or $>jouranlctl -x, I get 2500 or so lines, ALL dated October 15th 2014.
If I send, for example, $>journalctl --list-boots, I get a list including, naturally, dates up until and including today.
Is this normal?
No.
I get this:
linux-lf90:~ # journalctl --list-bootsjournalctl: unrecognized option '--list-boots'
Joke aside, what command are you really running?
The option “–list-boots” doesn’t exist, so I cannot really answer your question.
PS: Forget my reply. “–list-boots” seems to be a new option in 13.2. I only have 13.1 here.
Sorry.
But what you describe doesn’t sound that wrong, according to the documentation:
Show a tabular list of boot numbers (relative to the current boot), their IDs, and the timestamps of the first and last message pertaining to the boot.
But “journalctl” should only show the log from the current boot I think. At least it does here.
So what exactly are you getting (copy/paste it here, but not all 2500 lines of course), and why are you wondering whether that’s normal?
Is your system running since Oct. 15th? Or is the output showing Oct. 25th rather?
As you know Wolfie, I have rebooted many, many times since October 15th!
Here are some snippets:
Sending $>journalctl (first few lines)
journalctl
-- Logs begin at Wed 2014-10-15 13:23:35 BST, end at Sat 2014-10-25 20:47:52 BST. --
Oct 15 13:23:35 linux systemd-journal[1659]: Runtime journal is using 8.0M (max allowed 191.6M, trying to leave 287.5M free of 1.6G available → curren
Oct 15 13:23:35 linux systemd-journal[1659]: Runtime journal is using 8.0M (max allowed 191.6M, trying to leave 287.5M free of 1.6G available → curren
Oct 15 13:23:35 linux kernel: Initializing cgroup subsys cpuset
Oct 15 13:23:35 linux kernel: Initializing cgroup subsys cpu
Oct 15 13:23:35 linux kernel: Initializing cgroup subsys cpuacct
Oct 15 13:23:35 linux kernel: Linux version 3.16.3-1.gd2bbe7f-desktop (geeko@buildhost) (gcc version 4.8.3 20140627 [gcc-4_8-branch revision 212064] (
Oct 15 13:23:35 linux kernel: Command line: initrd=initrd ramdisk_size=512000 ramdisk_blocksize=4096
Oct 15 13:23:35 linux kernel: e820: BIOS-provided physical RAM map:
Oct 15 13:23:35 linux kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000009fbff] usable
Oct 15 13:23:35 linux kernel: BIOS-e820: [mem 0x000000000009fc00-0x000000000009ffff] reserved
Oct 15 13:23:35 linux kernel: BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved
Oct 15 13:23:35 linux kernel: BIOS-e820: [mem 0x0000000000100000-0x00000000b7fbffff] usable
Oct 15 13:23:35 linux kernel: BIOS-e820: [mem 0x00000000b7fc0000-0x00000000b7fcdfff] ACPI data
Oct 15 13:23:35 linux kernel: BIOS-e820: [mem 0x00000000b7fce000-0x00000000b7feffff] ACPI NVS
Oct 15 13:23:35 linux kernel: BIOS-e820: [mem 0x00000000b7ff0000-0x00000000b7ffffff] reserved
Oct 15 13:23:35 linux kernel: BIOS-e820: [mem 0x00000000fec00000-0x00000000fec00fff] reserved
Oct 15 13:23:35 linux kernel: BIOS-e820: [mem 0x00000000fee00000-0x00000000feefffff] reserved
Oct 15 13:23:35 linux kernel: BIOS-e820: [mem 0x00000000ff780000-0x00000000ffffffff] reserved
Oct 15 13:23:35 linux kernel: BIOS-e820: [mem 0x0000000100000000-0x000000013fffffff] usable
And the last few…
Oct 15 13:26:18 linux.site systemd[2173]: Reached target Sockets.
Oct 15 13:26:18 linux.site systemd[2173]: Starting Basic System.
Oct 15 13:26:18 linux.site systemd[2173]: Reached target Basic System.
Oct 15 13:26:18 linux.site systemd[2173]: Starting Default.
Oct 15 13:26:18 linux.site systemd[2173]: Reached target Default.
Oct 15 13:26:18 linux.site systemd[2173]: Startup finished in 80ms.
Oct 15 13:26:18 linux.site systemd[1]: Started User Manager for UID 999.
Oct 15 13:26:34 linux.site dbus[1752]: [system] Activating via systemd: service name='org.freedesktop.UPower' unit='upower.service'
Oct 15 13:26:35 linux.site dbus[1752]: [system] Successfully activated service 'org.freedesktop.UPower'
Oct 15 13:26:35 linux.site dbus[1752]: [system] Activating service name='org.kde.powerdevil.backlighthelper' (using servicehelper)
Oct 15 13:26:35 linux.site org.kde.powerdevil.backlighthelper[1752]: no kernel backlight interface found
Oct 15 13:26:35 linux.site dbus[1752]: [system] Successfully activated service 'org.kde.powerdevil.backlighthelper'
Oct 15 13:26:35 linux.site dbus[1752]: [system] Activating via systemd: service name='org.freedesktop.UDisks2' unit='udisks2.service'
BUT:
Sending $>journalctl --list-boots gives (in reverse order):
journalctl --list-boots
-153 9534349ccd854b02b753abfaeb72d885 Wed 2014-10-15 13:23:35 BST—Wed 2014-10-15 13:24:04 BST
-152 9534349ccd854b02b753abfaeb72d885 Wed 2014-10-15 13:23:35 BST—Wed 2014-10-15 13:24:04 BST
-151 c36a45aa37fd4c6a87995f16eb0ea195 Wed 2014-10-15 13:26:01 BST—Wed 2014-10-15 13:26:18 BST
-150 4f38aad89d594316885d55fff56c0510 Wed 2014-10-15 13:29:24 BST—Wed 2014-10-15 13:49:56 BST
-149 4f38aad89d594316885d55fff56c0510 Wed 2014-10-15 13:29:24 BST—Wed 2014-10-15 13:49:56 BST
-148 6f1240a2c9d146b0af551b42ba28926a Wed 2014-10-15 13:51:02 BST—Wed 2014-10-15 14:03:53 BST
-147 6f1240a2c9d146b0af551b42ba28926a Wed 2014-10-15 13:51:02 BST—Wed 2014-10-15 14:03:53 BST
-146 31399dd8d37e4e7b8b972e4acf081482 Wed 2014-10-15 14:04:33 BST—Wed 2014-10-15 15:16:02 BST
-145 31399dd8d37e4e7b8b972e4acf081482 Wed 2014-10-15 14:04:33 BST—Wed 2014-10-15 15:16:02 BST
And…
-12 142322d0b2ff489faa04e5e29b7a4259 Thu 2014-10-23 13:29:58 BST—Thu 2014-10-23 15:12:40 BST
-11 cc0312302f16481594f7d59985493f3b Thu 2014-10-23 15:12:59 BST—Thu 2014-10-23 15:49:57 BST
-10 cc0312302f16481594f7d59985493f3b Thu 2014-10-23 15:12:59 BST—Thu 2014-10-23 15:49:57 BST
-9 471b5f500886474f8c7b613bdc1cbb3f Thu 2014-10-23 15:54:09 BST—Fri 2014-10-24 08:10:54 BST
-8 471b5f500886474f8c7b613bdc1cbb3f Thu 2014-10-23 15:54:09 BST—Fri 2014-10-24 08:10:54 BST
-7 88dace00171740f3ad73e2bfe100e905 Fri 2014-10-24 08:11:38 BST—Fri 2014-10-24 08:24:27 BST
-6 88dace00171740f3ad73e2bfe100e905 Fri 2014-10-24 08:11:38 BST—Fri 2014-10-24 08:24:27 BST
-5 fbac471a62e948f4ba7f0dffa9fc8420 Fri 2014-10-24 08:25:12 BST—Fri 2014-10-24 18:30:01 BST
-4 fbac471a62e948f4ba7f0dffa9fc8420 Fri 2014-10-24 08:25:12 BST—Fri 2014-10-24 18:30:01 BST
-3 280cda47977f4ad0b17a4a02cc9b27ca Fri 2014-10-24 18:38:30 BST—Fri 2014-10-24 18:40:22 BST
-2 280cda47977f4ad0b17a4a02cc9b27ca Fri 2014-10-24 18:38:30 BST—Fri 2014-10-24 18:40:22 BST
-1 d5d63d94076a4033a9ff4f547a64dd3f Fri 2014-10-24 21:56:52 BST—Sat 2014-10-25 20:47:52 BST
0 d5d63d94076a4033a9ff4f547a64dd3f Fri 2014-10-24 21:56:52 BST—Sat 2014-10-25 20:47:52 BST
So my query is should journalctl without any options or flags only report a log from first boot?
Why did you not start this thread in the Pre-release/Beta forum.?
Now you see that Wolfi spend time helping you on the wrong version.
Not realy nice 
The first line of the post was “I am new to journactl…” And shortly after I said "I am reading this page to try to get some clues:
http://www.freedesktop.org/software/…ournalctl.html"
I had no way of knowing that one command option was not available in previous releases, either of openSUSE or of systemd or whatever. There is no reason to accuse me of being “not nice” If you must, move the thread to wherever you feel appropriate.
No I don’t.
How should I?
journalctl -- 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[1659]: 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[1752]: [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.
BUT:
Sending $>journalctl --list-boots gives (in reverse order):
journalctl --list-boots -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?
No.
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.
PS:
A lot of reboots there in a short time I’d say.
Did you have problems?
An inconsistent not-correctly shutdown filesystem (caused by crashes) might explain a corrupted journal.
But that’s just grasping for straws now. 
I am sure you did not mean to be not nice. But you are a frequent poster here and you must know by now which (sub)forums we have. Using the most appropriate forum helps to avoid things like this: assuming that there is no difference between versions where in fact there is.
As it takes time to mov a thread, which I do not have at the moment, I will postpone that till tomorow. In the maen time I see you get help nevertheless. O yes, people here are very nice (apart from me of cousrse).
Will be moved to Pre-release/Beta and is CLOSED for the moment.
Moved from Applications and open again.
Well… I agree whit wakou, how should he know that it was a “new” feature in 13.2? If wolfi323 run the full web-version of the forum he should have seen what wakou has in his signature. If wolfi323 run something else to work in the forum… Well.
The interesting tread “Considering switching to Opensuse” in Install/boot/login is full of problems that a moderator should have stept in. Ex not once I have seen that someone have rise the issue of use wrap (code) tags to the OP. Otherwise it is often mentioned to new users when post in the forum. Myself was question some advice given there even If I run 13.2RC1…
Yes I know, I had a bad day 1974. I still remember it.
Written whit a blink in my eye ;).
regards
Yes, I did use a web browser, and yes I have seen the signature, but only after writing the (first part of the) reply already.
Otherwise I wouldn’t even have had the idea this might be a new option in 13.2…
The interesting tread “Considering switching to Opensuse” in Install/boot/login is full of problems that a moderator should have stept in. Ex not once I have seen that someone have rise the issue of use wrap (code) tags to the OP.
Why do you mention this here?
Click on the triangle below a thread to report it to the moderators.
Personally, I have given up to tell people to use CODE tags…
Sorry for the delay of my answer, I was away for a few days.
My idea is that you start from the wrong question. The question asked when deciding which forum to use for a post is not “could I know that this problem is version specific”, the question is “do I know for sure that it is NOT version specific”.
Thus, when you have a problem in version X and you know these are forums where is was decided to offer different forums for different types of versions (in this case, pre-release vs. released) and where even inside category it is very advisable to mention the version you use, be nice and follow that style.
When you know FOR SURE that your problem is version independent, then you can choose the forum you think is best to get the best advice, but then of course you tell that you did test things on version A, B, C, … and do not keep that important information a secret for your potential helpers.
BTW, I have the strong impression that wakou knows this very well and it was just a slight mishap. He was only not very content with me calling his action “not nice”. But IMHO wakou is a nice person in general, it was just a mishap. And as I said earlier, sometimes I am the bad guy on the block.
I am reading this thread more or less only to see if no T&C violations arrive. In my very personal opinion, this thread has run completely out of hand. Lots of subjects never be covered by the title. No use in the future for technical fact finding. More something for General Chitchat. But you are free to report posts (or threads) when you think that the mods misssed something.
And about the CODE tags, also PMs are send to new users. You do not see them of course. But a message about CODE tags every now and then in the open might also trigger other people that are trying to find there way in these forums.
Hmm… Henk. One of my less asked properties/comments is that I can be questioned. I feel that most of the time I’m right on my opinions.
Is to late to ask to read my posts whit a ;). On the other hand I deserve some kick at my back as well on my posts.
I read your post and I dont agree 100% whit you.
Oh, -lucky me that I’m so perfect my self!
And yes the openSUSE forum is ~gold worth.
regards