Bug 1052262

Summary:

Empty offset not equivalent to -0 for -b option as man page documents

Product:

[Fedora] Fedora

Reporter:

Ankur Sinha (FranciscoD) <sanjay.ankur>

Component:

systemd

Assignee:

systemd-maint

Status:

CLOSED ERRATA

QA Contact:

Fedora Extras Quality Assurance <extras-qa>

Severity:

low

Docs Contact:

Priority:

unspecified

Version:

CC:

johannbg, lnykryn, msekleta, plautrba, systemd-maint, vpavlin, zbyszek

Target Milestone:

---

Target Release:

---

Hardware:

x86_64

OS:

Linux

Whiteboard:

Fixed In Version:

systemd-208-26.fc20

Doc Type:

Bug Fix

Doc Text:

Story Points:

---

Clone Of:

Environment:

Last Closed:

2014-11-02 07:26:30 UTC

Type:

Bug

Regression:

---

Mount Type:

---

Documentation:

---

CRM:

Verified Versions:

Category:

---

oVirt Team:

---

RHEL 7.3 requirements from Atomic Host:

Cloudforms Team:

---

Target Upstream Version:

Embargoed:

Attachments:

Description	Flags
journalctl --list-boots	none
Output of `journalctl -F _BOOT_ID`	none
Output of `journalctl _BOOT_ID=$(cat /proc/sys/kernel/random/boot_id\| sed s/-//g)`	none

Description Ankur Sinha (FranciscoD) 2014-01-13 14:34:24 UTC

Description of problem:
The man page says that not specifying an offset is the same as specifying -0 for the -b flag: the should both provide logs for the last boot (in most cases, this running boot). However, I get different logs when not specifying an offset and when I use -0 as the offset.

"An empty offset is equivalent to specifying -0, except when the current boot is
not the last boot (e.g. because --directory was specified to look at logs from a different machine)."


Version-Release number of selected component (if applicable):
systemd-208-9.fc20.x86_64

How reproducible:
Always

Steps to Reproduce:
1.journalct -k -b --no-pager > temp1
2.journalct -k -b -0 --no-pager > temp2
3.head temp1; head temp2

Actual results:
Should be same if -0 is equivalent to no offset

Expected results:
Not same as shown below:

Additional info:
[asinha@ankur-laptop  test]$ journalctl -k -b --no-pager > temp1
[asinha@ankur-laptop  test]$ journalctl -k -b -0 --no-pager > temp2
[asinha@ankur-laptop  test]$ head temp1
-- Logs begin at Fri 2013-09-27 17:19:35 EST, end at Tue 2014-01-14 01:22:09 EST. --
Jan 14 01:07:08 ankur-laptop kernel: Initializing cgroup subsys cpuset
Jan 14 01:07:08 ankur-laptop kernel: Initializing cgroup subsys cpu
Jan 14 01:07:08 ankur-laptop kernel: Initializing cgroup subsys cpuacct
Jan 14 01:07:08 ankur-laptop kernel: Linux version 3.11.10-301.fc20.x86_64 (mockbuild.fedoraproject.org) (gcc version 4.8.2 20131017 (Red Hat 4.8.2-1) (GCC) ) #1 SMP Thu Dec 5 14:01:17 UTC 2013
Jan 14 01:07:08 ankur-laptop kernel: Command line: BOOT_IMAGE=/vmlinuz-3.11.10-301.fc20.x86_64 root=UUID=e6393d35-3392-4c49-b114-278fcc274e13 ro vconsole.font=latarcyrheb-sun16 vconsole.keymap=us rhgb quiet LANG=en_US.UTF-8
Jan 14 01:07:08 ankur-laptop kernel: e820: BIOS-provided physical RAM map:
Jan 14 01:07:08 ankur-laptop kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000009d3ff] usable
Jan 14 01:07:08 ankur-laptop kernel: BIOS-e820: [mem 0x000000000009d400-0x000000000009ffff] reserved
Jan 14 01:07:08 ankur-laptop kernel: BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved

