*** This bug is a duplicate of bug 222804 ***
https://bugs.launchpad.net/bugs/222804
fai2ban appears corrected in Hardy, see:
https://bugs.launchpad.net/ubuntu/hardy/+source/fail2ban/+bug/222804
** This bug has been marked a duplicate of bug 222804
[SRU] fail2ban fails to start after reboo
fail2ban appears to be working fine in Intrepid. Unlike 8.04, I do not
have to manually create /var/run/fail2ban to get it started.
--
fail2ban will not start if fail2ban socket is present
https://bugs.launchpad.net/bugs/123916
You received this bug notification because you are a member of Ubunt
Ubuntu is getting worse and worse. This bug bit me too. It was all
working fine but after a reboot, it stopped working and I only noticed
because there where so many failed authentication attempts in the
logfiles.
And again, just like the bug with software raid that makes your machine
unbootable,
I took Yaroslav's package from Debian and build it in my ppa.
You could find it there :
https://launchpad.net/~stemp/+archive
http://launchpadlibrarian.net/16991842/fail2ban_0.8.3-2_all.deb
--
fail2ban will not start if fail2ban socket is present
https://bugs.launchpad.net/bugs/123916
You receive
I can verify that fail2ban still doesn't start properly.
/var/run/fail2ban is not being created on startup so fail2ban will not
start until this directory is created. Is there some problem preventing
the sync of the debian package into ubuntu repos? This would seem to be
an easy fix for the probl
guys -- how long would you keep chating before you simply sync from
Debian 0.8.2-3:
* Assure that /var/run/fail2ban exists upon start (LP: #222804, #223706)
On Sat, 17 May 2008, schnollk wrote:
> I understand this is not a security vulnerability but since it is highly
> security relevant I sug
I just noticed while skimming /etc/init.d/fail2ban that line 204 reads
'0) log_success_msg " $NAME is running" ;;' but
$ egrep 'is .* running' /var/log/fail2ban.log; echo $?
1
but don't have any more time to find why it's never called...
--
fail2ban will not start if fail2ban socket is presen
I understand this is not a security vulnerability but since it is highly
security relevant I suggest to put high importance on this bug. I would
have done it myself but cannot see how or am not allowed to.
--
fail2ban will not start if fail2ban socket is present
https://bugs.launchpad.net/bugs/12
Confirmed (using stop && rm -r && start and also using reload). After
creating
$ sudo mkdir /var/run/fail2ban
as suggested it works.
Very annoying is that fail2ban does not seam to be very talkative
(except when log level 4 -- 3 is default -- AND everything going well;
failure -> not even anythi
Have you tried to run 'sudo mkdir /var/run/fail2ban' before starting
fail2ban and see if it helps?
--
fail2ban will not start if fail2ban socket is present
https://bugs.launchpad.net/bugs/123916
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscri
fail2ban is still not working on Hardy 8.04...
For persons that have personnal servers, this feature was more important
than some policykit (sudo was simple and efficient; the wireless network
did not have to wait for a key unlocked by login password...) and
apparmor bullshit: Linux is not Vista..
me? not exactly. it was aimed to be like that: if for some reason
socket is present while application is not running -- there could have
been some abrupt interruption of the process -- and the admin has to
check WTF and may be fix the cause, clean up leftovers of fail2ban's
operation (altered /etc/
On Mon, Oct 15, 2007 at 09:48:07PM -, Nicolas Valcárcel wrote:
> In this bug it would be better to patch the "/etc/init.d/fail2ban" or
> make that on crash it remove the socket?
Init-script definitely. If an application crashes, it's usually pretty
difficult to tell it to clean up after itself
In this bug it would be better to patch the "/etc/init.d/fail2ban" or
make that on crash it remove the socket?
--
fail2ban will not start if fail2ban socket is present
https://bugs.launchpad.net/bugs/123916
You received this bug notification because you are a member of Ubuntu
Bugs, which is a dir
By the way, if you try to "restart" instead of start it, does it work?
--
fail2ban will not start if fail2ban socket is present
https://bugs.launchpad.net/bugs/123916
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing
Thanks for taking the time to report this bug and helping to make Ubuntu
better. I have unmarked it as a security issue since this bug does not
show evidence of allowing attackers to cross privilege boundaries nor
directly cause loss of data/privacy. Please feel free to report any
other bugs you ma
16 matches
Mail list logo
