Fail2Ban jails can not be activated: "ERROR:f2bmng:Failed to reload following jails due to errors in configuration"

Created:

2016-11-16 12:57:32 UTC

Modified:

2017-08-08 13:25:24 UTC

0

Was this article helpful?


Have more questions?

Submit a request

Fail2Ban jails can not be activated: "ERROR:f2bmng:Failed to reload following jails due to errors in configuration"

Applicable to:

  • Plesk 12.5 for Linux
  • Plesk 12.0 for Linux

Symptoms

Unable to switch ON the selected jails:

f2bmng failed: ERROR No file(s) found for glob /var/log/3proxy.log
ERROR Failed during configuration: Have not found any log file for 3proxy jail
ERROR:f2bmng:Command '['/usr/bin/fail2ban-client', 'reload', '3proxy']' returned non-zero exit status 255
ERROR:f2bmng:Failed to reload following jails due to errors in configuration: 3proxy

Other jails are also failing to get activated.

Cause

Jail rule contains default settings which are not matches with current system parameters: logpath, emails, etc. or there is no particular service installed which should be analyzed.

Resolution

Go to Home > Tools & Settings > IP Address Banning > Jails > JAIL_RULE > , click Change Settings and check that all parameters are set up properly for such jail.

Also, check that service which should be analyzed presents on a system.

Additional information:

Fail2ban works on the log files of the services and bans IPs that show the malicious signs -- too many password failures, seeking for exploits, etc.

If the service is not running and the corresponding log file is not present on the server, then it is not possible to enable the corresponding jail. The jail 3proxy is failing while trying to activate because the log file mentioned in the same jail (/var/log/3proxy.log) doesn't exist on the server. You can check the jail settings by clicking on it. The same message is showing as error while activating the jail with nonexisting error log file:

Unable to switch on the selected jails: f2bmng failed: ERROR No file(s) found for glob /var/log/3proxy.log
ERROR Failed during configuration: Have not found any log file for 3proxy jail

Other jails with non-existing log files are also failing to get activated.

Similarly the jails with the log files existing on the server are getting enabled fine.

Have more questions? Submit a request
Please sign in to leave a comment.