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/)
