Problems with Fail2Ban and sys firewall

aaP_sbudennogo

I saw the post https://www.aapanel.com/forum/d/4157-sys-firewall-country-by-country-blocking-doesnt-work/20
and checked systemctl status fail2ban.. an error occurs:

fail2ban.service - Fail2Ban Service
Loaded: loaded (/lib/systemd/system/fail2ban.service; disabled; vendor preset: enabled)
Active: inactive (dead)
Docs: man:fail2ban(1)

Jan 17 16:29:12 xxx systemd[1]: /lib/systemd/system/fail2ban.service:12: PIDFile= references path below legacy dir
Jan 17 16:29:53 xxx systemd[1]: /lib/systemd/system/fail2ban.service:12: PIDFile= references path below legacy dir
Jan 17 16:31:31 xxx systemd[1]: /lib/systemd/system/fail2ban.service:12: PIDFile= references path below legacy dir
Jan 17 16:33:14 xxx systemd[1]: /lib/systemd/system/fail2ban.service:12: PIDFile= references path below legacy dir
Jan 17 16:37:59 xxx systemd[1]: /lib/systemd/system/fail2ban.service:12: PIDFile= references path below legacy dir
lines 1-10/10 (END)

unistalled and installed again .. everything is fine until I reboot the system
does anyone have any ideas why that is?

also in sys firewall trying to block india, iraq, iran an error occurs <<choose the correct country from the list>> but i already chose
also unistalled and installed again, but nothing works
please help...so many connection from each single IP's addresses

aaPanel_Jose

aaP_sbudennogo
can you tell me your linux distribution?

aaP_sbudennogo

debian 10

it's seem to working, in a /var/mail/root i see some IP,s blocking, but if i check the status now is

fail2ban.service - Fail2Ban Service
Loaded: loaded (/lib/systemd/system/fail2ban.service; disabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Mon 2022-01-17 19:11:46 CET; 12h ago
Docs: man:fail2ban(1)
Process: 4532 ExecStartPre=/bin/mkdir -p /var/run/fail2ban (code=exited, status=0/SUCCESS)
Process: 4533 ExecStart=/usr/bin/fail2ban-server -xf start (code=exited, status=255/EXCEPTION)
Main PID: 4533 (code=exited, status=255/EXCEPTION)

Warning: Journal has been rotated since unit was started. Log output is incomplete or unavailable.

aaP_sbudennogo

you guys can close this one
If someone have the same prob here is answer, debian 10
first run this command

fail2ban-client -x stop
then

service fail2ban start
then you can check status by

systemctl status fail2ban

and evering should be fine
good luck

aaPanel_thisyear

aaP_sbudennogo Hello, has the problem been solved?

aaP_sbudennogo

aaPanel_thisyear
Hi,
Yes
this is strange, but if you do the commands that I gave above, then everything works, at least on debian 10