Since today fail2ban not working

[Azurel]

Not sure, maybe latest yum or plesk-update stopped working fail2ban in Plesk with CentOS 6.7 (Final)? In plesk ip banning is "off" and I can't set it "on".

I get this email today

/etc/cron.daily/logrotate:

ERROR Failed to access socket path: /var/run/fail2ban/fail2ban.sock. Is fail2ban running?

I checked it in putty:

# fail2ban-client status
ERROR Failed to access socket path: /var/run/fail2ban/fail2ban.sock. Is fail2ban running?

path "/var/run/fail2ban" is empty

Try to start:

# /etc/init.d/fail2ban start
Starting fail2ban: WARNING 'syslogsocket' not defined in 'Definition'. Using default one: 'auto'
WARNING 'dbfile' not defined in 'Definition'. Using default one: '/var/lib/fail2ban/fail2ban.sqlite3'
WARNING 'dbpurgeage' not defined in 'Definition'. Using default one: 86400
ERROR Found no accessible config files for 'filter.d/ssh-iptables' under /etc/fail2ban
ERROR No section: 'Definition'
ERROR No section: 'Definition'
ERROR Unable to read the filter
ERROR Errors in jail 'ssh-iptables'. Skipping...
[FAILED]

Can anyone help here? I use Plesk 12.0.18 Update #70(today), not working since #68

Restart the server not help here.


EDIT: Same problem found here: https://talk.plesk.com/threads/plesk-12-0-18-update-68-and-fail2ban-0-9-3-problem.335183/