@lgaetz - I finally was able to repro, and the issue seems to be coming from here:
ERROR Found no accessible config files for 'filter.d/apache-api' under /etc/fail2ban
ERROR Unable to read the filter
ERROR Errors in jail 'apache-api'. Skipping...
Fail2ban won't start after update
As far as I can tell on the system I have, the file
Is created when sysadmin 126.96.36.199 is installed.
I have that version of sysadmin and the file does not exist
My server was on .55 when this started for what that’s worth.
generates the necessary file. Checking the incron log shows that this was run but did not yield any resulting file. The hook is Zend encrypted so I can’t check the contents or tell why it’s not working.
@lgaetz - can you confirm that there’s a ticket for this?
Whoops \ Exception \ ErrorException (E_WARNING) Illegal string offset 'fail2ban_ban_time'
Did you guys
yum update recently? I just added a new Distro and started with
yum update which yielded this update:
then module upgrade and fail2ban (and everything else) are loading fine.
I mention it because the sangoma-pbx package does some work on apache.
I repro’d on 2107 too, so that’s not the issue.
[System 40] fail2ban should always be running
I spoke too soon. For some reason I thought it had started fine but then checked on it later and found the service had stopped with the same error as others reported. Ran the hook and solved.
Edit: I know what happened. I ran the
yum update and
fwconsole ma upgradeall and checked that services were running before I set up the firewall. After the updates I went through the out-of-box experience in the GUI where I configured the firewall. Once firewall was enabled, fail2ban stopped.
This issue is fixed in sysadmin 188.8.131.52, can you guys please try to run
fwconsole ma downloadinstall sysadmin --tag 184.108.40.206 -f
from CLI and try to restart fail2ban.
This seemed to fix it for me. Thank you.
I still get the same message about See “systemctl status fail2ban.service” and “journalctl -xe” for details.
It seems there was a typo. Try tag 220.127.116.11
Now I get a slightly different message that includes: .
To force a start use “systemctl reset-failed fail2ban.service” followed by “sysemctl start fail2ban.service” again.
Can’t tell what’s happening after doing the first command but after the second command I’m back to square 1
Do I need to reboot?
Has Fail2ban issue been resolved yet? I have FreePBX 15 PBXes that wont start Fail2Ban, even after upgrading sysadmin.
I dont think so. I just tried upgrading sys admin and the firewall and see no difference.
Did either of you try this:
Yes and that did not work, same error message. I looked through all of these recent threads before I left the question asking if it was resolved