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 1497985 - rsyslog daemon have unkown log entries "rsyslogd:imjournal: journal reloaded" from time to time
Summary: rsyslog daemon have unkown log entries "rsyslogd:imjournal: journal reloaded"...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: rsyslog
Version: 7.4
Hardware: x86_64
OS: Linux
urgent
high
Target Milestone: rc
: ---
Assignee: Radovan Sroka
QA Contact: Dalibor Pospíšil
URL:
Whiteboard:
Depends On:
Blocks: 1563145
TreeView+ depends on / blocked
 
Reported: 2017-10-03 09:45 UTC by Vansen Ng
Modified: 2020-12-14 10:21 UTC (History)
10 users (show)

Fixed In Version: rsyslog-8.24.0-13.el7
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1563145 (view as bug list)
Environment:
Last Closed: 2018-04-10 15:26:37 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
proposed patch (1.97 KB, patch)
2017-10-09 15:18 UTC, Radovan Sroka 		no flags Details | Diff
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2018:0856 0 None None None 2018-04-10 15:27:12 UTC

Description Vansen Ng 2017-10-03 09:45:10 UTC 
Description of problem:

I use the rsyslog to record logs. After upgrding from rhel7u2 to rhel7u4, I found there is the following unkown logs entried in /var/log/messages. But there is no such error in rhel7u2.  rsyslog use v7 version in rhel7u2 and v8 version in rhel7u4.

~~~
Sep 22 15:25:01 <user.info> test yum[7218]:Updated: rsyslog-8.24.0-12.el7.x86_64
Sep 22 15:25:45 <user.info> test yum[7218]:Updated: rsyslog-mmjsonparse-8.24.0-12.el7.x86_64
Sep 23 00:18:01 <syslog.err> test rsyslogd:imjournal: journal reloaded... [v8.24.0 try http://www.rsyslog.com/e/0 ]
Sep 23 08:39:01 <syslog.err> test rsyslogd:imjournal: journal reloaded... [v8.24.0 try http://www.rsyslog.com/e/0 ]
Sep 23 17:00:01 <syslog.err> test rsyslogd:imjournal: journal reloaded... [v8.24.0 try http://www.rsyslog.com/e/0 ]
Sep 24 01:23:02 <syslog.err> test rsyslogd:imjournal: journal reloaded... [v8.24.0 try http://www.rsyslog.com/e/0 ]
~~~


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

3.10.0-693.2.2.el7.x86_64(rhel7u4)
rsyslog-8.24.0-12.el7.x86_64
systemd-219-42.el7_4.1.x86_64

How reproducible:

I could re-produce this error in rhel7u4 environment from time to time. Below are my steps:

Steps to Reproduce:

1. Use default rsyslog setting; Run "for i in `seq 1 3000`;do logger -p local5.info "modify syslog rate limit modify 1640: $i" ;done" for six times.

2. Check the rsyslog output logs in /var/log/messages

PS: Since these error logs come out in /var/log/messages from time to time, it might need to run the above command for times. 

Actual results(two entries in /var/log/messages):

[root@rhel7u4 ~]# grep imjournal /var/log/messages
Oct  2 23:37:39 <syslog.err> rhel7u4 rsyslogd:imjournal: journal reloaded... [v8.24.0 try http://www.rsyslog.com/e/0 ]
Oct  2 23:38:55 <syslog.err> rhel7u4 rsyslogd:imjournal: journal reloaded... [v8.24.0 try http://www.rsyslog.com/e/0 ]

Expected results:

There is no such error in daily running. Is it rsyslog bug or something else?

Additional info:

In rhel7u2,rhel7u2, system use rsyslog v7. But in rhel7u4, it upgrade to rsyslog v8.
Comment 2 Radovan Sroka 2017-10-03 09:56:00 UTC 
Hi,

this message means only that journald logs were rotated, journald restarted or its files were changed between runtime and permanent. 

So it is basically info message, but we can remove it totally or move under debug mode.
Comment 4 Flos Qi Guo 2017-10-09 03:35:26 UTC 
Hi yisheng,

This should be a trivial issue when backporting upstream's code in rhbz #1419228. The code in upstream has the right log level:

https://github.com/rsyslog/rsyslog/pull/1747/files#diff-b1ea6478b8060f07cd30ecde78bfdc49R518

Best regards,
Flos
Comment 11 Radovan Sroka 2017-10-09 15:18:39 UTC 
Created attachment 1336444 [details]
proposed patch
Comment 23 errata-xmlrpc 2018-04-10 15:26:37 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2018:0856
Note You need to log in before you can comment on or make changes to this bug.