Your message dated Sat, 16 Feb 2008 12:17:06 +0000 with message-id <[EMAIL PROTECTED]> and subject line Bug#439962: fixed in fail2ban 0.7.5-2etch1 has caused the Debian Bug report #439962, regarding fail2ban might deadlock, taking cron.daily with it 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.) -- 439962: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=439962 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems
--- Begin Message ---Package: fail2ban Version: 0.7.5-2 Severity: critical For whatever reason, my fail2ban process is hung in a deadlock: seamus:/etc/init.d> sudo strace -p 11867 Process 11867 attached - interrupt to quit futex(0x81dbef0, FUTEX_WAIT, 0, NULL As a result, fail2ban-client reload will indefinitely wait: seamus:/etc/init.d> sudo strace python2.4 /usr/bin/fail2ban-client reload [...] socket(PF_FILE, SOCK_STREAM, 0) = 3 connect(3, {sa_family=AF_FILE, path="/tmp/fail2ban.sock"}, 20 This again causes the logrotate postrotate script to hang, which causes logrotate to hang, which causes cron.daily to hang. seamus:/etc/init.d> ps aux | grep -c fail2ban-client 11 seamus:/etc/init.d> ps aux | grep -c logrotate 22 seamus:/etc/init.d> ps aux | grep -c cron.daily 41 Undoubtedly, cron.daily or logrotate could use timeouts. Until they do, this is a critical bug in fail2ban because it breaks unrelated software. -- System Information: Debian Release: 4.0 APT prefers stable APT policy: (500, 'stable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-4-686 Locale: LANG=en_GB, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) 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 -- .''`. martin f. krafft <[EMAIL PROTECTED]> : :' : proud Debian developer, author, administrator, and user `. `'` http://people.debian.org/~madduck - http://debiansystem.info `- Debian - when you have better things to do than fixing systems
digital_signature_gpg.asc
Description: Digital signature (see http://martin-krafft.net/gpg/)
--- End Message ---
--- Begin Message ---Source: fail2ban Source-Version: 0.7.5-2etch1 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.7.5-2etch1.diff.gz to pool/main/f/fail2ban/fail2ban_0.7.5-2etch1.diff.gz fail2ban_0.7.5-2etch1.dsc to pool/main/f/fail2ban/fail2ban_0.7.5-2etch1.dsc fail2ban_0.7.5-2etch1_all.deb to pool/main/f/fail2ban/fail2ban_0.7.5-2etch1_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: Tue, 01 May 2007 22:18:03 -0400 Source: fail2ban Binary: fail2ban Architecture: source all Version: 0.7.5-2etch1 Distribution: stable-security Urgency: high Maintainer: Yaroslav Halchenko <[EMAIL PROTECTED]> Changed-By: Yaroslav Halchenko <[EMAIL PROTECTED]> Description: fail2ban - bans IPs that cause multiple authentication errors Closes: 421848 434368 439962 Changes: fail2ban (0.7.5-2etch1) stable-security; urgency=high . * Propagated fix for asctime pattern from 0.7.8 release (closes: #421848) * Propagated fix for not closed log files from 0.7.8-1 (closes: #439962,434368) * Propagated fix for "reload" bug which is as sever as #439962 and just never was hit by any Debian user yet * Added patch 00_numeric_iptables-L to avoid possible DoS attacks (introduced upstream in 0.7.6) * Propagated "Fixed removal of host in hosts.deny" from 0.7.6, to prevent possible DoS * CVE-2007-4321: anchored sshd and vsftpd failregex at the end of line to prevent DoS on those services. This issue was resolved in sid's version 0.8.0-4 (bugreport 438187). Files: 67efd3e859d89b4b2d2e527ff09ac659 704 net optional fail2ban_0.7.5-2etch1.dsc 36e65b8effcfd4f4a437d214613eb916 46075 net optional fail2ban_0.7.5.orig.tar.gz c1f185e48d340020de0651962fc34402 21899 net optional fail2ban_0.7.5-2etch1.diff.gz afb61355977afe99b2a807a6de03685f 63564 net optional fail2ban_0.7.5-2etch1_all.deb -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFHglRIjRFFY3XAJMgRAjewAKDWRMBLl0/ja2YmpKQ2/ySj0C9U2wCeJc6S 3NaT2m+1ROBy6Dmc+kY7Ues= =x0q5 -----END PGP SIGNATURE-----
--- End Message ---
