Resolved Onyx - Fail2Ban Error

[futureweb]

Hello,
trying to activate Fail2Ban on a fresh installed Onyx Plesk without any Hostings created yet.
Since there are no HTTP, ... Logs - Plesk fails to activate Fail2Ban Jails with a Hard Error ...

Die ausgewählten Jails können nicht eingeschaltet werden: f2bmng failed: ERROR No file(s) found for glob /var/www/vhosts/system/*/logs/error_log
ERROR NOK: ('plesk-apache',)
ERROR No file(s) found for glob /var/www/vhosts/system/*/logs/*access*log
ERROR NOK: ('plesk-apache-badbot',)
ERROR NOK: ('plesk-courierimap',)
ERROR NOK: ('plesk-horde',)
ERROR No file(s) found for glob /var/log/modsec_audit.log
ERROR Failed during configuration: Have not found any log file for plesk-modsecurity jail
ERROR:f2bmng:Command '['/usr/bin/fail2ban-client', 'reload', 'plesk-modsecurity']' returned non-zero exit status 255
ERROR NOK: ('plesk-panel',)
ERROR NOK: ('plesk-postfix',)
ERROR NOK: ('plesk-proftpd',)
ERROR NOK: ('plesk-roundcube',)
ERROR No file(s) found for glob /var/www/vhosts/system/*/logs/*access*log
ERROR NOK: ('plesk-wordpress',)
ERROR NOK: ('recidive',)
ERROR NOK: ('ssh',)
ERROR:f2bmng:Failed to reload following jails due to errors in configuration: plesk-modsecurity.

Die ausgewählten Jails können nicht eingeschaltet werden: f2bmng failed: ERROR NOK: ('plesk-courierimap',)
ERROR NOK: ('plesk-horde',)
ERROR No file(s) found for glob /var/log/modsec_audit.log
ERROR Failed during configuration: Have not found any log file for plesk-modsecurity jail
ERROR:f2bmng:Command '['/usr/bin/fail2ban-client', 'reload', 'plesk-modsecurity']' returned non-zero exit status 255
ERROR NOK: ('plesk-panel',)
ERROR NOK: ('plesk-postfix',)
ERROR NOK: ('plesk-proftpd',)
ERROR NOK: ('plesk-roundcube',)
ERROR No file(s) found for glob /var/www/vhosts/system/*/logs/*access*log
ERROR NOK: ('plesk-wordpress',)
ERROR NOK: ('recidive',)
ERROR NOK: ('ssh',)
ERROR:f2bmng:Failed to reload following jails due to errors in configuration: plesk-modsecurity.

Andreas Schnederle-Wagner

 

[Bitpalast]

If there are no log files, fail2ban does not have anything to do, hence no need to start it. This behavior is by design of fail2ban, it cannot be avoided. You must deactivate the jails that do not have target locations, e.g. webspace/logs.

 

[futureweb]

Hi,
it's clear WHY this happens ... but it complicates our workflow of deploying Plesk Servers for our Customers massively ... As we are a Hosting Provider we sell fully configured Plesk Servers to our Customers ... As those are new/empty Servers - we never can activate Fail2Ban for our Customers as there are no Logs yet ...
So we always have to check back later when Customer already created some Hostings on the Server to activate it for them ...
You see the Problem ... ?

 

[UFHH01]

Hi futureweb,

hint: Use an "Event handler", to activate specific Fail2Ban - jails, after a physical hosting has been created on the server.