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 audit 2.2.2-2 there is the following change in audisp-remote.c when compared to 2.2.1-2:
< if (sock > 0 && FD_ISSET(sock, &wfd))
< send_one(queue);
---
> if (sock > 0 && FD_ISSET(sock, &wfd)) {
> // If so, try to drain backlog
> while (q_queue_length(queue)&& !suspend && transport_ok)
> send_one(queue);
> }
Sending a pile of messages from the queue might be a problem if, for instance, remote audit.log partition is full and audit-remote plug-in action in set to "stop". In that case all records from queue will be sent as far as I can see and (eg.) rsyslog will be totally over-flooded with "remote logging stopping due to remote server's disk is full, disk full" messages.
I am not sure if this is intended or not, but aforementioned flooding can be reproduced quite easily. In just 2 minutes, I see 397797 messages "remote logging stopping..." in /v/l/m.
Version-Release number of selected component (if applicable):
audit-2.2.2-2.el7
How reproducible:
100%
Steps to Reproduce:
1. configure audit remote logging with disk full action "stop"
2. fill remote audit partition so that disk full action is triggered
3. search "remote logging stopping..." message in /v/l/m
Actual results:
Thousands of messages found, over-flooded /var/log/messages (but auditd is correctly stopped).
Expected results:
A reasonable number of messages found (and auditd stopped).
Additional info:
There is a very reliable reproducer available in our development branch of audit-test for RHEL7.
This request was resolved in Red Hat Enterprise Linux 7.0.
Contact your manager or support representative in case you have further questions about the request.
Description of problem: In audit 2.2.2-2 there is the following change in audisp-remote.c when compared to 2.2.1-2: < if (sock > 0 && FD_ISSET(sock, &wfd)) < send_one(queue); --- > if (sock > 0 && FD_ISSET(sock, &wfd)) { > // If so, try to drain backlog > while (q_queue_length(queue)&& !suspend && transport_ok) > send_one(queue); > } Sending a pile of messages from the queue might be a problem if, for instance, remote audit.log partition is full and audit-remote plug-in action in set to "stop". In that case all records from queue will be sent as far as I can see and (eg.) rsyslog will be totally over-flooded with "remote logging stopping due to remote server's disk is full, disk full" messages. I am not sure if this is intended or not, but aforementioned flooding can be reproduced quite easily. In just 2 minutes, I see 397797 messages "remote logging stopping..." in /v/l/m. Version-Release number of selected component (if applicable): audit-2.2.2-2.el7 How reproducible: 100% Steps to Reproduce: 1. configure audit remote logging with disk full action "stop" 2. fill remote audit partition so that disk full action is triggered 3. search "remote logging stopping..." message in /v/l/m Actual results: Thousands of messages found, over-flooded /var/log/messages (but auditd is correctly stopped). Expected results: A reasonable number of messages found (and auditd stopped). Additional info: There is a very reliable reproducer available in our development branch of audit-test for RHEL7.