Bug 1544139

Summary:	rsyslogd: imjournal: open on state file `/var/lib/rsyslog/imjournal.state' failed [v8.32.0 try http://www.rsyslog.com/e/2013 ]
Product:	[Fedora] Fedora	Reporter:	Mairi Dulaney <jdulaney>
Component:	rsyslog	Assignee:	Jiří Vymazal <jvymazal>
Status:	CLOSED ERRATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	27	CC:	dkopecek, jlieskov, jvymazal, lkundrak, mah.darade, rsroka, tosykora
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:	rsyslog-8.37.0-1.fc28 rsyslog-8.37.0-1.fc27	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-08-11 19:12:23 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 Mairi Dulaney 2018-02-10 15:46:17 UTC

Description of problem:
When running /sbin/rysyslogd, I get the error:
rsyslogd: imjournal: open on state file `/var/lib/rsyslog/imjournal.state' failed  [v8.32.0 try http://www.rsyslog.com/e/2013 ]

Version-Release number of selected component (if applicable):
rsyslog-8.32.0-1.fc27.x86_64

How reproducible:
Always

Steps to Reproduce:
1.  install rsyslog in updated fedora 27 docker image
2.  docker exec -it <container name> bash
3.  /sbin/rsyslogd

Actual results:
Error

Expected results:
No Error

Additional info:
Host system is up to date f27

Comment 1 Mairi Dulaney 2018-02-10 16:00:59 UTC

Oh, I should note that the file in question is not present.

Comment 2 Jiří Vymazal 2018-07-02 14:39:08 UTC

This needs to be fixed upstream first, in the meantime easy workaround is to simply restart rsyslog for the first time after install, it will work afterwards.

Comment 3 Jiří Vymazal 2018-07-26 07:56:57 UTC

Upstream PR has been merged, I will solve this with 8.37.0 rebase.

Comment 4 Jiří Vymazal 2018-08-08 10:18:18 UTC

Fedora commit:
==============
https://src.fedoraproject.org/rpms/rsyslog/c/af881d48de4334ccf5699239e1a59420d1a79ebd?branch=master

Comment 5 Fedora Update System 2018-08-08 12:50:41 UTC

rsyslog-8.37.0-1.fc27 has been submitted as an update to Fedora 27. https://bodhi.fedoraproject.org/updates/FEDORA-2018-2818fc5308

Comment 6 Fedora Update System 2018-08-08 12:51:04 UTC

rsyslog-8.37.0-1.fc28 has been submitted as an update to Fedora 28. https://bodhi.fedoraproject.org/updates/FEDORA-2018-749f2bae28

Comment 7 Fedora Update System 2018-08-08 14:27:07 UTC

rsyslog-8.37.0-1.fc27 has been pushed to the Fedora 27 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2018-2818fc5308

Comment 8 Fedora Update System 2018-08-08 17:15:10 UTC

rsyslog-8.37.0-1.fc28 has been pushed to the Fedora 28 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2018-749f2bae28

Comment 9 Fedora Update System 2018-08-11 19:12:23 UTC

rsyslog-8.37.0-1.fc28 has been pushed to the Fedora 28 stable repository. If problems still persist, please make note of it in this bug report.

Comment 10 Fedora Update System 2018-08-16 14:55:49 UTC

rsyslog-8.37.0-1.fc27 has been pushed to the Fedora 27 stable repository. If problems still persist, please make note of it in this bug report.