Package: fail2ban Version: 0.9.6-1 Severity: important After updating three servers from Jessie to Stretch all of them failed to start fail2ban.
When running it by hand I've got: # /usr/bin/fail2ban-client -x start ERROR Failed during configuration: While reading from '/etc/fail2ban/jail.local' [line 119]: option 'port' in section 'pam-generic' already exists Commenting out that port definition did the trick, although I don't know if that's the correct thing to do. -- System Information: Debian Release: 9.0 APT prefers unstable APT policy: (990, 'unstable'), (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'buildd-unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental-debug') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.9.0-2-amd64 (SMP w/2 CPU cores) Locale: LANG=es_AR.UTF-8, LC_CTYPE=es_AR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Init: systemd (via /run/systemd/system) Versions of packages fail2ban depends on: ii init-system-helpers 1.47 ii lsb-base 9.20161125 pn python3:any <none> 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: ii mailutils [mailx] 1:3.1.1-1 pn monit <none> ii rsyslog [system-log-daemon] 8.24.0-1 -- no debconf information
