Skip to content
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

[BR]: Failed during configuration: Have not found any log file for sshd jail #3567

Closed
1 of 3 tasks
Arne19 opened this issue Aug 27, 2023 · 1 comment
Closed
1 of 3 tasks

Comments

@Arne19
Copy link

Arne19 commented Aug 27, 2023

First sorry if this issue is already known, I couldn't find it here so far.

Environment:

freshly install Debian Bookworm on a remote server.

  • Fail2Ban version : v1.0.2
  • OS, including release name/version : Latest Debian 12
  • Fail2Ban installed via OS/distribution mechanisms
  • You have not applied any additional foreign patches to the codebase
  • Some customizations were done to the configuration (provide details below is so)

The issue:

Hi, on a just freshly installed Debian Bookworm I had this issue with fail2ban. Restarting it, rebooting or reinstallation didn't help. I had to manually change the backend from auto to systemd and then it worked.

Steps to reproduce

install debian bookworm, install ufw and fail2ban. Enable and start fail2ban.

Expected behavior

Fail2ban directly starts and filtering sshd.

Observed behavior

Fail2ban can't be started until manually change the backend from auto to systemd

Any additional information

Configuration, dump and another helpful excerpts

Any customizations done to /etc/fail2ban/ configuration

No customization was done on fail2ban configs.

Relevant parts of /var/log/fail2ban.log file:

 fail2ban.configreader   [2192]: WARNING 'allowipv6' not defined in 'Definition'. Using default one: 'auto'
 fail2ban                [2192]: ERROR   Failed during configuration: Have not found any log file for sshd jail
fail2ban                [2192]: ERROR   Async configuration of server failed

Relevant lines from monitored log files:

@sebres
Copy link
Contributor

sebres commented Aug 28, 2023

Dup of #3292
See #3292 (comment) for a solution.

@sebres sebres closed this as not planned Won't fix, can't repro, duplicate, stale Aug 28, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants