HELP! Firewall Intrusion Detection, fail2ban wont start


(United States) #1

HELP!
I’ve had to completely reinstall Freepbx twice for this same problem and trying to restore from backups didn’t work. So want to see if I can fix this without a third complete rebuild.

Freepbx system with two nics, internal lan and nat 1:1 via pfsense to voip.ms
I just replaced unmanged network with a Unifi Dream Machine Pro and managed switches. The network is up and working fine but the UDMP is causing problems with calls dropping on Freepbx. So natted around the UDMP to voip.ms and it was working.

I had the system working with a command line route of
route add -net 64.XX.XX.XXX netmask 255.255.255.255 gw 192.168.110.1 eth3

So went and tried to enter it into the /etc/sysconfig/network-scripts/ifcfg-eth0 file to make it persistent and when I restarted the network it indicated firewall rules corrupted and fail2ban wont start.

I’ve tried
fwconsole chown
fwconsole reload
service fail2ban restart
with the same problem.

Here are a couple of output. Any help on where to go from here would be appreciated.
I’ve tried everything I can find under google but nothing is fixing the problem.
Thanks

[[email protected] ~]# 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 Tue 2021-08-03 06:24:34 MDT; 4min 59s ago
Process: 6613 ExecStart=/usr/bin/fail2ban-client -x start (code=exited, status=255)
Process: 6611 ExecStartPre=/bin/mkdir -p /var/run/fail2ban (code=exited, status=0/SUCCESS)
Main PID: 14433 (code=killed, signal=TERM)

Aug 03 06:24:33 freepbx.sangoma.local systemd[1]: Failed to start Fail2Ban Service.
Aug 03 06:24:33 freepbx.sangoma.local systemd[1]: Unit fail2ban.service entered failed state.
Aug 03 06:24:33 freepbx.sangoma.local systemd[1]: fail2ban.service failed.
Aug 03 06:24:34 freepbx.sangoma.local systemd[1]: fail2ban.service holdoff time over, scheduling restart.
Aug 03 06:24:34 freepbx.sangoma.local systemd[1]: Stopped Fail2Ban Service.
Aug 03 06:24:34 freepbx.sangoma.local systemd[1]: start request repeated too quickly for fail2ban.service
Aug 03 06:24:34 freepbx.sangoma.local systemd[1]: Failed to start Fail2Ban Service.
Aug 03 06:24:34 freepbx.sangoma.local systemd[1]: Unit fail2ban.service entered failed state.
Aug 03 06:24:34 freepbx.sangoma.local systemd[1]: fail2ban.service failed.

[[email protected] ~]# journalctl -xe
Aug 03 06:52:05 freepbx.sangoma.local systemd[1]: Stopped Fail2Ban Service.
– Subject: Unit fail2ban.service has finished shutting down
– Defined-By: systemd
– Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel

– Unit fail2ban.service has finished shutting down.
Aug 03 06:52:05 freepbx.sangoma.local systemd[1]: Starting Fail2Ban Service…
– Subject: Unit fail2ban.service has begun start-up
– Defined-By: systemd
– Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel

– Unit fail2ban.service has begun starting up.
Aug 03 06:52:05 freepbx.sangoma.local fail2ban-client[12012]: ERROR Found no accessible config files for ‘filter.d/apache-api’ under /etc/fail2ban
Aug 03 06:52:05 freepbx.sangoma.local fail2ban-client[12012]: ERROR Unable to read the filter
Aug 03 06:52:05 freepbx.sangoma.local fail2ban-client[12012]: ERROR Errors in jail ‘apache-api’. Skipping…
Aug 03 06:52:05 freepbx.sangoma.local systemd[1]: fail2ban.service: control process exited, code=exited status=255
Aug 03 06:52:05 freepbx.sangoma.local systemd[1]: Failed to start Fail2Ban Service.
– Subject: Unit fail2ban.service has failed
– Defined-By: systemd
– Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel

– Unit fail2ban.service has failed.

– The result is failed.
Aug 03 06:52:05 freepbx.sangoma.local systemd[1]: Unit fail2ban.service entered failed state.
Aug 03 06:52:05 freepbx.sangoma.local systemd[1]: fail2ban.service failed.
Aug 03 06:52:05 freepbx.sangoma.local systemd[1]: fail2ban.service holdoff time over, scheduling restart.
Aug 03 06:52:05 freepbx.sangoma.local systemd[1]: Stopped Fail2Ban Service.
– Subject: Unit fail2ban.service has finished shutting down
– Defined-By: systemd
– Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel

– Unit fail2ban.service has finished shutting down.
Aug 03 06:52:05 freepbx.sangoma.local systemd[1]: start request repeated too quickly for fail2ban.service
Aug 03 06:52:05 freepbx.sangoma.local systemd[1]: Failed to start Fail2Ban Service.
– Subject: Unit fail2ban.service has failed
– Defined-By: systemd
– Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel

– Unit fail2ban.service has failed.

– The result is failed.
Aug 03 06:52:05 freepbx.sangoma.local systemd[1]: Unit fail2ban.service entered failed state.
Aug 03 06:52:05 freepbx.sangoma.local systemd[1]: fail2ban.service failed.
Aug 03 06:52:13 freepbx.sangoma.local crontab[12030]: (asterisk) LIST (asterisk)
Aug 03 06:52:13 freepbx.sangoma.local crontab[12032]: (asterisk) LIST (asterisk)
Aug 03 06:52:13 freepbx.sangoma.local crontab[12034]: (asterisk) LIST (asterisk)
Aug 03 06:52:13 freepbx.sangoma.local crontab[12036]: (asterisk) LIST (asterisk)
Aug 03 06:52:13 freepbx.sangoma.local crontab[12038]: (asterisk) LIST (asterisk)
Aug 03 06:52:13 freepbx.sangoma.local crontab[12040]: (asterisk) LIST (asterisk)
Aug 03 06:52:13 freepbx.sangoma.local crontab[12041]: (asterisk) REPLACE (asterisk)
Aug 03 06:52:13 freepbx.sangoma.local crontab[12043]: (asterisk) LIST (asterisk)
Aug 03 06:52:13 freepbx.sangoma.local crontab[12045]: (asterisk) LIST (asterisk)
Aug 03 06:52:13 freepbx.sangoma.local crontab[12046]: (asterisk) REPLACE (asterisk)
Aug 03 06:52:13 freepbx.sangoma.local crontab[12048]: (asterisk) LIST (asterisk)
Aug 03 06:52:14 freepbx.sangoma.local systemd[1]: Removed slice User Slice of asterisk.
– Subject: Unit user-995.slice has finished shutting down
– Defined-By: systemd
– Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel

– Unit user-995.slice has finished shutting down.
lines 2034-2094/2094 (END)


(system) closed #2

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