As Matt LaPlante pointed out above, this should be eligible for a SRU,
as the bug is a regression from a previous version
--
fail2ban fails to start after reboot
https://bugs.launchpad.net/bugs/222804
You received this bug notification because you are a member of Ubuntu
Server Team, which is a
This is actually fixed in 0.8.2-3 in Intrepid, so I'm marking it as Fix
Released as per the bug triage process. If you want it in Hardy, someone
needs to add a milestone I think, and I don't know how to do that
** Changed in: fail2ban (Ubuntu)
Status: Confirmed = Fix Released
--
fail2ban
ISSUE: fail2ban does not restart after reboot because of /var/run being
a tmpfs, so no pid file can be created. I have attached the debdiff
which fixes this issue. This has been backported from intrepid.
TEST CASE:
1. Install fail2ban
2. Reboot
3. Restart fail2ban after reboot see if it starts.
** Changed in: fail2ban (Ubuntu)
Status: Confirmed = Fix Released
** Changed in: fail2ban (Ubuntu Hardy)
Status: New = In Progress
--
[SRU] fail2ban fails to start after reboot
https://bugs.launchpad.net/bugs/222804
You received this bug notification because you are a member of
Set to HIGH, because this is a security tool, and you can feel that it's
working, but not !
** Changed in: fail2ban (Ubuntu)
Importance: Undecided = High
--
fail2ban fails to start after reboot
https://bugs.launchpad.net/bugs/222804
You received this bug notification because you are a member
As Matt LaPlante pointed out above, this should be eligible for a SRU,
as the bug is a regression from a previous version
--
fail2ban fails to start after reboot
https://bugs.launchpad.net/bugs/222804
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
This is actually fixed in 0.8.2-3 in Intrepid, so I'm marking it as Fix
Released as per the bug triage process. If you want it in Hardy, someone
needs to add a milestone I think, and I don't know how to do that
** Changed in: fail2ban (Ubuntu)
Status: Confirmed = Fix Released
--
fail2ban
** Changed in: fail2ban (Ubuntu)
Status: Fix Released = Confirmed
--
fail2ban fails to start after reboot
https://bugs.launchpad.net/bugs/222804
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ISSUE: fail2ban does not restart after reboot because of /var/run being
a tmpfs, so no pid file can be created. I have attached the debdiff
which fixes this issue. This has been backported from intrepid.
TEST CASE:
1. Install fail2ban
2. Reboot
3. Restart fail2ban after reboot see if it starts.
** Changed in: fail2ban (Ubuntu)
Status: Confirmed = Fix Released
** Changed in: fail2ban (Ubuntu Hardy)
Status: New = In Progress
--
[SRU] fail2ban fails to start after reboot
https://bugs.launchpad.net/bugs/222804
You received this bug notification because you are a member of
Ok, so what do we do now? It's still is not fixed. It works for me
when I install, but when I reboot the server it's broken.
--
fail2ban fails to start after reboot
https://bugs.launchpad.net/bugs/222804
You received this bug notification because you are a member of Ubuntu
Bugs, which is
David, Matt:
It looks like this fix has been released in Debian unstable. It doesn't
look like this is going to make it into hardy, unless someone manages to
get it through the SRU process:
https://wiki.ubuntu.com/StableReleaseUpdates
In the meantime, I've simply downloaded the Debian package
I see no reason this shouldn't meet the SRU requirements. Particularly, this
one:
- Bugs which represent severe regressions from the previous release of Ubuntu.
This includes packages which are totally unusuable, like being uninstallable or
crashing on startup.
A program which doesn't start
Here's my patch for this, for those who can't wait for 0.8.2-3 to be
released.
Note that this is only the second ever patch I've written, so if it is
wrong, please point me to resources to help me improve.
There is also a further fail2ban bug #234122 for which I have written a
patch, which
Agreed, my systems have not seen this bug fixed yet either.
** Changed in: fail2ban (Ubuntu)
Status: Fix Released = Confirmed
--
fail2ban fails to start after reboot
https://bugs.launchpad.net/bugs/222804
You received this bug notification because you are a member of Ubuntu
Bugs, which
Please add this update to the Ubuntu archive for download. I removed
fail2ban on my system and then reinstalled it. Fail2Ban v0.8.2 with the
bug is still downloading, as of 05/16/08.
--
fail2ban fails to start after reboot
https://bugs.launchpad.net/bugs/222804
You received this bug
This appears to still not be fixed, as of this writing.
--
fail2ban fails to start after reboot
https://bugs.launchpad.net/bugs/222804
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
This bug was fixed in the package fail2ban - 0.8.2-3
---
fail2ban (0.8.2-3) unstable; urgency=low
* Changes propagated from upstream trunk (future 0.8.3):
- Fixed fail2ban-client get jail logpath. Bug #1916986.
- Changed some log level.
- Added Day/Month/Year
18 matches
Mail list logo
