under 22.04 development release, fail2ban won't start
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
fail2ban (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
I upgraded from 21.10 to 22.04 on my workstation just to check out gotchas before the real release comes out, and one I ran into right away that fail2ban would not start.
I totally uninstalled and purged and then re-installed it in case somehow old stuff left was breaking it but fails with this error:
Loaded: loaded (/lib/systemd/
Active: failed (Result: exit-code) since Thu 2022-03-10 01:30:13 PST; 7s ago
Docs: man:fail2ban(1)
Process: 2272807 ExecStart=
Main PID: 2272807 (code=exited, status=
CPU: 39ms
Mar 10 01:30:13 nanook systemd[1]: Started Fail2Ban Service.
Mar 10 01:30:13 nanook fail2ban-
Mar 10 01:30:13 nanook systemd[1]: fail2ban.service: Main process exited, code=exited, status=
Mar 10 01:30:13 nanook systemd[1]: fail2ban.service: Failed with result 'exit-code'.
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: fail2ban 0.11.2-5
Uname: Linux 5.16.13 x86_64
ApportVersion: 2.20.11-0ubuntu78
Architecture: amd64
CasperMD5CheckR
CurrentDesktop: MATE
Date: Thu Mar 10 01:16:54 2022
InstallationDate: Installed on 2021-11-11 (119 days ago)
InstallationMedia: Ubuntu-MATE 21.10 "Impish Indri" - Release amd64 (20211012)
PackageArchitec
SourcePackage: fail2ban
UpgradeStatus: Upgraded to jammy on 2022-03-10 (0 days ago)
information type: | Private Security → Public |
The bug you say this is a duplicate of is for Impish (where it was formerly working for me) this bug is for Jammy (where it ceased working).
On 3/10/22 1:51 PM, Sylvestre Ledru <email address hidden> wrote: /bugs.launchpad .net/bugs/ 1958505
> *** This bug is a duplicate of bug 1958505 ***
> https:/
>
> ** This bug has been marked a duplicate of bug 1958505
> fail2ban fails to start on 22.04
>
>