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.

Description of problem:

We are seeing this periodically on machines (every week or so?):

Sep 24 09:28:02 host rsyslogd[10109]: imjournal: journal reloaded... [v8.24.0-41.el7_7 try http://www.rsyslog.com/e/0 ]
Sep 24 09:28:04 host rsyslogd[10109]: imjournal: begin to drop messages due to rate-limiting
Sep 24 09:29:01 host rsyslogd[10109]: imjournal: 394963 messages lost due to rate-limiting

# ls -l /var/lib/rsyslog/
total 4
-rw-------. 1 root root 127 Sep 18 03:34 imjournal.state

And we see old messages appearing in /var/log/messages:

Sep 23 01:14:46 host named[22665]: network unreachable resolving 'ns-332.awsdns-41.com/AAAA/IN': 2600:9000:5304:a900::1#53
Sep 23 01:14:46 host named[22665]: network unreachable resolving 'ns-560.awsdns-06.net/A/IN': 2600:9000:5303:800::1#53
Sep 23 01:14:46 host named[22665]: network unreachable resolving 'ns-1769.awsdns-29.co.uk/A/IN': 2600:9000:5307:2100::1#53
Sep 18 03:34:18 host systemd: Stopping System Logging Service...
Sep 18 03:34:18 host rsyslogd: [origin software="rsyslogd" swVersion="8.24.0-34.el7" x-pid="3464" x-info="http://www.rsyslog.com"] exiting on signal 15.

So it seems like the state file is not being updated before the journal is reloaded.  This started for us with rsyslog-8.24.0-41.el7_7.x86_64 on EL7.7.

Hi Orion,

which version you were using prior to 8.24.0-41 please?

Orion, the version you are currently using contains a bug which will be fixed by next update, from the symptoms and the fact it did not happen before it seems to affect you as well. Please apply next available update when it is released.

Thanks, will do.  For the record, previous version was rsyslog-8.24.0-38.el7.x86_64

Product Experience has reviewed this Bugzilla and has evaluated that it will not be resolved in RHEL 7. 
RHEL 7.9 will release in Maintenance Phase 1 where only "Critical and Important Security errata advisories (RHSAs) and Urgent Priority Bug Fix errata advisories (RHBAs) may be released". 
https://access.redhat.com/support/policy/updates/errata#Maintenance_Support_1_Phase
This BZ does not appear to meet Maintenance Support 1 Phase criteria so is being closed WONTFIX.