You are not logged in.
My fail2ban service has been failing since the last update on 3/11 or thereabouts. I had it setup running with systemd as backend, with firewalld/ipset for the rules and mailing out with ssmpt. I used an amalgamation of websites to get this setup properly since my use case isn't exactly standard and the Arch wiki was lacking in this regards.
Anyhow, the logs appear as follows:
➜ sudo systemctl restart fail2ban
Job for fail2ban.service failed because the control process exited with error code. See "systemctl status fail2ban.service" and "journalctl -xe" for details.
/etc/fail2ban ⍉ - 19:20:23
➜ journalctl -xe
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit fail2ban.service has finished shutting down.
Mar 23 19:20:24 wrangler systemd[1]: Starting Fail2Ban Service...
-- Subject: Unit fail2ban.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit fail2ban.service has begun starting up.
Mar 23 19:20:24 wrangler fail2ban-client[14572]: ERROR No file(s) found for glob /var/log/auth.log
Mar 23 19:20:24 wrangler fail2ban-client[14572]: ERROR Failed during configuration: Have not found any log file for sshd jail
Mar 23 19:20:24 wrangler systemd[1]: fail2ban.service: Control process exited, code=exited status=255
Mar 23 19:20:24 wrangler systemd[1]: Failed to start Fail2Ban Service.
-- Subject: Unit fail2ban.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit fail2ban.service has failed.
--
-- The result is failed.
Mar 23 19:20:24 wrangler systemd[1]: fail2ban.service: Unit entered failed state.
Mar 23 19:20:24 wrangler systemd[1]: fail2ban.service: Failed with result 'exit-code'.
Mar 23 19:20:24 wrangler systemd[1]: fail2ban.service: Service hold-off time over, scheduling restart.
Mar 23 19:20:24 wrangler systemd[1]: Stopped Fail2Ban Service.
-- Subject: Unit fail2ban.service has finished shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit fail2ban.service has finished shutting down.
Mar 23 19:20:24 wrangler systemd[1]: Starting Fail2Ban Service...
-- Subject: Unit fail2ban.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Any chance anyone has seen anything with the latest upgrade? I'm planning on rolling back a version to see if it solves my problem before modding config files but figured I'd put the feelers out on it.
Before anyone mentions it, my jail.local file has 'backend = systemd' in the [DEFAULT] section.
***update***
Opened an issue with Fail2ban group. Apparently there were some changes where the [DEFAULT] section is no longer read in the <jail>.conf file
Per https://github.com/fail2ban/fail2ban/issues/1372 , I renamed the [Default] section in my sshd.conf jail file to [SSHD] and it's working.
Last edited by kaos77 (2016-04-03 17:07:35)
Offline
I did downgrade to 9.3.6 from the 9.4.1 version. Worked a charm. Guess there's a bug that ignores the backend directive.
Offline
I can confirm. I updated my server today. I see the same errors with a failure to start the fail2ban service.
Offline