Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1549474 - journalctl stops working as soon as it encounters an empty journal file [rhel-7.4.z]
journalctl stops working as soon as it encounters an empty journal file [rhel...
Status: CLOSED ERRATA
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: systemd (Show other bugs)
7.3
x86_64 Linux
urgent Severity low
: rc
: ---
Assigned To: systemd-maint
Frantisek Sumsal
Marie Dolezelova
: ZStream
Depends On: 1465759
Blocks:
  Show dependency treegraph
 
Reported: 2018-02-27 03:03 EST by Oneata Mircea Teodor
Modified: 2018-03-06 16:50 EST (History)
7 users (show)

See Also:
Fixed In Version: systemd-219-42.el7_4.10
Doc Type: Bug Fix
Doc Text:
Previously, the journalctl utility stopped when it encountered an empty file in the systemd journal logs. With this update, systemd has been fixed to report an error message about such situation, and to continue scanning other files in the journal log under the described circumstances.
Story Points: ---
Clone Of: 1465759
Environment:
Last Closed: 2018-03-06 16:50:34 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2018:0416 normal SHIPPED_LIVE systemd bug fix update 2018-03-06 21:46:04 EST

  None (edit)
Description Oneata Mircea Teodor 2018-02-27 03:03:26 EST
This bug has been copied from bug #1465759 and has been proposed to be backported to 7.4 z-stream (EUS).
Comment 6 errata-xmlrpc 2018-03-06 16:50:34 EST
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2018:0416

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