[asinha@ankur-laptop  test]$ head temp2
-- Logs begin at Fri 2013-09-27 17:19:35 EST, end at Tue 2014-01-14 01:22:09 EST. --
Jan 14 00:47:31 ankur-laptop kernel: Initializing cgroup subsys cpuset
Jan 14 00:47:31 ankur-laptop kernel: Initializing cgroup subsys cpu
Jan 14 00:47:31 ankur-laptop kernel: Initializing cgroup subsys cpuacct
Jan 14 00:47:31 ankur-laptop kernel: Linux version 3.12.7-300.fc20.x86_64 (mockbuild.fedoraproject.org) (gcc version 4.8.2 20131212 (Red Hat 4.8.2-7) (GCC) ) #1 SMP Fri Jan 10 15:35:31 UTC 2014
Jan 14 00:47:31 ankur-laptop kernel: Command line: BOOT_IMAGE=/vmlinuz-3.12.7-300.fc20.x86_64 root=UUID=e6393d35-3392-4c49-b114-278fcc274e13 ro vconsole.font=latarcyrheb-sun16 vconsole.keymap=us rhgb quiet LANG=en_US.UTF-8 drm.debug=15
Jan 14 00:47:31 ankur-laptop kernel: e820: BIOS-provided physical RAM map:
Jan 14 00:47:31 ankur-laptop kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000009d3ff] usable
Jan 14 00:47:31 ankur-laptop kernel: BIOS-e820: [mem 0x000000000009d400-0x000000000009ffff] reserved
Jan 14 00:47:31 ankur-laptop kernel: BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved

[asinha@ankur-laptop  test]$ journalctl -k -b 0 --no-pager > temp3
[asinha@ankur-laptop  test]$ head temp3
-- Logs begin at Fri 2013-09-27 17:19:35 EST, end at Tue 2014-01-14 01:22:09 EST. --
Jan 14 00:47:31 ankur-laptop kernel: Initializing cgroup subsys cpuset
Jan 14 00:47:31 ankur-laptop kernel: Initializing cgroup subsys cpu
Jan 14 00:47:31 ankur-laptop kernel: Initializing cgroup subsys cpuacct
Jan 14 00:47:31 ankur-laptop kernel: Linux version 3.12.7-300.fc20.x86_64 (mockbuild.fedoraproject.org) (gcc version 4.8.2 20131212 (Red Hat 4.8.2-7) (GCC) ) #1 SMP Fri Jan 10 15:35:31 UTC 2014
Jan 14 00:47:31 ankur-laptop kernel: Command line: BOOT_IMAGE=/vmlinuz-3.12.7-300.fc20.x86_64 root=UUID=e6393d35-3392-4c49-b114-278fcc274e13 ro vconsole.font=latarcyrheb-sun16 vconsole.keymap=us rhgb quiet LANG=en_US.UTF-8 drm.debug=15
Jan 14 00:47:31 ankur-laptop kernel: e820: BIOS-provided physical RAM map:
Jan 14 00:47:31 ankur-laptop kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000009d3ff] usable
Jan 14 00:47:31 ankur-laptop kernel: BIOS-e820: [mem 0x000000000009d400-0x000000000009ffff] reserved
Jan 14 00:47:31 ankur-laptop kernel: BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved
[asinha@ankur-laptop  test]$ diff temp3 temp2
[asinha@ankur-laptop  test]$

Comment 1 Zbigniew Jędrzejewski-Szmek 2014-01-14 19:52:48 UTC

Can you provide the output from 

journalctl --list-boots

and

SYSTEMD_LOG_LEVEL=debug journalctl -b XXX |& grep -m1 'Journal filter'

where XXX is empty, or -0, 0, etc,

and the contents of /proc/sys/kernel/random/boot_id?

Comment 2 Ankur Sinha (FranciscoD) 2014-01-14 21:19:32 UTC

Created attachment 850214 [details]
journalctl --list-boots

Hi,

Other requested outputs:

[asinha@ankur-laptop  ~]$ SYSTEMD_LOG_LEVEL=debug journalctl -b |& grep -m1 'Journal filter'
Journal filter: _BOOT_ID=00b238359e6143b0aa5914b1c9825d01

