Dear maintainers,
I think it is a very important bug to fix because a lot of servers depend on this for core security. Further more after starting it does not show an error message. So user is left with impression that service runs. Only manual verification like `service status fail2ban` or a monitoring tool will make it clear that service stopped working (or never gets started). It scared me abit that this one has not been fixed.
In my case simply adding
I think it is a very important bug to fix because a lot of servers depend on this for core security. Further more after starting it does not show an error message. So user is left with impression that service runs. Only manual verification like `service status fail2ban` or a monitoring tool will make it clear that service stopped working (or never gets started). It scared me abit that this one has not been fixed.
In my case simply adding
backend = systemd
to my jail.local helped.
Probably best way to fix it is adding
[DEFAULT]
backend = systemd
[DEFAULT]
backend = systemd
at the top of
/etc/fail2ban/jail.d/defaults-debian.conf
although in /etc/fail2ban/jail.conf might be a cleaner solution.
/etc/fail2ban/jail.d/defaults-debian.conf
although in /etc/fail2ban/jail.conf might be a cleaner solution.
Restart of the service after the update would be needed of course.
