[Bug 2055114] Re: fail2ban is broken in 24.04 Noble

[Gianfranco Costamagna]

guys, please stop spamming this bug.
The patch is already in noble unapproved queue, waiting for ubuntu-SRU release managers to pick it up.
https://launchpadlibrarian.net/731722634/fail2ban_1.0.2-3_1.0.2-3ubuntu1.24.04.1.diff.gz

https://launchpad.net/ubuntu/noble/+queue?queue_state=1&queue_text=fail

The versioning looks correct 1.0.2-3ubuntu1.24.04.1, I hope it is just a
matter of time.

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/2055114

Title:
  fail2ban is broken in 24.04 Noble

Status in fail2ban package in Ubuntu:
  Fix Released
Status in fail2ban source package in Noble:
  Confirmed
Status in fail2ban source package in Oracular:
  Fix Released

Bug description:
  [ Impact ] 
  * fail2ban fails to start on Ubuntu 24.04, due to new Python and deprecated classes (now vendored upstream)

  [ Test Plan ]
  * Install and check systemctl status fail2ban.

  [ Where problems could occur ]
  * Nowhere, fixing a program failing to start

  [ Other info ]
  Was working in 22.04, but after upgrading to 24.04 I get this:

  × fail2ban.service - Fail2Ban Service
       Loaded: loaded (/etc/systemd/system/fail2ban.service; enabled; preset: enabled)
       Active: failed (Result: exit-code) since Sun 2024-02-25 02:27:29 PST; 1 day 18h ago
     Duration: 2.330s
         Docs: man:fail2ban(1)
      Process: 1130 ExecStartPre=/bin/mkdir -p /run/fail2ban (code=exited, status=0/SUCCESS)
      Process: 1133 ExecStart=/usr/local/bin/fail2ban-server -xf start (code=exited, status=255/EXCEPTION)
     Main PID: 1133 (code=exited, status=255/EXCEPTION)
          CPU: 660ms

  Feb 25 02:27:26 mx1 systemd[1]: Starting fail2ban.service - Fail2Ban Service...
  Feb 25 02:27:26 mx1 systemd[1]: Started fail2ban.service - Fail2Ban Service.
  Feb 25 02:27:28 mx1 fail2ban-server[1133]: 2024-02-25 02:27:28,952 fail2ban                [1133]: ERROR   No module named 'asynchat'
  Feb 25 02:27:29 mx1 systemd[1]: fail2ban.service: Main process exited, code=exited, status=255/EXCEPTION
  Feb 25 02:27:29 mx1 systemd[1]: fail2ban.service: Failed with result 'exit-code'.

  grep fail2ban syslog
  2024-02-25T02:25:17.813593-08:00 mx1 systemd[1]: Stopping fail2ban.service - Fail2Ban Service...
  2024-02-25T02:27:26.625640-08:00 mx1 systemd[1]: Starting fail2ban.service - Fail2Ban Service...
  2024-02-25T02:27:26.678572-08:00 mx1 systemd[1]: Started fail2ban.service - Fail2Ban Service.
  2024-02-25T02:27:28.954548-08:00 mx1 fail2ban-server[1133]: 2024-02-25 02:27:28,952 fail2ban                [1133]: ERROR   No module named 'asynchat'
  2024-02-25T02:27:29.004733-08:00 mx1 systemd[1]: fail2ban.service: Main process exited, code=exited, status=255/EXCEPTION
  2024-02-25T02:27:29.004834-08:00 mx1 systemd[1]: fail2ban.service: Failed with result 'exit-code'.

  Seems 24.04 is missing a python 3.12 module 'asynchat'.

  This leaves my systems vulnerable to brute-force password guessing
  attacks.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: fail2ban 1.0.2-3
  Uname: Linux 6.7.6 x86_64
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: MATE
  Date: Mon Feb 26 20:33:12 2024
  InstallationDate: Installed on 2017-08-14 (2388 days ago)
  InstallationMedia: Ubuntu-MATE 17.04 "Zesty Zapus" - Release amd64 (20170412)
  PackageArchitecture: all
  SourcePackage: fail2ban
  UpgradeStatus: Upgraded to noble on 2024-01-23 (35 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fail2ban/+bug/2055114/+subscriptions