Red Hat Bugzilla – Bug 1269226
fail2ban does not work out of box in a minimal Fedora 22 install
Last modified: 2016-07-19 14:07:23 EDT
Fedora does not install a traditional syslog daemon by default for some time now.
For things work, fail2ban needs to depend on fail2ban-systemd or on a syslog implementation that provides /var/log/secure et al. We have a virtual package 'syslog' for that.
RHEL 7 still uses rsyslogd by default and a 'Requires: syslog' for EPEL 7 is not urgent.
For Fedora I do not know. fail2ban stopped depending on fail2ban-systemd recently because some program did log to the journal. But adding 'Requires: syslog' may be overkill for folks that would be happy using the journal...
The use case is a simple sshd jail.
I'm not sure there is a good solution to this situation. Perhaps the default for those jails that work with the journal could be set to the journal, but not others.
The offending program 'jaila' logs where? journald captures syslog messages too (as well as all stout/stderr from services).
About syslog virtual package, I realise now systemd also provides it...
I really don't understand what you mean by "offending program 'jaila'".
That seems a bit strange that systemd provides syslog. But then again, only one thing seems to require it at this point.
Filed https://github.com/fail2ban/fail2ban/pull/1213 as an idea to fix this.
I was referring to
Doh, sorry, it is a typo.
But anyway it should work for any daemon that logs to journald directly (libsystemd's sd_journal_*() family), to glibc's syslog facility or to stdout/stderr if the service does not have StandardOutput=/StandardError= configured to null.
journald is a syslog implementation after all. Just not a "traditional" one.
I remembered this bug we should be aware of:
If the lack of space suffixes can affect fail2ban regexes I have no idea.
(In reply to Marcos Mello from comment #6)
> I was referring to
The problem was that apache httpd in particular (which is a large part of what people use fail2ban to match on) does not log to the journal. People expected that simply enabling the jails they wanted would activate them, but this silently failed since they were monitoring the journal and nothing was logged there.
fail2ban-0.9.4-2.fc22 has been submitted as an update to Fedora 22. https://bodhi.fedoraproject.org/updates/FEDORA-2016-10b5fefb0d
fail2ban-0.9.4-2.fc22 has been pushed to the Fedora 22 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2016-10b5fefb0d
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 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
Thank you for reporting this bug and we are sorry it could not be fixed.