Resolved Fail2ban will not start

[tkalfaoglu]

Following some thread on the 'net, I found that my fail2ban was installed or updated by some other repo, so I uninstalled it.. Removed the /etc/fail2ban directory that was left over, removed it from Plesk's installation utility and re-installed it using the same utility.

However, I noticed it was not running.. So I did a "service fail2ban start", and it gets stuck.. I waited for 5 minutes..

[root@pluto ~]# service fail2ban start
Starting fail2ban:
(stuck here)

Here is how it looks:
# ps ax|grep fail2
17441 pts/0 S+ 0:00 /bin/sh /sbin/service fail2ban start
17448 pts/0 S+ 0:00 /bin/bash /etc/init.d/fail2ban start
17454 pts/0 R+ 0:07 /usr/bin/python2.6 /usr/bin/fail2ban-client -x start
17459 pts/0 Z+ 0:00 [fail2ban-server] <defunct>
17461 ? S 0:00 /usr/bin/python2.6 /usr/bin/fail2ban-server -b -s /var/run/fail2ban/fail2ban.sock -p /var/run/fail2ban/fail2ban.pid -x
17479 pts/1 S+ 0:00 grep fail2

PS: This is not the same error a KB exists for - it never seems to log anything in /var/log/messages nor does it eventually throw an error.

What shall I do?
Many thanks, -turgut

 

[tkalfaoglu]

Followup: I discovered that it's doing an endless job of
2016-12-18 08:13:00,088 fail2ban.filter [4934]: INFO Added logfile = /var/www/vhosts/system/www.kalfaoglu.net/logs/access_log
(....)
2016-12-18 08:18:57,738 fail2ban.filter [4934]: INFO Added logfile = /var/www/vhosts/system/www.blabla.com/logs/proxy_access_log

So there is light at the end of the tunnel, if this adding ever finishes
-turgut

 

[tkalfaoglu]

Ten minutes later it is still going strong at "added logfile...." business..
Is that normal?