[SOLVED] List all previous boots (systemd)?

dockland · 2016-06-20 18:58:44

Is there a way to list all previous boots since installation my installation of Arch?

Iv'e tried journalctl --since="2016-06-10 00:00:00" but it only shows todays boot, even when scrolling down. I have not manipulated any boot-logs (eg. vaacum or likewise)

Last edited by dockland (2016-06-20 21:05:35)

null · 2016-06-20 19:03:55

~~It's the default behaviour of journalctl to only keep the current boot log.~~[If you miss the /var/log/journal/ folder systemd will write to /run/systemd/journal which isn't persistant over multiple boots.] You can get the list of all logged boots with `journalctl --list-boots`.
The wiki explains quite well how to change it: https://wiki.archlinux.org/index.php/Systemd#Journal

Last edited by null (2016-06-20 19:09:44)

dockland · 2016-06-20 19:28:41

null wrote:

~~It's the default behaviour of journalctl to only keep the current boot log.~~[If you miss the /var/log/journal/ folder systemd will write to /run/systemd/journal which isn't persistant over multiple boots.] You can get the list of all logged boots with `journalctl --list-boots`.
The wiki explains quite well how to change it: https://wiki.archlinux.org/index.php/Systemd#Journal

Yes, iv'e tried that as well. As root it lists:

0 e35faf72b4044ee39eab926a6b5c2248 Mon 2016-06-20 20:14:02 CEST—Mon 2016-06-20 21:26:54 CEST

And nothing more.

So there is no way to track reboots or startups? Date, time and so on for me?

loqs · 2016-06-20 19:52:44

journalctl --verify

To check for journal corruption
To check null's suggestion does /var/log/journal exist (it should have been created automatically)

pacman -Qo /var/log/journal/
/var/log/journal/ is owned by systemd 230-4

oliver · 2016-06-20 19:53:13

quick and dirty method

$ last|grep boot

graysky · 2016-06-20 20:02:34

dockland wrote:

Yes, iv'e tried that as well. As root it lists:
0 e35faf72b4044ee39eab926a6b5c2248 Mon 2016-06-20 20:14:02 CEST—Mon 2016-06-20 21:26:54 CEST
And nothing more.
So there is no way to track reboots or startups? Date, time and so on for me?

@OP - To be clear, that is the output of `journalctl --list-boots`? If so, something is wrong as others have suggested.

dockland · 2016-06-20 20:15:28

oliver wrote:

quick and dirty method
$ last|grep boot

Well, that seems legit. Thanks. Easy way, but what has that to do with systemd? Is there some other "init" running below systemd?

reboot system boot 4.6.2-1-ARCH Mon Jun 20 20:14 still running
reboot system boot 4.6.2-1-ARCH Sun Jun 19 20:47 - 20:57 (00:10)
reboot system boot 4.6.2-1-ARCH Sun Jun 19 08:58 - 20:47 (11:48)
reboot system boot 4.6.2-1-ARCH Sat Jun 18 14:53 - 02:04 (11:11)
reboot system boot 4.6.2-1-ARCH Sat Jun 18 10:47 - 14:53 (04:05)
reboot system boot 4.6.2-1-ARCH Fri Jun 17 17:04 - 00:53 (07:49)
reboot system boot 4.6.2-1-ARCH Fri Jun 17 14:21 - 17:04 (02:42)
reboot system boot 4.6.2-1-ARCH Wed Jun 15 16:38 - 22:29 (05:50)
reboot system boot 4.6.2-1-ARCH Tue Jun 14 18:24 - 22:51 (04:27)
reboot system boot 4.6.2-1-ARCH Tue Jun 14 08:01 - 18:14 (10:13)
reboot system boot 4.6.2-1-ARCH Tue Jun 14 08:00 - 08:01 (00:01)
reboot system boot 4.6.2-1-ARCH Mon Jun 13 17:18 - 06:55 (13:37)
reboot system boot 4.6.2-1-ARCH Mon Jun 13 07:59 - 17:12 (09:12)
reboot system boot 4.6.2-1-ARCH Sun Jun 12 17:12 - 23:52 (06:39)
reboot system boot 4.6.2-1-ARCH Sun Jun 12 16:11 - 17:12 (01:00)
reboot system boot 4.6.2-1-ARCH Sun Jun 12 10:46 - 16:11 (05:24)
reboot system boot 4.6.2-1-ARCH Sun Jun 12 10:07 - 16:11 (06:03)
reboot system boot 4.6.2-1-ARCH Sat Jun 11 13:23 - 10:07 (20:43)
reboot system boot 4.6.2-1-ARCH Sat Jun 11 13:12 - 13:23 (00:10)
reboot system boot 4.6.2-1-ARCH Sat Jun 11 09:58 - 13:12 (03:13)
...and so on

oliver · 2016-06-20 20:35:34

dockland wrote:

Well, that seems legit. Thanks. Easy way, but what has that to do with systemd? Is there some other "init" running below systemd?

No other init system... I always just assumed it was for backwards compatibility or compatibility with existing tools. I may have misunderstood if you specifically wanted the info from systemd, just thought it was by any means necessary and you were confirming the use of systemd.

dockland · 2016-06-20 21:05:18

oliver wrote:

dockland wrote:
Well, that seems legit. Thanks. Easy way, but what has that to do with systemd? Is there some other "init" running below systemd?
No other init system... I always just assumed it was for backwards compatibility or compatibility with existing tools. I may have misunderstood if you specifically wanted the info from systemd, just thought it was by any means necessary and you were confirming the use of systemd.

No, you haven't missunderstood anything. I just reflected that last | grep boot solved my question, whilst systemd-logs didn't. Just a statement. Marking as solved.

Arch Linux

#1 2016-06-20 18:58:44

[SOLVED] List all previous boots (systemd)?

#2 2016-06-20 19:03:55

Re: [SOLVED] List all previous boots (systemd)?

#3 2016-06-20 19:28:41

Re: [SOLVED] List all previous boots (systemd)?

#4 2016-06-20 19:52:44

Re: [SOLVED] List all previous boots (systemd)?

#5 2016-06-20 19:53:13

Re: [SOLVED] List all previous boots (systemd)?

#6 2016-06-20 20:02:34

Re: [SOLVED] List all previous boots (systemd)?

#7 2016-06-20 20:15:28

Re: [SOLVED] List all previous boots (systemd)?

#8 2016-06-20 20:35:34

Re: [SOLVED] List all previous boots (systemd)?

#9 2016-06-20 21:05:18

Re: [SOLVED] List all previous boots (systemd)?

Board footer