Package: fail2ban
Version: 1.1.0-4
Severity: important

        I started getting this recently in my logs with fail2ban
refusing to start entirely:
---
2024-07-17 02:33:11,197 fail2ban.server         [469516]: INFO    
--------------------------------------------------
2024-07-17 02:33:11,197 fail2ban.server         [469516]: INFO    Starting 
Fail2ban v1.1.0
2024-07-17 02:33:11,197 fail2ban.observer       [469516]: INFO    Observer 
start...
2024-07-17 02:33:11,201 fail2ban.database       [469516]: INFO    Connected to 
fail2ban persistent database '/var/lib/fail2ban/fail2ban.sqlite3'
2024-07-17 02:33:11,201 fail2ban.jail           [469516]: INFO    Creating new 
jail 'sshd'
2024-07-17 02:33:11,202 fail2ban.jail           [469516]: ERROR   Backend 
'systemd' failed to initialize due to No module named 'distutils'
2024-07-17 02:33:11,202 fail2ban.jail           [469516]: ERROR   Failed to 
initialize any backend for Jail 'sshd'
2024-07-17 02:33:11,202 fail2ban.transmitter    [469516]: ERROR   Command 
['server-stream', [['set', 'syslogsocket', 'auto'],<long line snipped>
2024-07-17 02:33:11,202 fail2ban                [469516]: ERROR   NOK: ("Failed 
to initialize any backend for Jail 'sshd'",)
2024-07-17 02:33:11,202 fail2ban.server         [469516]: INFO    Shutdown in 
progress...
2024-07-17 02:33:11,202 fail2ban.observer       [469516]: INFO    Observer stop 
... try to end queue 5 seconds
2024-07-17 02:33:11,222 fail2ban.observer       [469516]: INFO    Observer 
stopped, 0 events remaining.
2024-07-17 02:33:11,262 fail2ban.server         [469516]: INFO    Stopping all 
jails
2024-07-17 02:33:11,263 fail2ban.database       [469516]: INFO    Connection to 
database closed.
2024-07-17 02:33:11,463 fail2ban.server         [469516]: INFO    Exiting 
Fail2ban
---

Thankfully, I happened to run across this report from a Fedora
user:
---
https://github.com/fail2ban/fail2ban/issues/3787

with the exact same problem where someone mentions installing
python3-setuptools fixes the issue.  This works for Debian also.

        I'm not sure how long this situation is going to persist
since it sounds like from the aforementioned bug report that this
might not be necessary in the near future.  But for now, this
package might need an additional dependency defined on
python3-setuptools where it may not otherwise be installed.

-- System Information:
Debian Release: trixie/sid
  APT prefers testing
  APT policy: (700, 'testing'), (600, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.8.12-amd64 (SMP w/16 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.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.12.3-1
ii  python3-systemd  235-1+b4

Versions of packages fail2ban recommends:
ii  nftables           1.0.9-2
ii  python3-pyinotify  0.9.6-3
ii  whois              5.5.23

Versions of packages fail2ban suggests:
ii  bsd-mailx [mailx]            8.1.2-0.20220412cvs-1
pn  monit                        <none>
ii  rsyslog [system-log-daemon]  8.2406.0-1
ii  sqlite3                      3.46.0-1

-- no debconf information

-- 
Mark Nipper

Reply via email to