From /etc/fail2ban/jail.conf: [pam-generic] # pam-generic filter can be customized to monitor specific subset of 'tty's banaction = iptables-allports logpath = /var/log/auth.log But /var/log/auth.log doesn't exist on my system and I don't see any evidence that it should. I believe fail2ban should be looking at /var/log/secure. I just discovered this bug, and the fact that because of this bug my system hasn't been protected by fail2ban since I installed the most recent fail2ban update on May 29, since fail2ban crashes when it encounters a configured log file that it can't open. That's presumably true for every other Fedora 20 user of fail2ban who installed this update. Wow, that's bad.
Minor correction... pam-generic is disabled by default, so this is only going to cause fail2ban to crash for people who have enabled it.
The logpath for the xinetd-fail jail is also wrong -- /var/log/daemon.log, which also does not exist on Fedora.
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
This is fixed in 0.9.1-1.fc20: [pam-generic] # pam-generic filter can be customized to monitor specific subset of 'tty's banaction = iptables-allports logpath = %(syslog_authpriv)s
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
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.