Package: fail2ban
Version: 0.9.6-2
Severity: normal
Dear Maintainer,
* What led up to the situation?
I upgraded my system from Jessie to Stretch.
#767119 enables ssh jail in /etc/fail2ban/jail.d/defaults-debian.conf
* What exactly did you do (or not do) that was effective (or
ineffective)?
Disabling the SSH jail in /etc/fail2ban/jail.d/defaults-debian.conf
fixed the problem.
* What was the outcome of this action?
fail2ban does not start. Here is an example. The same happened when
I try to start it manually:
Aug 31 01:15:52 vbox systemd[1]: apt-daily-upgrade.timer: Adding 25min
818.405ms random time.
Aug 31 01:15:52 vbox systemd[1]: fail2ban.service: Control process
exited, code=exited status=255
Aug 31 01:15:52 vbox systemd[1]: Failed to start Fail2Ban Service.
Aug 31 01:15:52 vbox systemd[1]: fail2ban.service: Unit entered failed
state.
Aug 31 01:15:52 vbox systemd[1]: fail2ban.service: Failed with result
'exit-code'.
Aug 31 01:15:52 vbox systemd[1]: fail2ban.service: Service hold-off time
over, scheduling restart.
Aug 31 01:15:52 vbox systemd[1]: Stopped Fail2Ban Service.
Aug 31 01:15:52 vbox systemd[1]: Starting Fail2Ban Service...
Aug 31 01:15:52 vbox fail2ban-client[1464]: WARNING 'filter' not defined
in 'sshd'. Using default one: ''
Aug 31 01:15:52 vbox fail2ban-client[1464]: WARNING No filter set for
jail sshd
Aug 31 01:15:52 vbox fail2ban-client[1464]: WARNING 'filter' not defined
in 'sshd'. Using default one: ''
Aug 31 01:15:52 vbox fail2ban-client[1464]: ERROR Failed during
configuration: Bad value substitution: option 'action' in section 'sshd'
contains an interpolation key 'port' which is not a valid option name.
Raw value: '%(action_)s'
Aug 31 01:15:52 vbox systemd[1]: fail2ban.service: Control process
exited, code=exited status=255
Aug 31 01:15:52 vbox systemd[1]: Failed to start Fail2Ban Service.
Aug 31 01:15:52 vbox systemd[1]: fail2ban.service: Unit entered failed
state.
Aug 31 01:15:52 vbox systemd[1]: fail2ban.service: Failed with result
'exit-code'.
* What outcome did you expect instead?
fail2ban should start even if the SSH jail is enabled in
/etc/fail2ban/jail.d/defaults-debian.conf or this option should be
disabled on systems where this problem occurs.
-- System Information:
Debian Release: 9.1
APT prefers stable
APT policy: (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 4.9.0-3-amd64 (SMP w/1 CPU core)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8),
LANGUAGE=en_GB.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:
ii bsd-mailx [mailx] 8.1.2-0.20160123cvs-4
pn monit <none>
ii rsyslog [system-log-daemon] 8.24.0-1
-- Configuration Files:
/etc/fail2ban/action.d/blocklist_de.conf changed [not included]
/etc/fail2ban/jail.conf changed [not included]
/etc/fail2ban/jail.d/defaults-debian.conf changed [not included]
-- no debconf information
