[systemd-bugs] [Bug 64566] New: journalctl does not terminate, keeps printing in a loop

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=64566

          Priority: medium
            Bug ID: 64566
          Assignee: systemd-bugs at lists.freedesktop.org
           Summary: journalctl does not terminate, keeps printing in a
                    loop
        QA Contact: systemd-bugs at lists.freedesktop.org
          Severity: normal
    Classification: Unclassified
                OS: All
          Reporter: lekensteyn at gmail.com
          Hardware: All
            Status: NEW
           Version: unspecified
         Component: general
           Product: systemd

Created attachment 79274
  --> https://bugs.freedesktop.org/attachment.cgi?id=79274&action=edit
used for git bisect run

I have recently noticed issues with the use of `journalctl -a` (Arch Linux on
Raspberry Pi) and `journalctl --since today` (Arch Linux x86_64). Where the
command should stop (on end of log file), it continues printing older entries
and repeats that until the journalctl is killed.

I suspect it is related to corrupted logs or to the timestamps, the Raspberry
Pi boots with a timestamp in 1970, my laptop's RTC somehow jumped back 7 hours.

results of bisect:
a3e6f050de81a9830e52af09d5d38dad9a356e3b is the first bad commit
commit a3e6f050de81a9830e52af09d5d38dad9a356e3b
Author: Marius Vollmer <marius.vollmer at redhat.com>
Date:   Thu Apr 18 22:34:36 2013 +0200

    journal: when iterating through a file we might lose messages when changing
direction.

    https://bugs.freedesktop.org/show_bug.cgi?id=63672

:100644 100644 1221b39cd419325010e331d66068c1fd44039816
cd66914b5c6da29db002723e4eb7487f1070b35c M      TODO
:040000 040000 a0196f64399d332d2fd43455f3bc0575146d3806
a0bf7285eddc892d51642be205983bc11f85ac9c M      src

Reverting this commit on master (v204-25-g32821c7) fixes the wrap-around issue.

I prefer not to share the logs in public, if you need them please send me a
email. Attached is a quick-n-dirty bisect script which I used to isolate the
faulty commit.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/systemd-bugs/attachments/20130513/63ceb6d0/attachment-0001.html>