On Fri, May 3, 2024 at 4:13 PM Patrick O'Callaghan <pocallaghan@xxxxxxxxx> wrote:
On Fri, 2024-05-03 at 13:08 -0400, Tom Rivers via users wrote:
> Until the fix is available, I've been able to get it running until
> the
> next system reboot by doing the following:
>
> # setenforce 0
> # systemctl start fail2ban
>
> ... wait a minute ...
>
> # setenforce 1
>
That seems to work. Looks like a problem with SElinux labelling.
More or less, basically from what I can tell with F40 that the link from /var/run->/run for compatibility was dropped and the selinux context in the fail2ban package needed to be updated (and it was) but my assumption is that installation of the new package would take care of it.
Thanks,
Richard
-- _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
