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.
1. Proposed title of this feature request
(RFE RHEL-7.7 (or later): rsyslogd: imjournal: messages lost due to rate-limiting should also print burst+interva
3. What is the nature and description of the request?
Improve the quality and usefullness of syslog messages
4. Why does the customer need this? (List the business requirements here)
When the defaults are shown, the customer does not have to open a ticket with redhat.
The customer can use the time more efficient and continue to work on the underlying
problem more quickly.
5. How would the customer like to achieve this? (List the functional requirements here)
Improve the message as described.
6. For each functional requirement listed, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented.
As soon as rate-limiting triggers, the message can be observed.
Also changing the limits to trigger earlier, the problem can be reproduced easier and
also it can show the correct values are printed.
7. Is there already an existing RFE upstream or in Red Hat Bugzilla?
I don`t know.
8. Does the customer have any specific timeline dependencies and which release would they like to target (i.e. RHEL5, RHEL6)?
RHEL8
10. List any affected packages or components.
rsyslogd (as far as I know)
11. Would the customer be able to assist in testing this functionality if implemented?
Yes.
Actual behaviour:
65180 Sep 22 16:40:01 evesp07 rsyslogd: imjournal: 17190 messages lost due to rate-limiting
Expected behaviour:
It should print the parameters which are in effect.
65180 Sep 22 16:40:01 evesp07 rsyslogd: imjournal: 17190 messages lost due to rate-limiting (20000 messages allowed in 600 seconds)
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/RHSA-2020:1702