Applying the fix in github resulted in a different error:
ail2ban.service - Fail2Ban Service
Loaded: loaded (/lib/systemd/system/fail2ban.service; enabled; vendor
preset: enabled)
Active: failed (Result: exit-code) since Thu 2022-03-10 14:51:00 PST; 5s
ago
Docs: man:fail2ban(1)
Process: 22282 ExecStartPre=/bin/mkdir -p /run/fail2ban (code=exited,
status=0/SUCCESS)
Process: 22283 ExecStart=/usr/bin/fail2ban-server -xf start (code=exited,
status=255/EXCEPTION)
Main PID: 22283 (code=exited, status=255/EXCEPTION)
CPU: 33ms
Mar 10 14:51:00 nanook systemd[1]: Starting Fail2Ban Service...
Mar 10 14:51:00 nanook systemd[1]: Started Fail2Ban Service.
Mar 10 14:51:00 nanook fail2ban-server[22283]: ERROR: No module named
'ConfigParser'
Mar 10 14:51:00 nanook systemd[1]: fail2ban.service: Main process exited,
code=exited, status=255/EXCEPTION
Mar 10 14:51:00 nanook systemd[1]: fail2ban.service: Failed with result
'exit-code'.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1958505
Title:
fail2ban fails to start on 22.04
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fail2ban/+bug/1958505/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
