Package: fail2ban
Version: 0.6.1-3
Severity: normal

When a more-or-less unconfigured fail2ban installation is started on this 
system, it fails to set up its rules, while 
putting this in its log:

2006-05-31 12:06:48,705 WARNING: Verbose level is 1
2006-05-31 12:06:48,732 INFO: Fail2Ban v0.6.1 is running
2006-05-31 12:06:48,739 INFO: Enabled sections: ['SSH']
2006-05-31 12:06:48,740 WARNING:  is not a valid IP address
2006-05-31 12:06:48,895 ERROR: unknown locale: en_DK
2006-05-31 12:06:48,896 ERROR: Please check the format and your locale settings.
2006-05-31 12:06:48,973 ERROR: Fail2Ban got an unhandled exception and died.
2006-05-31 12:06:48,973 ERROR: Type: 'AttributeError'
Value: ('strptime',)
TB: [('/usr/bin/fail2ban', 55, '?', 'fail2ban.main()'), 
('/usr/share/fail2ban/fail2ban.py', 513, 'main', 'e = 
element[1].getFailures()'), ('/usr/share/fail2ban/logreader/logreader.py', 143, 
'getFailures', 'for element in 
self.findFailure(line):'), ('/usr/share/fail2ban/logreader/logreader.py', 174, 
'findFailure', 'date = 
self.getUnixTime(timeMatch.group())'), 
('/usr/share/fail2ban/logreader/logreader.py', 216, 'getUnixTime', 'date = 
list(time.strptime(value, self.timepattern))')]
2006-05-31 12:06:48,996 WARNING: Restoring firewall rules...

Apparently fail2ban wants to know every locale out thereƃ, before trying 
anything with it?

This bug is somewhat related to #363391, as the remedy is somewhat similar:
# killall fail2ban
# LANG=en_US fail2ban


-- System Information:
Debian Release: testing/unstable
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.15-1-686
Locale: LANG=en_DK, LC_CTYPE=en_DK (charmap=ISO-8859-1)

Versions of packages fail2ban depends on:
ii  iptables                      1.3.3-2    Linux kernel 2.4+ iptables adminis
ii  lsb-base                      3.1-5      Linux Standard Base 3.1 init scrip
ii  python                        2.3.5-5    An interactive high-level object-o

fail2ban recommends no packages.

-- no debconf information

Reply via email to