[asinha@ankur-laptop  ~]$ SYSTEMD_LOG_LEVEL=debug journalctl -b 0 |& grep -m1 'Journal filter'
Journal filter: _BOOT_ID=fea739fa036b4c628ffa0e796ee5ab08

[asinha@ankur-laptop  ~]$ SYSTEMD_LOG_LEVEL=debug journalctl -b -0 |& grep -m1 'Journal filter'
Journal filter: _BOOT_ID=fea739fa036b4c628ffa0e796ee5ab08

[asinha@ankur-laptop  ~]$ cat /proc/sys/kernel/random/boot_id
00b23835-9e61-43b0-aa59-14b1c9825d01


Thanks,
Warm regards,
Ankur

Comment 3 Zbigniew Jędrzejewski-Szmek 2014-01-15 14:14:15 UTC

It seems that --list-boots does not return "current boot" as one of the possibilities. Then -b behaves as expected in light of this. Just great :)

Can you post the output of 'journalctl -F _BOOT_ID' ?

And also, does 'journalctl _BOOT_ID=$(cat /proc/sys/kernel/random/boot_id| sed s/-//g)' print anything?

Comment 4 Ankur Sinha (FranciscoD) 2014-01-16 03:44:52 UTC

Created attachment 850838 [details]
Output of `journalctl -F _BOOT_ID`

Comment 5 Ankur Sinha (FranciscoD) 2014-01-16 03:46:04 UTC

Created attachment 850839 [details]
Output of `journalctl _BOOT_ID=$(cat /proc/sys/kernel/random/boot_id| sed s/-//g)`

It does. I'm not sure if it's the current or previous boot though. I've just rebooted a couple of times to check another bug :/

Comment 6 Ankur Sinha (FranciscoD) 2014-01-16 04:36:51 UTC

Something is seriously wrong with journalctl at the moment. I booted into kernel 3.13 from the rawhide debug repo to test it out but it isn't anywhere in journalctl --list-boots.. I've checked the last 5 boots:

[asinha@ankur-laptop  ~]$ journalctl -b | egrep "kernel: Command line:"
Jan 16 15:18:15 ankur-laptop kernel: Command line: BOOT_IMAGE=/vmlinuz-3.11.10-301.fc20.x86_64 root=UUID=e6393d35-3392-4c49-b114-278fcc274e13 ro vconsole.font=latarcyrheb-sun16 vconsole.keymap=us rhgb quiet
[asinha@ankur-laptop  ~]$ journalctl -b 0 | egrep "kernel: Command line:"
Jan 14 01:07:08 ankur-laptop kernel: Command line: BOOT_IMAGE=/vmlinuz-3.11.10-301.fc20.x86_64 root=UUID=e6393d35-3392-4c49-b114-278fcc274e13 ro vconsole.font=latarcyrheb-sun16 vconsole.keymap=us rhgb quiet LANG=en_US.UTF-8
[asinha@ankur-laptop  ~]$ journalctl -b -1 | egrep "kernel: Command line:"
Jan 14 00:51:51 ankur-laptop kernel: Command line: BOOT_IMAGE=/vmlinuz-3.11.10-301.fc20.x86_64 root=UUID=e6393d35-3392-4c49-b114-278fcc274e13 ro vconsole.font=latarcyrheb-sun16 vconsole.keymap=us rhgb quiet LANG=en_US.UTF-8
[asinha@ankur-laptop  ~]$ journalctl -b -2 | egrep "kernel: Command line:"
Jan 14 00:47:31 ankur-laptop kernel: Command line: BOOT_IMAGE=/vmlinuz-3.12.7-300.fc20.x86_64 root=UUID=e6393d35-3392-4c49-b114-278fcc274e13 ro vconsole.font=latarcyrheb-sun16 vconsole.keymap=us rhgb quiet LANG=en_US.UTF-8 drm.debug=15
[asinha@ankur-laptop  ~]$ journalctl -b -3 | egrep "kernel: Command line:"
Jan 14 00:43:08 ankur-laptop kernel: Command line: BOOT_IMAGE=/vmlinuz-3.11.10-301.fc20.x86_64 root=UUID=e6393d35-3392-4c49-b114-278fcc274e13 ro vconsole.font=latarcyrheb-sun16 vconsole.keymap=us rhgb quiet LANG=en_US.UTF-8
[asinha@ankur-laptop  ~]$ journalctl -b -4 | egrep "kernel: Command line:"
Jan 14 00:40:56 ankur-laptop kernel: Command line: BOOT_IMAGE=/vmlinuz-3.12.7-300.fc20.x86_64 root=UUID=e6393d35-3392-4c49-b114-278fcc274e13 ro vconsole.font=latarcyrheb-sun16 vconsole.keymap=us rhgb quiet LANG=en_US.UTF-8 drm.debug=15 3
[asinha@ankur-laptop  ~]$

