Facebook
Twitter- Server operating system version
- Debian 12
- Plesk version and microupdate number
- 18.0.70 #1
Hi,
when creating a new fail2ban jail in fail2ban (v1.1.0) through the Plesk UI (v18.0.70#1), the fail2ban service is restarted, clearing the banned IPs and forcing to restore all the previous bans. This causes a spike in CPU usage until all the IPs are banned again.
Is that the desired behaviour when creating new jails? Because it's a problem when you have to create a new "emergency jail" when there's a ddos attack to a website.
In previous versions of Plesk+Fail2ban (18.0.44#3 + v0.11.2) , when you created a custom new jail the previous jails didn't change, and the service wasn't restarted.
when creating a new fail2ban jail in fail2ban (v1.1.0) through the Plesk UI (v18.0.70#1), the fail2ban service is restarted, clearing the banned IPs and forcing to restore all the previous bans. This causes a spike in CPU usage until all the IPs are banned again.
Is that the desired behaviour when creating new jails? Because it's a problem when you have to create a new "emergency jail" when there's a ddos attack to a website.
In previous versions of Plesk+Fail2ban (18.0.44#3 + v0.11.2) , when you created a custom new jail the previous jails didn't change, and the service wasn't restarted.
