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:
In RHEL 9, the config files from /etc/rsyslog.d are included before loading the imjournal module. When a config file tries to adjust the ratelimiting parameters an error is logged:
rsyslogd[37074]: invalid or yet-unknown config file command 'imjournalRatelimitInterval' - have you forgotten to load a module? [v8.2102.0-105.el9 try https://www.rsyslog.com/e/3003 ]
Version-Release number of selected component (if applicable):
8.2102.0-105.el9
I understand your point but please note that it's not recommended to mix up legacy syntax with the new rainerscript format.
For the time being as a workaround, if you really need to alter the ratelimit interval parameter of the imjournal module, then replace
========
module(load="imjournal" # provides access to the systemd journal
StateFile="imjournal.state") # File to store the position in the journal
========
with
========
module(load="imjournal" # provides access to the systemd journal
StateFile="imjournal.state" # File to store the position in the journal
Ratelimit.Interval="some_value") # Specifies the interval in seconds onto which rate-limiting is to be applied
========
May I ask what is the main reason of changing the default of this parameter? Is the default 600 seconds not enough for your use case?
Indeed, the configuration used to trigger the error uses the legacy rsyslog directives because it was easier to put a custom configuration file in /etc/rsyslog.d with the desired rate-limiting directives instead of modifying /etc/rsyslog.conf.
The higher rate is configured for a system running a systemd service that logs many HTTP requests: systemd service output -> journald -> rsyslog -> log file. I know that it is ineffective and we should just use journalctl directly, but other people would like it this way.
The issue is whether the difference between RHEL 9 and RHEL 8 and Fedora is intentional and the RHEL 9 order is the new way or the order should be the same on all of them.
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 (rsyslog bug fix and enhancement update), 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-2023:6444