Comment 7 Ankur Sinha (FranciscoD) 2014-01-22 03:00:18 UTC

I reinstalled Fedora 20 afresh because of the scriptlet failure caused by the selinux policy error. Now journalctl seems to give the correct results.

It gave the same log with -b, -b 0, -b -0, info about the currently running boot. Not sure what's changed. Is it possible the the journal was "corrupted" in the earlier install?

[asinha@ankur-laptop  ~]$ diff journalctl-0.log journalctl--0.log
[asinha@ankur-laptop  ~]$ diff journalctl-0.log journalctl-b.log
[asinha@ankur-laptop  ~]$ head journalctl-0.log journalctl--0.log journalctl-b.log
==> journalctl-0.log <==
-- Logs begin at Fri 2014-01-17 10:51:18 EST, end at Wed 2014-01-22 13:53:09 EST. --
Jan 22 13:42:01 localhost.localdomain kernel: Initializing cgroup subsys cpuset
Jan 22 13:42:01 localhost.localdomain kernel: Initializing cgroup subsys cpu
Jan 22 13:42:01 localhost.localdomain kernel: Initializing cgroup subsys cpuacct
Jan 22 13:42:01 localhost.localdomain kernel: Linux version 3.11.10-301.fc20.x86_64 (mockbuild.fedoraproject.org) (gcc version 4.8.2 20131017 (Red Hat 4.8.2-1) (GCC) ) #1 SMP Thu Dec 5 14:01:17 UTC 2013
Jan 22 13:42:01 localhost.localdomain kernel: Command line: BOOT_IMAGE=/vmlinuz-3.11.10-301.fc20.x86_64 root=UUID=27989a5c-5a27-490b-90e4-35dd065bac9c ro vconsole.font=latarcyrheb-sun16 vconsole.keymap=us rhgb quiet LANG=en_US.UTF-8
Jan 22 13:42:01 localhost.localdomain kernel: e820: BIOS-provided physical RAM map:
Jan 22 13:42:01 localhost.localdomain kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000009d3ff] usable
Jan 22 13:42:01 localhost.localdomain kernel: BIOS-e820: [mem 0x000000000009d400-0x000000000009ffff] reserved
Jan 22 13:42:01 localhost.localdomain kernel: BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved

==> journalctl--0.log <==
-- Logs begin at Fri 2014-01-17 10:51:18 EST, end at Wed 2014-01-22 13:53:09 EST. --
Jan 22 13:42:01 localhost.localdomain kernel: Initializing cgroup subsys cpuset
Jan 22 13:42:01 localhost.localdomain kernel: Initializing cgroup subsys cpu
Jan 22 13:42:01 localhost.localdomain kernel: Initializing cgroup subsys cpuacct
Jan 22 13:42:01 localhost.localdomain kernel: Linux version 3.11.10-301.fc20.x86_64 (mockbuild.fedoraproject.org) (gcc version 4.8.2 20131017 (Red Hat 4.8.2-1) (GCC) ) #1 SMP Thu Dec 5 14:01:17 UTC 2013
Jan 22 13:42:01 localhost.localdomain kernel: Command line: BOOT_IMAGE=/vmlinuz-3.11.10-301.fc20.x86_64 root=UUID=27989a5c-5a27-490b-90e4-35dd065bac9c ro vconsole.font=latarcyrheb-sun16 vconsole.keymap=us rhgb quiet LANG=en_US.UTF-8
Jan 22 13:42:01 localhost.localdomain kernel: e820: BIOS-provided physical RAM map:
Jan 22 13:42:01 localhost.localdomain kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000009d3ff] usable
Jan 22 13:42:01 localhost.localdomain kernel: BIOS-e820: [mem 0x000000000009d400-0x000000000009ffff] reserved
Jan 22 13:42:01 localhost.localdomain kernel: BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved

