Bug 1388850 - wrong timestamp of "journalctl -b -0" /"journalctl -b -1"
Summary: wrong timestamp of "journalctl -b -0" /"journalctl -b -1"
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: systemd
Version: 25
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: systemd-maint
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-10-26 10:01 UTC by lnie
Modified: 2016-11-15 09:00 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-11-15 09:00:54 UTC
Type: Bug


Attachments (Terms of Use)
screenshot (219.07 KB, image/png)
2016-10-26 10:01 UTC, lnie
no flags Details
journal (239.66 KB, text/x-vhdl)
2016-10-26 10:02 UTC, lnie
no flags Details

Description lnie 2016-10-26 10:01:36 UTC
Created attachment 1214234 [details]
screenshot

Description of problem:
Please see the attached picture for the specific information,thanks.

Version-Release number of selected component (if applicable):
systemd-231-10.fc25.x86_64

How reproducible:
always

Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 lnie 2016-10-26 10:02:40 UTC
Created attachment 1214235 [details]
journal

Comment 2 Zbigniew Jędrzejewski-Szmek 2016-10-29 17:46:25 UTC
This might be caused a time jump (for example from the clock being set incorrectly and then being set properly by ntp). Systemd-232 had a bunch of fixes for that case. You might want to try with systemd-232 (when it is released, should be soon now, unfortunately only for rawhide, not for F25).

If you want me to look at this further, please send me the raw journal files, it's hard to say anything about his from the text output of journalctl.


Note You need to log in before you can comment on or make changes to this bug.