jean pierre Lerbscher

@Hi drybjec, I always have this log when using debops.fail2ban role with a custom playbooks and become: yes option on the playbook level like this. Do you have an idea?...

Yes it's the same error. I think the origi of the error is related to the fact that the file fail2ban-ssh in /proc/net/xt_recent directory is not found and the command...

When i restart fail2ban by hand, i have the same errors (Fail2ban v0.8.13).

lsmod | grep recent xt_recent 17246 0 x_tables 27111 3 xt_recent,ip_tables,iptable_filter

The host is an AWS/EC2 server

When i re install fail2ban from scratch it works perfectly with default configuration. sudo apt-get purge fail2ban sudo apt-get install fail2ban

Thanks for the response. These files contains fail2ban_jails and fail2ban_filters declarations which are, sometimes, specific for each component.

[WARNING] After scanning for Entities, no annotated Entities were found. on java 8 jpa project (jpa entitiy jar files are in the classpath). com.edugility:jpa-maven-plugin:jar:3-20140611.160749-5 and dependencies [DEBUG] net.sf.scannotation:scannotation:jar:1.0.2:compile [DEBUG] org.javassist:javassist:jar:3.18.2-GA:compile...

I'm sorry for the late response. I open an issue which is more a question https://github.com/ljnelson/jpa-maven-plugin/issues/11