Package: fail2ban
X-Debbugs-Cc: guido.vanbra...@outlook.com
Version: 1.0.2-2
Severity: important
Dear Maintainer,
* What led up to the situation? Installing fail2ban on Debian 12
* What exactly did you do (or not do) that was effective (or
ineffective)?
* What was the outcome of this action? Fail2ban fails to start
* What outcome did you expect instead? Fail2ban just starting without
needing to
-- System Information:
Debian Release: 12.4
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 6.1.0-16-cloud-amd64 (SMP w/8 CPU threads; PREEMPT)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages fail2ban depends on:
ii python3 3.11.2-1+b1
Versions of packages fail2ban recommends:
ii iptables 1.8.9-2
ii python3-pyinotify 0.9.6-2
ii python3-systemd 235-1+b2
ii whois 5.5.17
Versions of packages fail2ban suggests:
Versions of packages fail2ban suggests:
pn mailx <none>
pn monit <none>
pn sqlite3 <none>
pn system-log-daemon <none>
-- Configuration Files:
/etc/fail2ban/jail.conf changed:
[INCLUDES]
before = paths-debian.conf
[DEFAULT]
ignorecommand =
bantime = 10m
findtime = 10m
maxretry = 5
maxmatches = %(maxretry)s
backend = systemd
