Package: fail2ban
Version: 0.9.6-2
Severity: normal
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
I upgraded my distritution from debian jessie to stretch.
Under jessie i didnt had this problem.
* What exactly did you do (or not do) that was effective (or
ineffective)?
I have a custom filter with approx. 1300 entries for blocking specific
file types
which are used by cryptolockers. I use this filter to protect my samba
shares.
After the upgrade, fail2ban failed to start with an timeout error.
-- System Information:
Debian Release: 9.1
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 4.9.0-3-amd64 (SMP w/2 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8),
LANGUAGE=de_DE.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.48
ii lsb-base 9.20161125
ii python3 3.5.3-1
Versions of packages fail2ban recommends:
ii iptables 1.6.0+snapshot20161117-6
ii python 2.7.13-2
ii python3-pyinotify 0.9.6-1
ii python3-systemd 233-1
ii whois 5.2.15
Versions of packages fail2ban suggests:
pn mailx <none>
pn monit <none>
ii rsyslog [system-log-daemon] 8.24.0-1
-- no debconf information
