fail2ban Fehler

fendix · 26. September 2019

Moin,

ich bekomme leider fail2ban nicht auf meinem Server zu laufen.

Debian 9
apt purge fail2ban
apt autoremove
apt install fail2ban

Bash

The following NEW packages will be installed:
  fail2ban python3-pyinotify python3-systemd
0 upgraded, 3 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/348 kB of archives.
After this operation, 1616 kB of additional disk space will be used.
Do you want to continue? [Y/n] y
Selecting previously unselected package fail2ban.
(Reading database ... 39741 files and directories currently installed.)
Preparing to unpack .../fail2ban_0.9.6-2_all.deb ...
Unpacking fail2ban (0.9.6-2) ...
Selecting previously unselected package python3-pyinotify.
Preparing to unpack .../python3-pyinotify_0.9.6-1_all.deb ...
Unpacking python3-pyinotify (0.9.6-1) ...
Selecting previously unselected package python3-systemd.
Preparing to unpack .../python3-systemd_233-1_amd64.deb ...
Unpacking python3-systemd (233-1) ...
Setting up fail2ban (0.9.6-2) ...
Created symlink /etc/systemd/system/multi-user.target.wants/fail2ban.service → /                                                          lib/systemd/system/fail2ban.service.
Job for fail2ban.service failed because the control process exited with error co                                                          de.
See "systemctl status fail2ban.service" and "journalctl -xe" for details.
invoke-rc.d: initscript fail2ban, action "start" failed.
● fail2ban.service - Fail2Ban Service
   Loaded: loaded (/lib/systemd/system/fail2ban.service; enabled; vendor preset:                                                           enabled)
   Active: activating (auto-restart) (Result: exit-code) since Thu 2019-09-26 14                                                          :57:08 CEST; 7ms ago
     Docs: man:fail2ban(1)
  Process: 9144 ExecStart=/usr/bin/fail2ban-client -x start (code=exited, status                                                          =255)
 Main PID: 2009 (code=killed, signal=TERM)


Sep 26 14:57:08 v220 systemd[1]: fail2ban.service: Control pr…255
Sep 26 14:57:08 v220 systemd[1]: Failed to start Fail2Ban Ser…ce.
Sep 26 14:57:08 v220 systemd[1]: fail2ban.service: Unit enter…te.
Sep 26 14:57:08 v220 systemd[1]: fail2ban.service: Failed wit…e'.
Hint: Some lines were ellipsized, use -l to show in full.
dpkg: error processing package fail2ban (--configure):
 subprocess installed post-installation script returned error exit status 1
Setting up python3-systemd (233-1) ...
Processing triggers for systemd (232-25+deb9u12) ...
Processing triggers for man-db (2.7.6.1-2) ...
Setting up python3-pyinotify (0.9.6-1) ...
Errors were encountered while processing:
 fail2ban
E: Sub-process /usr/bin/dpkg returned an error code (1)

Alles anzeigen

journalctl -xe

Bash

Sep 26 14:57:10 v220 systemd[1]: fail2ban.service: Failed with result 'exit-code'.
Sep 26 14:57:10 v220 systemd[1]: fail2ban.service: Service hold-off time over, scheduling restart.
Sep 26 14:57:10 v220 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.
Sep 26 14:57:10 v220 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.
Sep 26 14:57:10 v220 fail2ban-client[9257]: ERROR  Server already running
Sep 26 14:57:10 v220 systemd[1]: fail2ban.service: Control process exited, code=exited status=255
Sep 26 14:57:10 v220 systemd[1]: Failed to start Fail2Ban Service.
-- Subject: Unit fail2ban.service has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- Unit fail2ban.service has failed.
--
-- The result is failed.
Sep 26 14:57:10 v220 systemd[1]: fail2ban.service: Unit entered failed state.
Sep 26 14:57:10 v220 systemd[1]: fail2ban.service: Failed with result 'exit-code'.
Sep 26 14:57:10 v220 systemd[1]: fail2ban.service: Service hold-off time over, scheduling restart.
Sep 26 14:57:10 v220 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.
Sep 26 14:57:10 v220 systemd[1]: fail2ban.service: Start request repeated too quickly.
Sep 26 14:57:10 v220 systemd[1]: Failed to start Fail2Ban Service.
-- Subject: Unit fail2ban.service has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- Unit fail2ban.service has failed.
--
-- The result is failed.
Sep 26 14:57:10 v220 systemd[1]: fail2ban.service: Unit entered failed state.
Sep 26 14:57:10 v220 systemd[1]: fail2ban.service: Failed with result 'exit-code'.


