Your message dated Thu, 27 May 2010 07:47:18 -0400
with message-id <[email protected]>
and subject line Re: Bug#496633: fail2ban: Does not start
has caused the Debian Bug report #496633,
regarding fail2ban: Does not start
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
496633: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=496633
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: fail2ban
Version: 0.8.3-1
Severity: important
fail2ban fails to start.
To do some testing I reinstalled it afther I had removed and purged the
package. but it didn't help.
The log-file is completely empty. Log level 4 (debug) doesn't help either. It's
still empty.
If I do "/etc/init.d/fail2ban restart" I get a message stating that
/var/run/fail2ban/fail2ban.sock
is present, and a "Failed". If I remove that file and then do
"/etc/init.d/fail2ban start" the error
is gone, but fail2ban is still not in the process list, and there is no entries
in the log file.
If I execute "fail2ban-server -x" I get:
2008-08-26 11:45:18,901 fail2ban.server : INFO Starting Fail2ban v0.8.3
2008-08-26 11:45:18,909 fail2ban.server : INFO Starting in daemon mode
And then fail2ban-server is present in the process list, but no enties in the
log file.
After a reboot it's the same again. No log entries and no fail2ban in the
process list.
-- System Information:
Debian Release: lenny/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: arm (armv5tel)
Kernel: Linux 2.6.25-2-ixp4xx
Locale: LANG=sv_SE.UTF-8, LC_CTYPE=sv_SE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages fail2ban depends on:
ii lsb-base 3.2-19 Linux Standard Base 3.2 init scrip
ii python 2.5.2-2 An interactive high-level object-o
ii python-central 0.6.8 register and build utility for Pyt
Versions of packages fail2ban recommends:
ii iptables 1.4.1.1-2 administration tools for packet fi
ii whois 4.7.27 an intelligent whois client
Versions of packages fail2ban suggests:
ii bsd-mailx [mailx] 8.1.2-0.20071201cvs-3 A simple mail user agent
ii mailx 1:20071201-3 Transitional package for mailx ren
pn python-gamin <none> (no description available)
-- no debconf information
--- End Message ---
--- Begin Message ---
Thank you Stefan for following up -- closing the bug report then ;)
Cheers!
On Thu, 27 May 2010, Stefan Carslöv wrote:
> Hi Yaroslav
> Yes, the issue is resolved. I didn't even know that the bug was still open :)
> I'm now using python 2.5.4-9 and fail2ban 0.8.4-2 on Debian Testing.
> /Stefan
> > Hi Stefan,
> > Could you please check once again either you keep experiencing this
> > issue you have reported long time ago? May be it is gone by now and I
> > could close this bugreport ;)
> > since last 2 years, there even was a new upstream release ;)
--
.-.
=------------------------------ /v\ ----------------------------=
Keep in touch // \\ (yoh@|www.)onerussian.com
Yaroslav Halchenko /( )\ ICQ#: 60653192
Linux User ^^-^^ [175555]
--- End Message ---