==> journalctl-b.log <==
-- Logs begin at Fri 2014-01-17 10:51:18 EST, end at Wed 2014-01-22 13:53:09 EST. --
Jan 22 13:42:01 localhost.localdomain kernel: Initializing cgroup subsys cpuset
Jan 22 13:42:01 localhost.localdomain kernel: Initializing cgroup subsys cpu
Jan 22 13:42:01 localhost.localdomain kernel: Initializing cgroup subsys cpuacct
Jan 22 13:42:01 localhost.localdomain kernel: Linux version 3.11.10-301.fc20.x86_64 (mockbuild.fedoraproject.org) (gcc version 4.8.2 20131017 (Red Hat 4.8.2-1) (GCC) ) #1 SMP Thu Dec 5 14:01:17 UTC 2013
Jan 22 13:42:01 localhost.localdomain kernel: Command line: BOOT_IMAGE=/vmlinuz-3.11.10-301.fc20.x86_64 root=UUID=27989a5c-5a27-490b-90e4-35dd065bac9c ro vconsole.font=latarcyrheb-sun16 vconsole.keymap=us rhgb quiet LANG=en_US.UTF-8
Jan 22 13:42:01 localhost.localdomain kernel: e820: BIOS-provided physical RAM map:
Jan 22 13:42:01 localhost.localdomain kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000009d3ff] usable
Jan 22 13:42:01 localhost.localdomain kernel: BIOS-e820: [mem 0x000000000009d400-0x000000000009ffff] reserved
Jan 22 13:42:01 localhost.localdomain kernel: BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved
[asinha@ankur-laptop  ~]$

Comment 8 Zbigniew Jędrzejewski-Szmek 2014-01-22 03:20:15 UTC

(In reply to Ankur Sinha (FranciscoD) from comment #7)
> Is it possible the the journal was
> "corrupted" in the earlier install?
That's possible.

I'm don't have any idea how to debug this atm. Let's see if anybody else encounters something similar.

Comment 9 Zbigniew Jędrzejewski-Szmek 2014-10-12 20:44:30 UTC

This should be fixed with the recent changes (not backported yet).

Comment 10 Fedora Update System 2014-10-26 23:10:09 UTC

systemd-208-25.fc20 has been submitted as an update for Fedora 20.
https://admin.fedoraproject.org/updates/systemd-208-25.fc20

Comment 11 Fedora Update System 2014-10-30 11:59:45 UTC

systemd-208-26.fc20,kmod-15-2.fc20 has been submitted as an update for Fedora 20.
https://admin.fedoraproject.org/updates/systemd-208-26.fc20,kmod-15-2.fc20

Comment 12 Fedora Update System 2014-11-01 01:40:30 UTC

Package systemd-208-26.fc20, kmod-15-2.fc20:
* should fix your issue,
* was pushed to the Fedora 20 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing systemd-208-26.fc20 kmod-15-2.fc20'
as soon as you are able to, then reboot.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2014-14032/systemd-208-26.fc20,kmod-15-2.fc20
then log in and leave karma (feedback).

Comment 13 Fedora Update System 2014-11-02 07:26:30 UTC

systemd-208-25.fc20 has been pushed to the Fedora 20 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 14 Fedora Update System 2014-11-05 03:56:17 UTC

systemd-208-26.fc20, kmod-15-2.fc20 has been pushed to the Fedora 20 stable repository.  If problems still persist, please make note of it in this bug report.