Solved: Fail2ban failing to start

[compsos]

If the logs or a systemctl restart fail2ban errors, look at the file /etc/fail2ban/jail.local and modify as below

Code Select Expand


[asterisk]
enabled  = true

#[asterisk-udp]
#enabled  = true

It seems there is no longer a asterisk-tcp or asterisk-udp definition only asterisk

Or copy  cp /opt/sark/etc/fail2ban/jail-jessie.local  /opt/sark/etc/fail2ban/jail-stretch.local
nano /opt/sark/etc/fail2ban/jail-stretch.local as above
relink /etc/fail2ban/jail.local to /opt/sark/etc/fail2ban/jail-stretch.local

[sysadmin]

Thank you, good input.   We are doing some stretch testing for V6 at the moment so I'll take a look at it.   

[compsos]

Still the same in V6
Change the /opt/sark/etc/fail2ban/jail-jessie.local file to

Code Select Expand

[asterisk]
enabled  = true
or better stilll make a new file jail-stretch.local
and relink /etc/fail2ban/jail.local to the new file
restart fail2ban

[sysadmin]

We are just about to test a new V6 point release with a fix in it for this.   Yes, we can link a file but the issue is the content.   It is different for wheezy, jessie and stretch.  Painful.   Moreover, we have to leave the file undisturbed because the jail.local file has to be available to the user to add her own changes.

I'll post once we've cut the release and done some testing 

[sysadmin]

This all seems to working OK now on Debian and Ubuntu.   Latest repo release is -47 at time of posting but -49 isn't far behind.  It's in testing now.