Fail2ban not starting up after the latest vulnerability update

Re: FreePBX 14.0.16.11 Current Asterisk Version: 13.38.3
Current version: fail2ban v0.11.1, fail2ban-firewalld v0.11.1, fail2ban-sendmail v0.11.1, fail2ban-server v0.11.1

After updated my server for security threats, the Fail2ban service refused to start. The update has broken something, now I’m feeling really vulnerable. I don’t think the fail2ban server was updated specifically. Something else is preventing the service from starting. How do I fix this? Please advise,

[[email protected] ~]# additional information to troubleshoot the issue:
systemctl status fail2ban
● fail2ban.service - Fail2Ban Service
Loaded: loaded (/usr/lib/systemd/system/fail2ban.service; disabled; vendor preset: disabled)
Active: failed (Result: start-limit) since Sat 2021-09-18 10:21:45 EDT; 33min ago
Process: 6829 ExecStart=/usr/bin/fail2ban-client -x start (code=exited, status=255)
Process: 6827 ExecStartPre=/bin/mkdir -p /var/run/fail2ban (code=exited, status=0/SUCCESS)

Sep 18 10:21:45 freepbx.yius.local systemd[1]: fail2ban.service: control process exited, code=exited status=255
Sep 18 10:21:45 freepbx.yius.local systemd[1]: Failed to start Fail2Ban Service.
Sep 18 10:21:45 freepbx.yius.local systemd[1]: Unit fail2ban.service entered failed state.
Sep 18 10:21:45 freepbx.yius.local systemd[1]: fail2ban.service failed.
Sep 18 10:21:45 freepbx.yius.local systemd[1]: fail2ban.service holdoff time over, scheduling restart.
Sep 18 10:21:45 freepbx.yius.local systemd[1]: Stopped Fail2Ban Service.
Sep 18 10:21:45 freepbx.yius.local systemd[1]: start request repeated too quickly for fail2ban.service
Sep 18 10:21:45 freepbx.yius.local systemd[1]: Failed to start Fail2Ban Service.
Sep 18 10:21:45 freepbx.yius.local systemd[1]: Unit fail2ban.service entered failed state.
Sep 18 10:21:45 freepbx.yius.local systemd[1]: fail2ban.service failed.

from a shell, as root, run /usr/bin/fail2ban-client -x start and post the result and the associated fail2ban.log file

[[email protected] ~]# /usr/bin/fail2ban-client -x start
ERROR No file(s) found for glob /var/log/asterisk/zulu_out.log
ERROR Failed during configuration: Have not found any log file for zulu jail

Do you use zulu ?

Zulu is enabled but no license…

From a shell

touch /var/log/asterisk/zulu_out.log

and try over

[[email protected] ~]# fwconsole start fail2ban
Running FreePBX startup…
Taking too long? Customize the chown command, See http://wiki.freepbx.org/display/FOP/FreePBX+Chown+Conf
Setting Permissions…
Setting base permissions…Done in 14 seconds
Setting specific permissions…
59034 [============================]
Finished setting permissions
Unable to run Pre-Asterisk hooks, because Asterisk is already running on PID 3159 and has been running for 54 minutes, 6 seconds

No

/usr/bin/fail2ban-client -x start

Wait…
I went to the sysadmin panel and checked again. It’s started

Perhaps file a bug?

No, the fail2ban hs started:grinning:

Thank you for the quick reply…all systems are green. I’m back to normal. thank you so much.

perhaps only until the next logrotate, filing a bug is for the communities benefit.

Great…thanks

This topic was automatically closed 31 days after the last reply. New replies are no longer allowed.