Fail2ban wont start

(Yois) #8

@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
(Lorne Gaetz) #9

As far as I can tell on the system I have, the file


Is created when sysadmin is installed.

(Yois) #10

I have that version of sysadmin and the file does not exist

(Bob Reiber) #11

My server was on .55 when this started for what that’s worth.

(Yois) #12

Manually running

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'

This fixed it for me

Fail2ban won't start after update
(Simon Telephonics) #14

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.

(Yois) #15

I repro’d on 2107 too, so that’s not the issue.

[System 40] fail2ban should always be running
(Simon Telephonics) #16

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.

(Sandesh Prakash) #17

This issue is fixed in sysadmin, can you guys please try to run

fwconsole ma downloadinstall sysadmin --tag -f

from CLI and try to restart fail2ban.

Thank you.

(Lucas Ryan) #18

This seemed to fix it for me. Thank you.

(Bob Reiber) #19

I still get the same message about See “systemctl status fail2ban.service” and “journalctl -xe” for details.

(Yois) #20

It seems there was a typo. Try tag

(Bob Reiber) #21

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?

(Jeremy Lizzotte) #22

Has Fail2ban issue been resolved yet? I have FreePBX 15 PBXes that wont start Fail2Ban, even after upgrading sysadmin.

(Bob Reiber) #23

I dont think so. I just tried upgrading sys admin and the firewall and see no difference.

(Yois) #24

Did either of you try this:

(Jeremy Lizzotte) #25

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

(Yois) #26

(Jeremy Lizzotte) #27

Thanks. Unfortunately that did not work.