Description of problem:
sosreport collects journalctl --list-boots,
but the result in sos_commands/systemd/journalctl_--list-boots
always "journalctl: unrecognized option '--list-boots'"
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Run sosreport
2. Extraxt xz file
3. See sos_commands/systemd/journalctl_--list-boots
journalctl: unrecognized option '--list-boots'
Boot time and date should be display.
It seemed journalctl in systemd-208-20.el7_1.6 doesn't have this option.
Either remove this command from sos, or backport this option into
systemd-208-20.el7 is a solution.
Business impact : none
This is not a bug in sos: we support multiple distributions from the same sos version meaning that there is some variation in the environment and tool capabilities where sos runs.
The same command on a recent Fedora system would produce something like:
$ cat sos_commands/systemd/journalctl_--list-boots
-3 cd6f638cafa4451bbff8f71f8e018388 Tue 2015-10-06 21:16:56 BST—Tue 2015-10-06 22:09:40 BST
-2 37aa3ac637d2499c9911566a14deb976 Tue 2015-10-06 22:09:50 BST—Wed 2015-10-07 10:15:56 BST
-1 c15e6ac9f12944069e6ace081d31201d Wed 2015-10-07 10:45:48 BST—Fri 2015-10-09 18:07:36 BST
0 9180c1bf81f3466f93b9e656750098c6 Fri 2015-10-09 18:08:19 BST—Thu 2015-10-15 11:03:59 BST
> It seemed journalctl in systemd-208-20.el7_1.6 doesn't have this option.
> Either remove this command from sos, or backport this option into
> systemd-208-20.el7 is a solution.
I believe persistent journald logs are disabled by policy in RHEL7 and that this is a requirement for any operation working with boot IDs, e.g.:
# journalctl -k -b -1
Failed to look up boot -1: Cannot assign requested address
Note that other products such as Atomic do use the journal (and this version of sos): if there is to be a change here it needs to be in the systemd packaging.