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:
100% CPU usage seen on rsyslog via GnuTLS when TLS connection is broken.

> Version-Release number of selected component (if applicable):
rsyslog-8.2102.0-5.el8.x86_64
rsyslog-gnutls-8.2102.0-5.el8.x86_64

> How reproducible:
Frequently.

> Steps to Reproduce:
1. RHEL 8.3 system
2. Rsyslog with GnuTLS net stream driver is configured
3. 

> Actual results:
Rsyslogd suddenly keeps consuming CPU a lot.

> Expected results:
Rsyslog should be running stable.

> Additional info:
This issue should also affect upstream.

Upstream report: https://github.com/rsyslog/rsyslog/issues/4638

Hello Orion,

Seems no much analysis in the issue you shared. I create an new issue and try to discuss with upstream here: https://github.com/rsyslog/rsyslog/issues/4818.

Thanks,
Flos

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:7460