Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
DescriptionThomas Scheunemann
2019-09-19 14:51:24 UTC
Description of problem:
After updating to RHEL 7.7 log messages get duplicated whenever rsyslog is restarted.
Version-Release number of selected component (if applicable):
8.24.0-41.el7_7.x86_64
How reproducible:
Always
Steps to Reproduce:
1. update to 7.7
2. systemctl restart rsyslog
Actual results:
Old Log-Messages get repeated in Log-Files.
Expected results:
Only new messages added to Log-Files
Additional info:
The problem seems to be that "imjournal.state" is not updated or created if
it is missing. This results in imjournal using an empty or old statefile and
therefore treats old messages as new messages.
Comment 2Thomas Scheunemann
2019-09-20 11:00:02 UTC
This happens only with the Option WorkAroundJournalBug="on" set in "rsyslog.conf".
Setting WorkAroundJournalBug to "off" or not setting it at all makes it work as intended.
How did you came to have this version please? 8.24.0-41 is not supposed to be on RHEL-7.7
Comment 4Thomas Scheunemann
2019-09-23 08:55:44 UTC
Actually I ran into this version on CentOS 7.7.
But I reported this only after verifying that the same error happens in the version that I could download via RedHat Download Page.
I just checked and this is officially the latest version on "RedHat Enterprise Linux Server x86_64 packages" for RHEL 7.7 rsyslog.
It says on that page that this is from the repos of active subscriptions, but I didn't check if its actually available in any Red Hat repository.
Ok, I found internal bug that this corresponds to. I t will be fixed in next release for both 7.8 and 7.7. Many thanks for reporting. I will close this know, if this is not fixed after update on newer version feel free to reopen.
*** This bug has been marked as a duplicate of bug 1752424 ***