Your message dated Fri, 29 Feb 2008 01:17:03 +0000 with message-id <[EMAIL PROTECTED]> and subject line Bug#468382: fixed in fail2ban 0.8.1-5 has caused the Debian Bug report #468382, regarding fail2ban uses 100% cpu on february 29 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.) -- 468382: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=468382 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems
--- Begin Message ---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
--- End Message ---
--- Begin Message ---Source: fail2ban Source-Version: 0.8.1-5 We believe that the bug you reported is fixed in the latest version of fail2ban, which is due to be installed in the Debian FTP archive: fail2ban_0.8.1-5.diff.gz to pool/main/f/fail2ban/fail2ban_0.8.1-5.diff.gz fail2ban_0.8.1-5.dsc to pool/main/f/fail2ban/fail2ban_0.8.1-5.dsc fail2ban_0.8.1-5_all.deb to pool/main/f/fail2ban/fail2ban_0.8.1-5_all.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to [EMAIL PROTECTED], and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Yaroslav Halchenko <[EMAIL PROTECTED]> (supplier of updated fail2ban package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing [EMAIL PROTECTED]) -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Format: 1.7 Date: Thu, 28 Feb 2008 19:51:53 -0500 Source: fail2ban Binary: fail2ban Architecture: source all Version: 0.8.1-5 Distribution: unstable Urgency: low Maintainer: Yaroslav Halchenko <[EMAIL PROTECTED]> Changed-By: Yaroslav Halchenko <[EMAIL PROTECTED]> Description: fail2ban - bans IPs that cause multiple authentication errors Closes: 468382 Changes: fail2ban (0.8.1-5) unstable; urgency=low . * manually "cherry picked" f6639981: Fixed "Feb 29" bug. Thanks to James Andrewartha who pointed this out. Thanks to Yaroslav Halchenko for the fix (closes: #468382) Files: 775394691d4dd433c160d86c1824c0a6 797 net optional fail2ban_0.8.1-5.dsc 93bba0e249fb9bde1f304d064a774c3b 27308 net optional fail2ban_0.8.1-5.diff.gz 866ed9c570409af0bacbf299d304887f 79722 net optional fail2ban_0.8.1-5_all.deb -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFHx1qyjRFFY3XAJMgRAqK/AJ9KgNDsg73UbWik/eu/GEVtqSuW2wCfe/uR /HZLDgzqq6d1Hjr2BEQiT7E= =/fMa -----END PGP SIGNATURE-----
--- End Message ---
