registry team mailing list archive

Thread
Date

[Bug 403808] Re: fail2ban not execute command to start jail

To: registry@xxxxxxxxxxxxxxxxxxx
From: Pawel Barcik <403808@xxxxxxxxxxxxxxxxxx>
Date: Thu, 15 Jul 2010 15:07:37 -0000
Reply-to: Bug 403808 <403808@xxxxxxxxxxxxxxxxxx>
Sender: bounces@xxxxxxxxxxxxx

It is caused by iptables, and the solution is here at the end of the
page:

http://www.fail2ban.org/wiki/index.php/Fail2ban_talk:Community_Portal

"fail2ban.action.action ERROR on startup/restart

I had multiple fail2ban.action.action ERROR on startup/restart. It seems
there was a "race" condition with iptables. I solved the problem
completely on my system by editing /usr/bin/fail2ban-client and adding a
time.sleep(0.1)

def __processCmd(self, cmd, showRet = True): 
beautifier = Beautifier() for c in cmd: time.sleep(0.1) beautifier.setInputCmd(c) "

adding " time.sleep(0.1)" worked like a charm for me. it extends the
restart time by 20 or so seconds, but works great.

-- 
fail2ban not execute command to start jail
https://bugs.launchpad.net/bugs/403808
You received this bug notification because you are a member of Registry
Administrators, which is the registrant for Debian.