• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion

Issue Error activating Fail2Ban

Goodnight:

I am trying to activate Fail2Ban from the Plesk Panel, but I always get this error message:

Error: Failed to save settings:f2bmng failed: Job for fail2ban.service failed because the control process exited with error code. See "systemctl status fail2ban.service" and "journalctl -xe" for details.
ERROR:f2bmng:Failed to start fail2ban service

Captura_de_pantalla_6.png


Command #service fail2ban status

[root@mydomain ~]# service fail2ban status
Redirecting to /bin/systemctl status fail2ban.service
● fail2ban.service - Fail2ban Service
Loaded: loaded (/etc/systemd/system/fail2ban.service; enabled; vendor preset: disabled)
Active: failed (Result: start-limit) since Tue 2016-11-08 00:22:32 CET; 6min ago
Process: 3258 ExecStart=/usr/bin/fail2ban-client -x start (code=exited, status=255)

Nov 08 00:22:32 mydomain.com systemd[1]: fail2ban.service: control process exited, code=exited status=255
Nov 08 00:22:32 mydomain.com systemd[1]: Failed to start Fail2ban Service.
Nov 08 00:22:32 mydomain.com systemd[1]: Unit fail2ban.service entered failed state.
Nov 08 00:22:32 mydomain.com systemd[1]: fail2ban.service failed.
Nov 08 00:22:32 mydomain.com systemd[1]: fail2ban.service holdoff time over, scheduling restart.
Nov 08 00:22:32 mydomain.com systemd[1]: start request repeated too quickly for fail2ban.service
Nov 08 00:22:32 mydomain.com systemd[1]: Failed to start Fail2ban Service.
Nov 08 00:22:32 mydomain.com systemd[1]: Unit fail2ban.service entered failed state.
Nov 08 00:22:32 mydomain.com systemd[1]: fail2ban.service failed.


Where the problem lies?

A greeting and thanks in advance.
 
Hi jorgemartincasasola,

pls. see as well depending log - entries from "/var/log/fail2ban.log" and don't forget the second suggestion from your error - message for investigations reasons:
See "systemctl status fail2ban.service" and "journalctl -xe" for details.

In addition, it would really help if you would provide informations about:
  • Your operating system
  • Your current Plesk version ( incl. MU )


A common reason why Fail2Ban can't start is the absent directory "/var/run/fail2ban". Pls. make sure that the directory exists and that it has the correct permissions ( 0755 / user: root / group: root ).
Code:
COMMAND TO USE OVER THE COMMAND LINE - logged in as user "root":

mkdir -p /var/run/fail2ban

Another common reason might be the missing file "/var/log/fail2ban.log". Pls. consider to create it manually with for example:
Code:
COMMAND TO USE OVER THE COMMAND LINE - logged in as user "root":

touch /var/log/fail2ban.log
 
Back
Top