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



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to