The new package has been working good for me EXCEPT wordpress thinks it
isn't running even though it is AND it acts on the WordPress filters and jails
I have installed.
-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-
Eskimo North Linux Friendly Internet Access, Shell Accounts, and Hosting.
Knowledgeable human assistance, not telephone trees or script readers.
See our web site: http://www.eskimo.com/ (206) 812-0051 or (800) 246-6874.
On Tue, 11 Jun 2024, Brian Murray wrote:
> Date: Tue, 11 Jun 2024 20:05:13 -0000
> From: Brian Murray <2055...@bugs.launchpad.net>
> To: nan...@eskimo.com
> Subject: [Bug 2055114] Re: fail2ban is broken in 24.04 Noble
>
> Hello Robert, or anyone else affected,
>
> Accepted fail2ban into noble-proposed. The package will build now and be
> available at
> https://launchpad.net/ubuntu/+source/fail2ban/1.0.2-3ubuntu0.1 in a few
> hours, and then in the -proposed repository.
>
> Please help us by testing this new package. See
> https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
> to enable and use -proposed. Your feedback will aid us getting this
> update out to other Ubuntu users.
>
> If this package fixes the bug for you, please add a comment to this bug,
> mentioning the version of the package you tested, what testing has been
> performed on the package and change the tag from verification-needed-
> noble to verification-done-noble. If it does not fix the bug for you,
> please add a comment stating that, and change the tag to verification-
> failed-noble. In either case, without details of your testing we will
> not be able to proceed.
>
> Further information regarding the verification process can be found at
> https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in
> advance for helping!
>
> N.B. The updated package will be released to -updates after the bug(s)
> fixed by this package have been verified and the package has been in
> -proposed for a minimum of 7 days.
>
> ** Changed in: fail2ban (Ubuntu Noble)
> Status: Confirmed => Fix Committed
>
> ** Tags added: verification-needed verification-needed-noble
>
> --
> You received this bug notification because you are 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:
> Fix Committed
> 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
>
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2055114
Title:
fail2ban is broken in 24.04 Noble
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fail2ban/+bug/2055114/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
