On Thu, Feb 9, 2023 at 8:26 AM L. V. Lammert <l...@omnitec.net> wrote:
>
> On Thu, 9 Feb 2023, Marcos A.T. Silva wrote:
>
> > Hi again,
> >
> > I think I understood. Thank you very much.
> >
> > Well, doing that (I´ve only changed tne jail.local because I don't
> > understood very well that jail.d part) the error regarding Selinux
> > disappeared. But now a new error is being displayed:
> >
> > "[21330]: ERROR Failed during configuration: Have not found any log file
> > for apache-auth jail"
> >
> Same problem; the configuration you are working from does not match the
> machine where it is deployed.
>
> In most instances, fail2ban installs with a single jail enabled, ssh, and
> then the configuration is updated to include jails as required, using
> logfiles present on the machine.
>
Which distro are you using?
My 2 coffee grains:
1. Turn ONE of the fail2ban monitoring things in jail.local on. Just one.
1.5. Turn them all off in jail.local and then create a jail.d/service.conf file
2. Go to /etc/fail2ban/paths-common.conf and verify the log file(s)
used by the service you are actually monitoring exists. Adjust as
needed either there or in your service.conf file
3. Restart fail2ban and ensure it works.
4. Once satisfied fail2ban is monitoring service, create a new
jail.d/service.conf and repeats steps 2-4 on this new service
_______________________________________________
Fail2ban-users mailing list
Fail2ban-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/fail2ban-users
