Hi Meaulnes,
> Mar 19 17:30:02 vs fail2ban-server[26348]: 2020-03-19 17:30:02,434
> fail2ban.configreader [26348]: ERROR Found no accessible config
> files for 'filter.d/sshd-ddos' under /etc/fail2ban
My guess (from what I've just seen from another 5209R) is that some
config files are still
thank you Michael!
# systemctl status fail2ban
* fail2ban.service - Fail2Ban Service
Loaded: loaded (/usr/lib/systemd/system/fail2ban.service; enabled; vendor
preset: disabled)
Active: failed (Result: exit-code) since Thu 2020-03-19 17:30:02 CET; 11min
ago
Docs: man:fail2ban(1)
Hi Meaulnes,
> «Fail2ban is not running and could not be restarted. Please try to
> restart the service fail2ban manually.»
>
> does anyone encounter this, too?
>
> restarting fail2ban over the GUI doesn't change anything and I don't
> know to do it from the command line.
The command for that
hello all
since 07:30 CET Active Monitor publishes on all five servers running 5209R the
following message:
«Fail2ban is not running and could not be restarted. Please try to restart the
service fail2ban manually.»
does anyone encounter this, too?
restarting fail2ban over the GUI doesn't
