fail2ban like stoped but running after yum update
Posted: Tue Feb 11, 2020 12:04 pm
After yum update, the fail2ban was updated and it appears like stoped in the web admin (server section).
The probem is that /usr/local/vesta/bin/v-list-sys-services can't detect fail2ban procces fine, because the old proccess was named "fail2ban-service", and after the update the new name of procces is "f2b/server".
Is it possible to patch the /usr/local/vesta/bin/v-list-sys-services to detect the new name?.
This is the output in the updated server (not working):
And this before update (working):
Thank you
****
Updated;
It works fine if I change in line 273 in the /usr/local/vesta/bin/v-list-sys-services
from:
to:
But ... It is correct?
The probem is that /usr/local/vesta/bin/v-list-sys-services can't detect fail2ban procces fine, because the old proccess was named "fail2ban-service", and after the update the new name of procces is "f2b/server".
Is it possible to patch the /usr/local/vesta/bin/v-list-sys-services to detect the new name?.
This is the output in the updated server (not working):
And this before update (working):
Thank you
****
Updated;
It works fine if I change in line 273 in the /usr/local/vesta/bin/v-list-sys-services
from:
Code: Select all
# Checking FIREWALL Fail2ban extention
if [ ! -z "$FIREWALL_EXTENSION" ]; then
get_srv_state $FIREWALL_EXTENSION fail2ban-server script
data="$data\nNAME='$FIREWALL_EXTENSION' SYSTEM='brute-force monitor'"
data="$data STATE='$state' CPU='$cpu' MEM='$mem' RTIME='$rtime'"
fi
Code: Select all
# Checking FIREWALL Fail2ban extention
if [ ! -z "$FIREWALL_EXTENSION" ]; then
get_srv_state $FIREWALL_EXTENSION f2b/server script
data="$data\nNAME='$FIREWALL_EXTENSION' SYSTEM='brute-force monitor'"
data="$data STATE='$state' CPU='$cpu' MEM='$mem' RTIME='$rtime'"
fi