This was bug https://github.com/fail2ban/fail2ban/issues/51
Correct fix that has been in debian for a while
https://github.com/fail2ban/fail2ban/commit/9c4b0418218d150f763e46236631c22c32ee134e
Daniel
fail2ban dev
--
You received this bug notification because you are a member of Ubuntu
Bugs,
This was fixed in 0.8.5-2, which has been in Ubuntu since before 12.04.
Marking Fix Released.
** Changed in: fail2ban (Ubuntu)
Status: Confirmed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Bug still present in fail2ban-0.8.5-1 (in oneiric).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/403808
Title:
fail2ban not execute command to start jail
To manage notifications about this bug go
** Changed in: fail2ban (Ubuntu)
Importance: Undecided = Medium
** Changed in: fail2ban (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/403808
Title:
Confirmed in natty. To reproduce, enable more than a couple of jails in
jail.conf and do a restart of the service.
** Changed in: fail2ban (Ubuntu)
Status: Incomplete = New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Again, patch proposed in #2 does fix the issue reliably, at least on
every system I've applied it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/403808
Title:
fail2ban not execute command to start
Why is it marked incomplete, following a request for more info based on
a version which is not yet released? The bug is present in lucid and
maverick, there is a workaround and the info for reproducing are
present...
Anyway, I'm going to test it on natty ASAP.
--
You received this bug
Hi, Can anyone confirm if this bug is present in Natty please?
** Changed in: fail2ban (Ubuntu)
Status: New = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/403808
Title:
fail2ban
Bug still present in Maverick. Proposed workaround (patching /usr/bin
/fail2ban-client) does solve the problem.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/403808
Title:
fail2ban not execute
The sleep(0.1) described above
(https://bugs.launchpad.net/ubuntu/+source/fail2ban/+bug/403808/comments/2)
appears to work on both my Karmic and Lucid boxes. I don't mind adding
a few seconds to booting. But this does seem like a brittle fix. A
better solution would be a handshake with a finite
I was getting the same behavior as the reporter of this bug (Mike) and
when I finally found this page and realized that this is an bug of
fail2ban itself. My system is Ubuntu 10.04 with 0.8.4-1ubuntu1 version
of the fail2ban package for Ubuntu.
I just added the time.sleep(0.1) line to
I was trying to nominate this for lucid and mistakenly nominated for
past releases. I do not see how I can remove nominations for the older
releases after I have nominated them. I see that this has already been
nominated for Karmic and Lucid by the fail2ban team.
--
fail2ban not execute command
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
** Tags removed: fail2ban
--
fail2ban not execute command to start jail
https://bugs.launchpad.net/bugs/403808
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Invalidated wrongly set tasks.
@ Fail2Ban: Please do not add new tasks to bug reports or nominate for release
without commenting to advise why you have done this.
Thanks in advance!
** Changed in: iptables (Ubuntu)
Status: New = Invalid
** Changed in: fail2ban (Arch Linux)
** Tags added: fail2ban
** Also affects: fail2ban (Debian)
Importance: Undecided
Status: New
** Also affects: fail2ban (Mandriva)
Importance: Undecided
Status: New
** Also affects: fail2ban (Suse)
Importance: Undecided
Status: New
** Also affects: fail2ban (Arch
16 matches
Mail list logo
