Every time fail2ban starts up it complains, "ERROR NOK: ("File option must be 'head' or 'tail'",)". This is because the logpath setting of the php-url-fopen section of jail.conf lists two log files separated by whitespace. Alas, fail2ban requires multiple log paths to be separated by newline + whitespace rather than just whitespace.
Reported upstream
fail2ban-0.9.1-1.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/fail2ban-0.9.1-1.fc20
Package fail2ban-0.9.1-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.1-1.fc20' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2014-15988/fail2ban-0.9.1-1.fc20 then log in and leave karma (feedback).
Um, you need to fix this in F21 too?
Of course: https://admin.fedoraproject.org/updates/FEDORA-2014-13919/fail2ban-0.9.1-1.fc21 I'm just one of these weird folks who when a bug is filed against a specific release, only notes the bug in the update for that release. I find it too distracting otherwise.
Perhaps I was not clear. I have fail2ban-0.9.1-1.fc21. It is not fixed in that package: jik2:~/build/scripts!1041$ rpm2cpio /var/cache/yum/x86_64/21/fedora/packages/fail2ban-server-0.9.1-1.fc21.noarch.rpm | cpio --extract --to-stdout ./etc/fail2ban/jail.conf | egrep 'php-url-fopen|logpath' ... [php-url-fopen] logpath = %(nginx_access_log)s %(apache_access_log)s
Apparently I was completely asleep when last addressing this.
For f21 this should be fixed in https://admin.fedoraproject.org/updates/fail2ban-0.9.1-2.fc21
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.