Bug 1303179 - journalctl's logs verification fails and I never altered it
Summary: journalctl's logs verification fails and I never altered it
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: systemd
Version: 23
Hardware: Unspecified
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: systemd-maint
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-01-29 19:27 UTC by Andrei Cristian Petcu
Modified: 2016-01-29 20:41 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-01-29 20:41:56 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Andrei Cristian Petcu 2016-01-29 19:27:38 UTC
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
+PAM +AUDIT +SELINUX +IMA -APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ -LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD +IDN

How reproducible:
Every time

Steps to Reproduce:
1. sudo journalctl --verify

Actual results:
https://paste.fedoraproject.org/316305/45408886/
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 20:41:56 UTC
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.