Bug 891798
Summary: | fail2ban logrotate script is either useless or mangles up the setting of fail2ban's logtarget | ||||||
---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora EPEL | Reporter: | Christoph Anton Mitterer <calestyo> | ||||
Component: | fail2ban | Assignee: | Orion Poplawski <orion> | ||||
Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
Severity: | medium | Docs Contact: | |||||
Priority: | unspecified | ||||||
Version: | el6 | CC: | admiller, daniel, orion | ||||
Target Milestone: | --- | ||||||
Target Release: | --- | ||||||
Hardware: | All | ||||||
OS: | All | ||||||
Whiteboard: | |||||||
Fixed In Version: | fail2ban-0.8.13-2.el6 | Doc Type: | Bug Fix | ||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2014-08-15 18:58:39 UTC | Type: | Bug | ||||
Regression: | --- | Mount Type: | --- | ||||
Documentation: | --- | CRM: | |||||
Verified Versions: | Category: | --- | |||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
Cloudforms Team: | --- | Target Upstream Version: | |||||
Embargoed: | |||||||
Attachments: |
|
Description
Christoph Anton Mitterer
2013-01-04 02:56:06 UTC
Some additions/corrections: 1) As Yaroslav pointed out in the corresponding Debian bug... the whole thing to find out the current logtarget (to then re-set it) can be done much easier with fail2ban-client get logtarget 2) Even when the postrotate phase is made dynamic,... the logrotate config snippet will still apply only to /var/log/fail2ban. So the only advantage we'd get is, that the user would need to modify the logrotate config snippet only in the first line,... not the postrotate phase. And the problem of useless "empty" rotations in the case that e.g. SYSLOG is used as target isn't solved either. upstream bug: https://github.com/fail2ban/fail2ban/issues/458 might see if I can implement a flushlog method on fail2ban-client. Upstream fix committed. https://github.com/fail2ban/fail2ban/pull/470/files fail2ban-0.8.13-1.el6 has been submitted as an update for Fedora EPEL 6. https://admin.fedoraproject.org/updates/fail2ban-0.8.13-1.el6 Package fail2ban-0.8.13-1.el6: * should fix your issue, * was pushed to the Fedora EPEL 6 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=epel-testing fail2ban-0.8.13-1.el6' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-EPEL-2014-1985/fail2ban-0.8.13-1.el6 then log in and leave karma (feedback). Package fail2ban-0.8.13-2.el6: * should fix your issue, * was pushed to the Fedora EPEL 6 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=epel-testing fail2ban-0.8.13-2.el6' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-EPEL-2014-1985/fail2ban-0.8.13-2.el6 then log in and leave karma (feedback). fail2ban-0.8.13-2.el6 has been pushed to the Fedora EPEL 6 stable repository. If problems still persist, please make note of it in this bug report. |