Re: [Fail2ban-users] Fail2ban 0.9.3-1 not starting

[Harrison J. <hjo...@co...>]

He got it working by re-installing from the source.

On Sat, 2015-10-03 at 19:19 -0600, Orion Poplawski wrote:

> On 10/03/2015 06:46 AM, fai...@fi... 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"?
> 
>