Hi list. After updating fail2ban (yum update) to the latest fail2ban 0.9.3-1.el7 from 0.9.2-1.el7, my fail2ban will not start properly.
I'm running Centos7 (3.10.0-229.14.1.el7.x86_64) with latest updates. Nothing is written in the fail2ban.log file since the update stopped the former fail2ban - nicely 'fail2ban-client -x -v start' does not provide any lines in fail2ban.log but output shows all filters, actions and conf files loads fine but it ends as shown in the below inserted message.log but it starts an instance of fail2ban-server, but still same status from systemctl and journalctl as below inserted I have read the release notes but cannot see any specifics that suggest I need to change anything in *.conf files. What am I missing ? in the messages log /usr/bin/fail2ban-client -x start 2015-10-03 13:22:36,555 fail2ban.server [2946]: INFO Starting Fail2ban v0.9.1 2015-10-03 13:22:36,555 fail2ban.server [2946]: INFO Starting in daemon mode Traceback (most recent call last): File "/usr/bin/fail2ban-client", line 470, in <module> if client.start(sys.argv): File "/usr/bin/fail2ban-client", line 440, in start return self.__processCommand(args) File "/usr/bin/fail2ban-client", line 244, in __processCommand self.__waitOnServer() File "/usr/bin/fail2ban-client", line 331, in __waitOnServer while not self.__ping(): File "/usr/bin/fail2ban-client", line 153, in __ping return self.__processCmd([["ping"]], False) File "/usr/bin/fail2ban-client", line 185, in __processCmd client.close() AttributeError: CSocket instance has no attribute 'close' systemctl status fail2ban fail2ban.service - Fail2Ban Service Loaded: loaded (/usr/lib/systemd/system/fail2ban.service; enabled) Active: failed (Result: start-limit) since Sat 2015-10-03 13:00:02 CEST; 9min ago Docs: man:fail2ban(1) Process: 2845 ExecStart=/usr/bin/fail2ban-client -x start code=exited, status=1/FAILURE) systemd[1]: fail2ban.service: control process exited, code=exited status=1 systemd[1]: Failed to start Fail2Ban Service. systemd[1]: Unit fail2ban.service entered failed state. systemd[1]: fail2ban.service holdoff time over, scheduling restart. systemd[1]: Stopping Fail2Ban Service... systemd[1]: Starting Fail2Ban Service... systemd[1]: fail2ban.service start request repeated too quickly, refusing to start. systemd[1]: Failed to start Fail2Ban Service. systemd[1]: Unit fail2ban.service entered failed state. journalctl -xn -- Logs begin at Sat 2015-10-03 12:04:20 CEST, end at Sat 2015-10-03 13:01:01 CEST. -- systemd[1]: fail2ban.service start request repeated too quickly, refusing to start. 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. systemd[1]: Unit fail2ban.service entered failed state. systemd[1]: Starting Session 2 of user root. -- Subject: Unit session-2.scope has begun with start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit session-2.scope has begun starting up. systemd[1]: Started Session 2 of user root. -- Subject: Unit session-2.scope has finished start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit session-2.scope has finished starting up. Thanks Finn ------------------------------------------------------------------------------ _______________________________________________ Fail2ban-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/fail2ban-users
