Bug 1095784

Summary:	imjournal.state easily corrupted
Product:	Red Hat Enterprise Linux 7	Reporter:	Nate Straz <nstraz>
Component:	rsyslog	Assignee:	Tomas Heinrich <theinric>
Status:	CLOSED DUPLICATE	QA Contact:	BaseOS QE Security Team <qe-baseos-security>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	7.0	CC:	pvrabec, twright
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-05-08 18:56:29 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 Nate Straz 2014-05-08 13:54:45 UTC

Description of problem:

I've found during recovery testing that the file /var/lib/rsyslog/imjournal.state is easily corrupted.  When that happens, /var/log/messages stops recording logs from the journal.  The file needs to be manually removed and rsyslogd restarted.

May  7 22:26:09 host-074 rsyslogd: [origin software="rsyslogd" swVersion="7.4.7" x-pid="547" x-info="http://www.rsyslog.com"] start
May  7 22:26:09 host-074 rsyslogd-2027: imjournal: fscanf on state file `/var/lib/rsyslog/imjournal.state' failed

[root@host-074 rsyslog]# ls -l /var/lib/rsyslog/
total 0
-rw-r--r--. 1 root root 0 May  7 22:25 imjournal.state


Version-Release number of selected component (if applicable):
rsyslog-7.4.7-6.el7.x86_64
systemd-208-11.el7.x86_64

How reproducible:
Easily

Steps to Reproduce:
1. reboot -ff
2.
3.

Actual results:


Expected results:


Additional info:

Comment 2 Tomas Heinrich 2014-05-08 18:56:29 UTC

The contents of /var/lib/rsyslog/imjournal.state are only manipulated through systemd API.

*** This bug has been marked as a duplicate of bug 1088021 ***