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 1495631 - Journal is reloaded and duplicate messages are output into log file.
Summary: Journal is reloaded and duplicate messages are output into log file.
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: rsyslog
Version: 7.4
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: rc
: ---
Assignee: Radovan Sroka
QA Contact: BaseOS QE Security Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-09-26 11:13 UTC by Xueying Nie
Modified: 2021-07-21 13:26 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-10-10 08:29:45 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Xueying Nie 2017-09-26 11:13:38 UTC 
Description of problem:

Journal is reloaded and duplicate messages are output into log file.

Version-Release number of selected component (if applicable):

rsyslog-8.24.0-12.el7.x86_64

How reproducible:


Steps to Reproduce:
1. Disable the rate-limiting of journald.
    -/etc/systemd/journald.conf
　 RateLimitInterval=0  

2. Execute the command below.
   # for i in `seq 1 3000`;do logger -p local5.info "modify syslog rate limit modify 1640: $i" ;done 

3. Check /var/log/messages.

Actual results:

Journal reloaded and some duplicate messages are output to log file.
~~~
Sep 14 20:19:01 R74Router root: modify syslog rate limit modify 1640: 871
Sep 14 20:19:01 R74Router root: modify syslog rate limit modify 1640: 872
Sep 14 20:19:01 R74Router root: modify syslog rate limit modify 1640: 873
Sep 14 20:19:01 R74Router root: modify syslog rate limit modify 1640: 865  <
Sep 14 20:19:01 R74Router root: modify syslog rate limit modify 1640: 866  <
Sep 14 20:19:01 R74Router root: modify syslog rate limit modify 1640: 867  <
Sep 14 20:19:01 R74Router root: modify syslog rate limit modify 1640: 868  <
Sep 14 20:19:01 R74Router root: modify syslog rate limit modify 1640: 869  <
Sep 14 20:19:01 R74Router root: modify syslog rate limit modify 1640: 870  <
Sep 14 20:19:01 R74Router root: modify syslog rate limit modify 1640: 871  <
Sep 14 20:19:01 R74Router root: modify syslog rate limit modify 1640: 872  <
Sep 14 20:19:01 R74Router root: modify syslog rate limit modify 1640: 873  <
Sep 14 20:19:01 R74Router root: modify syslog rate limit modify 1640: 874
Sep 14 20:19:01 R74Router rsyslogd: imjournal: journal reloaded... [v8.24.0 try http://www.rsyslog.com/e/0 ]
Sep 14 20:19:01 R74Router root: modify syslog rate limit modify 1640: 875
~~~

Expected results:

No duplicate messages are output to the file.
~~~
Sep 14 20:19:01 R74Router root: modify syslog rate limit modify 1640: 871
Sep 14 20:19:01 R74Router root: modify syslog rate limit modify 1640: 872
Sep 14 20:19:01 R74Router root: modify syslog rate limit modify 1640: 873
Sep 14 20:19:01 R74Router root: modify syslog rate limit modify 1640: 874
Sep 14 20:19:01 R74Router root: modify syslog rate limit modify 1640: 875
~~~

Additional info:

There is no duplicate messages in Journal.
Comment 2 Radovan Sroka 2017-09-27 15:38:23 UTC 
Actually I cannot reproduce this issue. 

Can you try to set PersistStateInterval for imjournal to 1?

If this works, this is expected behavior.

With reloading of journal or rsyslog itself, it comes the price. It is technically impossible to handle duplication of messages. Duplication is always =< PersistStateInterval. But PersistStateInterval = 1 has impact on performance.
Note You need to log in before you can comment on or make changes to this bug.