-------- Original Message -------- Subject: Re: [Fail2ban-users] Fail2ban 0.9.3-1 not starting Date: 2015-10-04 09:52 From: FinnB <[email protected]> To: Orion Poplawski <[email protected]>
On 2015-10-04 03:19, Orion Poplawski wrote: > On 10/03/2015 06:46 AM, [email protected] wrote: >> 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' >> > > That really makes no sense to me. what does "rpm -V fail2ban-server" > report? Anything more in "journalctl -b -u fail2ban.service"? I got it up running again, by removing the yum updates and install from source as originally. Locating fail2ban-xxxxx I only got those placed under /usr/bin/fail2ban-server dated Sept. 12. My guess will be that yum did not update the /usr/bin/fail2ban-xxxxx scripts - neither from 0.9.1 -> 0.9.2 or from 0.9.2 -> 0.9.3 but some libraries got changed from release 0.9.2 -> 0.9.3 and that did the inconsistincy with my 0.9.1. (all yum updates went fine according to yum.log) journalctl -b -u fail2ban.service does only reveal same things as listed above. Regards, Finn ------------------------------------------------------------------------------ _______________________________________________ Fail2ban-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/fail2ban-users
