Package: fail2ban Version: 0.9.2-1 Severity: normal Dear Maintainer,
I have the following in my jail.local to re-ban things which were banned in the last 10 days on startup: bantime = -1 findtime = 864000 This makes fail2ban take quite a long time to start as it re-scrapes the logs. Because of this long start-up, systemd thinks fail2ban failed to start and tries to restart it. This results in many fail2ban processes. I had to add the following to /etc/systemd/system/multi-user.target.wants/fail2ban.service: TimeoutStartSec=900 For systems with small log files this may not be necessary but tracking this down took some time. It is worthwhile adding this to the fail2ban.service and maybe adding a comment to jail.conf -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (1000, 'testing'), (750, 'testing'), (50, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.0.4-x86_64-linode57 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages fail2ban depends on: ii init-system-helpers 1.23 ii lsb-base 4.1+Debian13+nmu1 ii python3 3.4.2-2 pn python3:any <none> Versions of packages fail2ban recommends: ii iptables 1.4.21-2+b1 ii python 2.7.9-1 ii python3-pyinotify 0.9.5-1 ii python3-systemd 215-18 ii whois 5.2.8 Versions of packages fail2ban suggests: ii mailutils [mailx] 1:2.99.98-2 pn monit <none> ii rsyslog [system-log-daemon] 8.9.0-3 -- Configuration Files: /etc/fail2ban/filter.d/ignorecommands/apache-fakegooglebot changed [not included] /etc/fail2ban/paths-debian.conf changed [not included] -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
