Bug 1303179

Summary:	journalctl's logs verification fails and I never altered it
Product:	[Fedora] Fedora	Reporter:	Andrei Cristian Petcu <andreip>
Component:	systemd	Assignee:	systemd-maint
Status:	CLOSED NOTABUG	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	23	CC:	johannbg, lnykryn, msekleta, muadda, s, systemd-maint, zbyszek
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-01-29 20:41:56 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

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.