RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1095784 - imjournal.state easily corrupted
Summary: imjournal.state easily corrupted
Keywords:
Status: CLOSED DUPLICATE of bug 1088021
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: rsyslog
Version: 7.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Tomas Heinrich
QA Contact: BaseOS QE Security Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-05-08 13:54 UTC by Nate Straz
Modified: 2016-09-20 04:52 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-05-08 18:56:29 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

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 ***


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