Package: fail2ban
Version: 0.7.5-2etch1
Severity: important
Starting at 12am on February 29, fail2ban started taking 100% CPU.
Successive restarts did nothing, and the same is happening on another
machine as well. strace isn't helpful, it just reports:
gettimeofday({1204217132, 583543}, NULL) = 0
futex(0x81522b0, FUTEX_WAKE, 1) = 0
select(0, NULL, NULL, NULL, {0, 50000}) = 0 (Timeout)
futex(0x81522b0, FUTEX_WAIT, 0, NULL) = 0
futex(0x81522b0, FUTEX_WAKE, 1) = 0
over and over again.
-- System Information:
Debian Release: 4.0
APT prefers stable
APT policy: (900, 'stable'), (400, 'testing')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.21.3madako1
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Versions of packages fail2ban depends on:
ii iptables 1.3.6.0debian1-5 administration tools for packet fi
ii lsb-base 3.1-23.2etch1 Linux Standard Base 3.1 init scrip
ii python 2.4.4-2 An interactive high-level object-o
ii python-central 0.5.12 register and build utility for Pyt
ii python2.4 2.4.4-3 An interactive high-level object-o
fail2ban recommends no packages.
-- no debconf information
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