root@v220:~# clear
root@v220:~# journalctl -xe
-- The result is failed.
Sep 26 14:57:10 v220 systemd[1]: fail2ban.service: Unit entered failed state.
Sep 26 14:57:10 v220 systemd[1]: fail2ban.service: Failed with result 'exit-code'.
Sep 26 14:57:10 v220 systemd[1]: fail2ban.service: Service hold-off time over, scheduling restart.
Sep 26 14:57:10 v220 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.
Sep 26 14:57:10 v220 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.
Sep 26 14:57:10 v220 fail2ban-client[9257]: ERROR  Server already running
Sep 26 14:57:10 v220 systemd[1]: fail2ban.service: Control process exited, code=exited status=255
Sep 26 14:57:10 v220 systemd[1]: Failed to start Fail2Ban Service.
-- Subject: Unit fail2ban.service has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- Unit fail2ban.service has failed.
--
-- The result is failed.
Sep 26 14:57:10 v220 systemd[1]: fail2ban.service: Unit entered failed state.
Sep 26 14:57:10 v220 systemd[1]: fail2ban.service: Failed with result 'exit-code'.
Sep 26 14:57:10 v220 systemd[1]: fail2ban.service: Service hold-off time over, scheduling restart.
Sep 26 14:57:10 v220 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.
Sep 26 14:57:10 v220 systemd[1]: fail2ban.service: Start request repeated too quickly.
Sep 26 14:57:10 v220 systemd[1]: Failed to start Fail2Ban Service.
-- Subject: Unit fail2ban.service has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- Unit fail2ban.service has failed.
--
-- The result is failed.
Sep 26 14:57:10 v220 systemd[1]: fail2ban.service: Unit entered failed state.
Sep 26 14:57:10 v220 systemd[1]: fail2ban.service: Failed with result 'exit-code'.

Alles anzeigen

lg.

Fischer · 26. September 2019

Was sagt denn die fail2ban.log ?

fendix · 26. September 2019

Zitat von [NeS]Fischer

Was sagt denn die fail2ban.log ?

Die Log ist leider leer.

Individuum · 27. September 2019

Welche Änderungen hast du denn an dem System vorgenommen?
Gibt es irgendwelche Symlinks, die auf fail2ban referenzieren, nach dem du

Zitat von damx

apt purge fail2ban
apt autoremove
apt install fail2ban

ausgeführt hast?

Du hast, meiner Meinung nach, noch irgendwo was liegen, wo der

Teste mal die Deinstallation mit:

Code

dpkg --list | grep "fail2ban"

ob wirklich alles weg ist.

Weiterhin:

Code

apt --purge remove fail2ban -y

zur Entfernung des Paketes.

Wenn du möchtest, kann ich auch mal eben mit drüber schauen. Melde dich dazu einfach bei mir

fendix · 27. September 2019

Moin,

Bash

root@v220190910434497810:~# dpkg --list | grep "fail2ban"
root@v220190910434497810:~# apt --purge remove fail2ban -y
Reading package lists... Done
Building dependency tree
Reading state information... Done
Package 'fail2ban' is not installed, so not removed
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
root@v220190910434497810:~#

Habe dir mal eine PN geschrieben

fail2ban Fehler

seegras 27. Oktober 2021

breadfish.de 12. März 2022