Fail2Ban Exit code 1 Error

    • Fail2Ban Exit code 1 Error

      Hello OMV,

      I've been a lurker for a little bit, I've read through some of the solutions for fixing fail2ban which involve removing debian default confs and still haven't come up with a solution.

      When attempting to start fail2ban I get the following error:
      Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C.UTF-8; systemctl start 'fail2ban' 2>&1' with exit code '1': Job for fail2ban.service failed because the control process exited with error code. See "systemctl status fail2ban.service" and "journalctl -xe" for details.

      Running journalctl -xe I get:
      Apr 01 22:01:19 raspberrypi systemd[1]: Starting Fail2Ban Service...
      -- Subject: Unit fail2ban.service has begun start-up
      -- Defined-By: systemd
      -- Support: https://www.debian.org/support
      --
      -- Unit fail2ban.service has begun starting up.
      root@raspberrypi:/etc/fail2ban# journalctl -xe
      -- Unit fail2ban.service has failed.
      --
      -- The result is failed.
      Apr 01 22:01:20 raspberrypi systemd[1]: [b]fail2ban.service: Unit entered failed state.[/b]
      Apr 01 22:01:20 raspberrypi systemd[1]: [b]fail2ban.service: Failed with result 'exit-code'.[/b]
      Apr 01 22:01:20 raspberrypi systemd[1]: fail2ban.service: Service hold-off time over, scheduling re
      Apr 01 22:01:20 raspberrypi systemd[1]: Stopped Fail2Ban Service.
      -- Subject: Unit fail2ban.service has finished shutting down
      -- Defined-By: systemd
      -- Support: https://www.debian.org/support
      --
      -- Unit fail2ban.service has finished shutting down.
      Apr 01 22:01:20 raspberrypi systemd[1]: [b]fail2ban.service: Start request repeated too quickly.[/b]
      Apr 01 22:01:20 raspberrypi systemd[1]: [b]Failed to start Fail2Ban Service.[/b]
      -- Subject: Unit fail2ban.service has failed
      -- Defined-By: systemd
      -- Support: https://www.debian.org/support
      --
      -- Unit fail2ban.service has failed.
      --
      -- The result is failed.
      Apr 01 22:01:20 raspberrypi systemd[1]: [b]fail2ban.service: Unit entered failed state.[/b]
      Apr 01 22:01:20 raspberrypi systemd[1]: [b]fail2ban.service: Failed with result 'exit-code'.[/b]

      It's not very descriptive and the solutions online don't seem to help.

      Anyone have any ideas? Thank you.
    • Okay I think I got somewhere - every time you reboot OMV or restart docker, there's a new container id.

      I'm using my /var/lib/docker/container/___________/________.log

      As the log file in fail2ban. However, it changes frequently. Is there any way to automatically create the linkage to that log file? I checked my samba shares and the log file doesn't seem to be on there.
    • Users Online 1

      1 Guest