Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1696995 - fail2ban metapackage does not depend on fail2ban-systemd
Summary: fail2ban metapackage does not depend on fail2ban-systemd
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: fail2ban
Version: 29
Hardware: All
OS: Linux
unspecified
low
Target Milestone: ---
Assignee: Orion Poplawski
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-04-06 23:53 UTC by Mikel Pérez
Modified: 2019-04-14 22:52 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-04-14 22:52:20 UTC


Attachments (Terms of Use)

Description Mikel Pérez 2019-04-06 23:53:30 UTC
Description of problem:
the fail2ban package doesn't require fail2ban-systemd. I just sudo dnf install fail2ban and the systemd backend config wasn't installed.

Version-Release number of selected component (if applicable):
0.10.4-1.fc29

Additional info:
had I not read https://fedoraproject.org/wiki/Fail2ban_with_FirewallD I wouldn't even know it'd have problems logging to journald

Comment 1 Orion Poplawski 2019-04-14 22:52:20 UTC
That wiki page is somewhat out of date and misleading.  With the current version of the fail2ban-server package, the jails that require it are configured to use the journal and so the fail2ban-systemd package is not required.  Installing fail2ban-systemd breaks jails for services that do not log to the journal (such as apache) which is why it is not installed by default.


Note You need to log in before you can comment on or make changes to this bug.