Bug 1047436
| Summary: | Fail2ban fails to start because of /var/log/secure not found | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Vladislav Grigoryev <vg.aetera> |
| Component: | fail2ban | Assignee: | Orion Poplawski <orion> |
| Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 20 | CC: | Axel.Thimm, jonathan.underwood, orion, vg.aetera, vgulch, vonsch |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2015-06-30 01:33:57 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: | |||
|
Description
Vladislav Grigoryev
2013-12-31 06:43:40 UTC
Workaround: echo -e '[DEFAULT]\nbackend=systemd' >/etc/fail2ban/jail.d/common.conf fail2ban-0.9-3 and later in F21 takes the approach of splitting fail2ban up into sub-packages to handle this configuration. I've been hesitant to push this change out to F20 though. fail2ban-0.9.1-1.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/FEDORA-2014-15988/fail2ban-0.9.1-1.fc20 Sorry, already migrated to F21. Have installed: fail2ban-firewalld-0.9.1-3.fc21.noarch fail2ban-server-0.9.1-3.fc21.noarch fail2ban-systemd-0.9.1-3.fc21.noarch This version works fine, no issues. fail2ban-0.9.2-1.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/fail2ban-0.9.2-1.fc20 Package fail2ban-0.9.2-1.fc20: * should fix your issue, * was pushed to the Fedora 20 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing fail2ban-0.9.2-1.fc20' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2015-8727/fail2ban-0.9.2-1.fc20 then log in and leave karma (feedback). This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '20'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed. |