Fail2ban won’t start after update #2

[VoIPTek]

Sorry to spin this one up again, I got busy in other directions and still have no resolve after reading through the original thread as to why fail2ban won’t start (closed 1 day ago).

I visited the " [FREEPBX-22578] update fail2ban in SNG7 distro - Sangoma Issue Tracker" with no answer there.

Here is what I know now:

Running: fail2ban-fpbx-0.8.14-76.sng7.noarch
It still doesn’t start.

ALL OS Updates are current.
ALL FreePBX Updates are current ( ran fwconsole ma upgradeall to make sure ).

systemctl status fail2ban.service
● fail2ban.service - Fail2Ban Service
   Loaded: loaded (/usr/lib/systemd/system/fail2ban.service; disabled; vendor preset: disabled)
   Active: failed (Result: start-limit) since Tue 2021-08-17 17:23:18 UTC; 18s ago
  Process: 14516 ExecStart=/usr/bin/fail2ban-client -x start (code=exited, status=255)
  Process: 14514 ExecStartPre=/bin/mkdir -p /var/run/fail2ban (code=exited, status=0/SUCCESS)

Aug 17 17:23:18 bpbx.innovativeinternet.net systemd[1]: fail2ban.service: control process exited,         code=exited status=255
Aug 17 17:23:18  systemd[1]: Failed to start Fail2Ban Service.
Aug 17 17:23:18  systemd[1]: Unit fail2ban.service entered failed state.
Aug 17 17:23:18  systemd[1]: fail2ban.service failed.
Aug 17 17:23:18  systemd[1]: fail2ban.service holdoff time over,     scheduling restart.
Aug 17 17:23:18  systemd[1]: Stopped Fail2Ban Service.
Aug 17 17:23:18  systemd[1]: start request repeated too quickly for     fail2ban.service
Aug 17 17:23:18  systemd[1]: Failed to start Fail2Ban Service.
Aug 17 17:23:18  systemd[1]: Unit fail2ban.service en

Any suggestions would be appreciated, hackers are still out there trying to get in!

Thanks!

[yois]

Fail2ban wont start

Try Fail2ban-client -x start

[VoIPTek]

Same Thing, it won’t start…

fail2ban-client -x start
ERROR Found no accessible config files for ‘filter.d/zulu’ under /etc/fail2ban
ERROR Unable to read the filter
ERROR Errors in jail ‘zulu’. Skipping…

systemctl status fail2ban.service
● fail2ban.service - Fail2Ban Service
Loaded: loaded (/usr/lib/systemd/system/fail2ban.service; disabled; vendor preset: disabled)
Active: failed (Result: start-limit) since Tue 2021-08-17 17:23:18 UTC; 2h 40min ago
Process: 14516 ExecStart=/usr/bin/fail2ban-client -x start (code=exited, status=255)
Process: 14514 ExecStartPre=/bin/mkdir -p /var/run/fail2ban (code=exited, status=0/SUCCESS)

Aug 17 17:23:18 systemd[1]: fail2ban.service: control process exited, code=exited status=255
Aug 17 17:23:18 systemd[1]: Failed to start Fail2Ban Service.
Aug 17 17:23:18 systemd[1]: Unit fail2ban.service entered failed state.
Aug 17 17:23:18 systemd[1]: fail2ban.service failed.
Aug 17 17:23:18 systemd[1]: fail2ban.service holdoff time over, scheduling restart.
Aug 17 17:23:18 systemd[1]: Stopped Fail2Ban Service.
Aug 17 17:23:18 systemd[1]: start request repeated too quickly for fail2ban.service
Aug 17 17:23:18 systemd[1]: Failed to start Fail2Ban Service.
Aug 17 17:23:18 systemd[1]: Unit fail2ban.service entered failed state.
Aug 17 17:23:18 systemd[1]: fail2ban.service failed.

[yois]

Yes, but now we see that the Zulu jail is the problem. See the linked thread for solution.