Re: Fail2ban is failing

2024-05-03 Thread Patrick O'Callaghan
On Fri, 2024-05-03 at 16:52 -0500, Richard Shaw wrote:
> On Fri, May 3, 2024 at 4:13 PM Patrick O'Callaghan
> 
> 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.

# ls -lZ /var/run/fail2ban/fail2ban.sock
srwx--. 1 root root system_u:object_r:var_run_t:s0 0 May  3 22:10 
/var/run/fail2ban/fail2ban.sock

Running restorecon on that (and the directory itself) leaves it
unchanged, so presumably it's incorrect in the database.

poc
--
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
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@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue


Re: Fail2ban is failing

2024-05-03 Thread Richard Shaw
On Fri, May 3, 2024 at 4:13 PM Patrick O'Callaghan 
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@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
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@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue


Re: Fail2ban is failing

2024-05-03 Thread Patrick O'Callaghan
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.

poc
--
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
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@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue


Re: Fail2ban is failing

2024-05-03 Thread Tom Rivers via users
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

Tom

On 5/3/2024 12:39 PM, Patrick O'Callaghan wrote:

On Fri, 2024-05-03 at 06:45 -0500, Richard Shaw wrote:

On Fri, May 3, 2024 at 6:31 AM Patrick O'Callaghan

wrote:


F40 fully updated.


Try a `dnf --refresh update`. The fix just went to stable last night.

That just gets the same update I already tried.

poc
--
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
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@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

--
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
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@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue


Re: Fail2ban is failing

2024-05-03 Thread Patrick O'Callaghan
On Fri, 2024-05-03 at 06:45 -0500, Richard Shaw wrote:
> On Fri, May 3, 2024 at 6:31 AM Patrick O'Callaghan
> 
> wrote:
> 
> > F40 fully updated.
> > 
> 
> Try a `dnf --refresh update`. The fix just went to stable last night.

That just gets the same update I already tried.

poc
--
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
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@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue


Re: Fail2ban is failing

2024-05-03 Thread Richard Shaw
On Fri, May 3, 2024 at 6:31 AM Patrick O'Callaghan 
wrote:

> F40 fully updated.
>

Try a `dnf --refresh update`. The fix just went to stable last night.

Thanks,
Richard
--
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
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@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue