-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fail2ban unable to start in ubuntu 24.04 container #3685
Comments
I have added backend = systemd and the error i now get is ;
trying fail2ban client -x start also fails..... |
Well, if your system does not use journal, then sshd wouldn't log to journal and this setting would be wrong in that case.
Is python version 3.12+? (see #3487) Then it is only possible with newer fail2ban version or if you install that modules manually, e. g, with pip as described in pyasynchat and pyasyncore Otherwise I don't understand why this must be not found within ubuntu 24.04 (no matter container or not). |
I had this issue but installing from the |
Hi I'm trying to get fail2ban to run my ubuntu container (24.04) but getting error message ;
service fail2ban start
2024-02-29 13:44:50,301 fail2ban [78]: ERROR Failed during configuration: Have not found any log file for sshd jail
I am not using systemd so i'm unsure if it will work as i was originally upgrading a pod because it had been flagged by our security team (debian buster) with critical vulnerabilities. I have also configured /etc/fail2ban/jail.local with my sshd settings, is that the correct location ? I saw mention that i should set backend = systemd but not sure as i'm not using systemd.
The text was updated successfully, but these errors were encountered: