[Bug 976941] New: journalctl -b shows wrong log entries
http://bugzilla.novell.com/show_bug.cgi?id=976941 Bug ID: 976941 Summary: journalctl -b shows wrong log entries Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: Other OS: openSUSE 13.2 Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening@forge.provo.novell.com Reporter: piny@gmx.com QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- Any offset other than 0 produces a wrong result. Partly, a wrong log entry is presented, partly, the command fails. To set the stage, this is an excerpt of # journalctl --list-boots -284 ee430b062fcf4f0bba0afdf422b9440d Sat 2015-05-09 11:59:48 CEST—Sat 2015-05-09 12:26:42 CEST ... -267 e055338182904c34bb5005c3acc81006 Fri 2015-05-15 11:57:22 CEST—Fri 2015-05-15 13:58:16 CEST -266 987f1c02a1054d1bbe3e235f33bc6555 Fri 2015-05-15 13:58:40 CEST—Sat 2015-05-23 20:43:34 CEST ... -262 8317f4cb2f8f42a5b39bd5355eceba8f Sun 2015-05-24 13:42:36 CEST—Mon 2015-05-25 12:28:56 CEST ... -42 f25299939e3842f79107fa8ba2c8c355 Sat 2016-03-05 11:08:56 CET—Sat 2016-03-05 12:05:59 CET -41 f7783a3abd594fb5ba10ca36872d48a2 Sat 2016-03-05 12:06:58 CET—Sun 2016-03-06 22:24:46 CET ... -2 7f200de4985341f2b1b20b9f7e3ecaef Mon 2016-04-18 22:26:15 CEST—Fri 2016-04-22 02:12:23 CEST -1 477d52a712104f6eb90611fe5987086c Fri 2016-04-22 14:53:36 CEST—Sat 2016-04-23 12:16:25 CEST ... 0 4d3804e3fe53429c999fedc58d4ff682 Sat 2016-04-23 12:17:09 CEST—Sat 2016-04-23 13:00:01 CEST Note: Each time a log is shown the first line consistently reads -- Logs begin at Sat 2015-05-09 11:59:48 CEST, end at Sat 2016-04-23 12:57:43 CEST. -- Examples # journalctl -b 0 Apr 23 12:17:09 ... = 0 >> OK # journalctl -b 1 May 15 13:58:40 ... = -266 >> should be -284? # journalctl -b 2 May 24 13:42:36 ... = -262 >> should be -283?
so not only some offset, but also some iteration offset?
# journalctl -b -1 Mar 05 12:06:58 ... = -41 >> should be -1! # journalctl -b -2 Mar 05 11:08:56 ... = -42 >> should be -2! same behaviour with "-boot=-2" syntax Another strange result: # journalctl -b -284 Failed to look up boot -284: Cannot assign requested address checking the limit: # journalctl -b -144 May 15 13:58:40 ... = -266 >> should be -144 = same wrong result as -b 1! # journalctl -b -145 Failed to look up boot -145: Cannot assign requested address
should be -145!
However, try checking for -267 with boot ID: journalctl _BOOT_ID=e055338182904c34bb5005c3acc81006q May 15 11:57:22 ... = -267, OK dito for -284 # journalctl _BOOT_ID=ee430b062fcf4f0bba0afdf422b9440d May 09 11:59:48 = -284, OK For any boot id the --boot syntax fails, example: # journalctl --boot=4d3804e3fe53429c999fedc58d4ff682 Failed to look up boot ID 4d3804e3fe53429c999fedc58d4ff682+0: Cannot assign requested address but # journalctl _BOOT_ID=4d3804e3fe53429c999fedc58d4ff682 Apr 23 12:17:09 ... = 0, OK Further info: # journalctl --version systemd 210 +PAM -LIBWRAP +AUDIT +SELINUX -IMA +SYSVINIT +LIBCRYPTSETUP +GCRYPT +ACL +XZ +SECCOMP +APPARMOR -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=976941
Pi Ny
participants (1)
-
bugzilla_noreply@novell.com