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 2064318 - [RFE] rsyslog action.errorfile max size
Summary: [RFE] rsyslog action.errorfile max size
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: rsyslog
Version: 9.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: rc
: ---
Assignee: Sergio Arroutbi
QA Contact: Dalibor Pospíšil
Jan Fiala
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-03-15 14:33 UTC by Sergio Arroutbi
Modified: 2022-11-15 10:14 UTC (History)
3 users (show)

Fixed In Version: rsyslog-8.2102.0-102.el9
Doc Type: Enhancement
Doc Text:
.Added a maximum size option for Rsyslog error files Using the new `action.errorfile.maxsize` option, you can specify a maximum number of bytes of the error file for the Rsyslog log processing system. When the error file reaches the specified size, Rsyslog cannot write any additional errors or other data in it. This prevents the error file from filling up the file system and making the host unusable.
Clone Of: 1962318
Environment:
Last Closed: 2022-11-15 09:53:07 UTC
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-115627 0 None None None 2022-03-15 14:52:34 UTC
Red Hat Issue Tracker SECENGSP-4423 0 None None None 2022-03-15 14:52:36 UTC
Red Hat Product Errata RHBA-2022:7963 0 None None None 2022-11-15 09:53:13 UTC

Description Sergio Arroutbi 2022-03-15 14:33:41 UTC
+++ This bug was initially created as a clone of Bug #1962318 +++

SUMMARY: RFE

1. Proposed title of this feature request

[RFE] rsyslog action.errorfile max size

2. Who is the customer behind the request?

Account: Citigroup
Account #: 411070
TAM customer: yes
CSM customer: yes
Strategic: yes

3. What is the nature and description of the request?

This is a request to add max errorfile option to rsyslog. Without a logfile size management rsyslog error file can fill up the filesystem and render the host useless.

4. Why does the customer need this? (List the business requirements here)

The solution is to mitigate host vulnerability against a possible service outage generated by a large rsyslog errorfile that can grow without limit.

5. How would the customer like to achieve this? (List the functional requirements here)

By implementing an a configuration option in rsyslog for the max size of an error file, such as other similar services already have (Eg: journald, auditd)

6. For each functional requirement listed, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented.

Once the max error file size option is implemented we can test that that rsyslog does not create an error log file larger than max size.

7. Is there already an existing RFE upstream or in Red Hat Bugzilla?
No

8. Does the customer have any specific timeline dependencies and which release would they like to target (i.e. RHEL8, RHEL9)?
RHEL9

9. Is the sales team involved in this request and do they have any additional input?
No

10. List any affected packages or components.
rsyslog

11. Would the customer be able to assist in testing this functionality if implemented?
Yes

Comment 14 errata-xmlrpc 2022-11-15 09:53:07 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 (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-2022:7963


Note You need to log in before you can comment on or make changes to this bug.