Your message dated Sun, 01 Sep 2024 07:04:32 +0000 with message-id <e1skedu-002xsp...@fasolo.debian.org> and subject line Bug#1076494: fixed in fail2ban 1.1.0-7 has caused the Debian Bug report #1076494, regarding fail2ban: failure to start due to missing distutils and needing python3-setuptools installed currently to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1076494: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1076494 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---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
--- End Message ---
--- Begin Message ---Source: fail2ban Source-Version: 1.1.0-7 Done: Sylvestre Ledru <sylves...@debian.org> We believe that the bug you reported is fixed in the latest version of fail2ban, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1076...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sylvestre Ledru <sylves...@debian.org> (supplier of updated fail2ban package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Format: 1.8 Date: Sun, 01 Sep 2024 08:40:14 +0200 Source: fail2ban Architecture: source Version: 1.1.0-7 Distribution: unstable Urgency: medium Maintainer: Debian Python Team <team+pyt...@tracker.debian.org> Changed-By: Sylvestre Ledru <sylves...@debian.org> Closes: 1076494 Changes: fail2ban (1.1.0-7) unstable; urgency=medium . * Add python3-setuptools to the run time build deps (Closes: #1076494) Should be removed at some point when upstream removes the need Checksums-Sha1: 5d519366cc671c0373246f9918a55c1d04b50176 2054 fail2ban_1.1.0-7.dsc cdec19b5826b26ffe765d33ebdf3ec9fac9baec0 30664 fail2ban_1.1.0-7.debian.tar.xz 18b333bec25e5da4b945e3e4d2c447d15a831b5d 6823 fail2ban_1.1.0-7_amd64.buildinfo Checksums-Sha256: 4b3cda61557328f2d26b66e6daad096dcc860792ae8bf07a1b9dca4ffa7ccbca 2054 fail2ban_1.1.0-7.dsc 69c95b82d37092dac0e8b62992ecb1e03944d21de7aa8cfc5642c2efab4d5bcb 30664 fail2ban_1.1.0-7.debian.tar.xz d82efcdeedc3245521f336838d24181f2149e36454c67ed6fc361352947b870c 6823 fail2ban_1.1.0-7_amd64.buildinfo Files: 73879a92bb7eafa631a5fc08f9de6bf5 2054 net optional fail2ban_1.1.0-7.dsc d2af1e9680696d991d3d4a5b358fcf68 30664 net optional fail2ban_1.1.0-7.debian.tar.xz 3c524b200a5d819f05a66621636c5722 6823 net optional fail2ban_1.1.0-7_amd64.buildinfo -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEtg21mU05vsTRqVzPfmUo2nUvG+EFAmbUDfYACgkQfmUo2nUv G+EltA//ftMrm8iziIj7VINkx74Sy2tKiFoxZG5UC7vL9VHbpiI2nEXC8bPnp4s4 UUG0lo8Slu0c2fFvKCS6mHTd4U1mxQM2EIIftxAy9v1uE8S6rJGJzuW7SVouyLyr xatPPvfDkv95nlhWNHFjv+YaO3e4IXSf9ej5JXcz7k1MnT0XklsEuBn5bbmpOD9C eVoEh1f5V0YL9R2aBfIv2uhDb2DwVg+2Gg0S/OcmtUzMsnWjBjifue742hqLAt29 1/+yBKIOdvy3QZIKvM0NtFk+i0u1s4WKrrL5OwcZ4RjzWEx8P0MyttGWe/I82lHr /g8cQec+OAIVxYvrtwUgkFSSwq0u2fJBASHKeokfQto99aFe14663MuvsrUyufrI v/oC0285k3ZcdcW7BJUnB0wkNes/mx9eB2YYDLTmJqTX66A2rkm6bn6vKCiVtfqr XyZuaUCh6RRsBjdS1TN0+ltZwlzVtPRAqHR6bDzdBJLTJbshvL6lEf2r1chKioCo N8mpXDVNH6SGsjkjBcUrjY7tP+o4mXc39geAs5wHG9c6VwfxvPjGlAyPDZB61PSo ADWo2mWIVtT4KQq7xs++BwQXkvrepk90uWwb7YlshaJUvOcSjvvw8IAPNFnv2BFE 8Xj3ZwzQTCsCDGqpn7eHF7GT6ktdyLZe40v2vEf4exmjMCIEy68= =Kf5z -----END PGP SIGNATURE-----
pgpJyL9KwHRZF.pgp
Description: PGP signature
--- End Message ---
