Bug 1303179 - journalctl's logs verification fails and I never altered it
journalctl's logs verification fails and I never altered it
Product: Fedora
Classification: Fedora
Component: systemd (Show other bugs)
Unspecified Linux
unspecified Severity unspecified
: ---
: ---
Assigned To: systemd-maint
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2016-01-29 14:27 EST by Andrei Cristian Petcu
Modified: 2016-01-29 15:41 EST (History)
7 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2016-01-29 15:41:56 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Andrei Cristian Petcu 2016-01-29 14:27:38 EST
Description of problem:
journalctl's logs verification fails and I never altered it. Is this ok?

Version-Release number of selected component (if applicable):
$journalctl --version
systemd 222

How reproducible:
Every time

Steps to Reproduce:
1. sudo journalctl --verify

Actual results:
Got a lot of "FAIL: File corruption detected at" messages.

Expected results:
All logs should pass. I never changed my logs in any way.

Additional info:
I never used this feature of systemd so I might be misusing it. From what I understand a system with logs that have never been altered should pass the validation.
Comment 1 Zbigniew Jędrzejewski-Szmek 2016-01-29 15:41:56 EST
It usually means that the file was not closed properly when shutting down or similar. You can ignore those failures, journald will remove those failing files following normal rotation of logs.

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