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.
DescriptionJonathon Anderson
2012-08-05 06:54:39 UTC
Description of problem:
We have fail2ban configured with loglevel = 3, logtarget = SYSLOG; but fail2ban is logging to syslog with kern.emerg priority.
kern.emerg<0>: Aug 1 18:08:44 gate1 ?<28>fail2ban.actions: WARNING [ssh-iptables] Unban 10.228.1.11
Effectively, this means that such messages are logged to all user consoles, due to the default rsyslog config on RHEL6.
*.emerg *
Version-Release number of selected component (if applicable):
RHEL6.3, fail2ban-0.8.4-28.el6.noarch
How reproducible:
Always.
Steps to Reproduce:
1. Install fail2ban and configure for ssh banning
2. Invoke a ban (or wait for an unban)
Actual results:
Message is logged to syslog as an emergency.
Expected results:
Message is logged as info (loglevel 3).
Comment 2Jonathon Anderson
2012-08-28 08:33:06 UTC
> This appears to have been fixed in fail2ban 0.8.7
It looks like the latest in EPEL is 0.8.4(-28). What needs to happen to get this fix backported, or get fail2ban upgraded?
I don't maintain this package for "Fedora proper", only EPEL and I would like not to have EPEL be ahead of Fedora, please file a request for the Fedora package to be updated and I will happily follow suit.
> I don't maintain this package for "Fedora proper", only EPEL and I would
> like not to have EPEL be ahead of Fedora, please file a request for the
> Fedora package to be updated and I will happily follow suit.
Done: bug# 864998
Is there an ETA on when an update containing this fix will be released?
Comment 19Bohuslav "Slavek" Kabrda
2013-10-14 09:04:42 UTC
(In reply to James Juran from comment #18)
> Is there an ETA on when an update containing this fix will be released?
Hello James,
bugfix for this issue will be part of next RHEL 6 minor release.
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.
http://rhn.redhat.com/errata/RHSA-2013-1582.html