Package: fail2ban Version: 0.9.1-1 Severity: normal I've had fail2ban segfaulting yesterday (in libsqlite3; probably not worth a bug report, since I couldn't reproduce it). Anyway, fail2ban is no longer running[*], so let's restart it:
# service fail2ban start [....] Starting authentication failure monitor: fail2ban[....] Socket file /var/[FAILail2ban/fail2ban.sock is present ... failed! failed! Yeah, I doubt it had the occasion to remove the socked file before segfaulting. Nevertheless, the process is no longer running: # kill -0 `cat /var/run/fail2ban/fail2ban.pid` bash: kill: (24147) - No such process Shouldn't the init script automatically ignore/remove the socket file if the process in the PID file is no longer running? Isn't that what PID files are for? This is probably the first time I remember having to manually do something before restarting a server after a simple crash. [*] Maybe this wouldn't be a problem if I was running systemd? :) -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (x86_64) Foreign Architectures: amd64 Kernel: Linux 3.16-2-amd64 (SMP w/3 CPU cores) Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages fail2ban depends on: ii init-system-helpers 1.22 ii lsb-base 4.1+Debian13+nmu1 ii python3 3.4.2-1 pn python3:any <none> Versions of packages fail2ban recommends: ii iptables 1.4.21-2+b1 pn python3-pyinotify <none> ii whois 5.2.2 Versions of packages fail2ban suggests: ii bsd-mailx [mailx] 8.1.2-0.20140825cvs-1 pn python3-systemd <none> ii rsyslog [system-log-daemon] 8.4.2-1 -- Configuration Files: /etc/fail2ban/action.d/iptables-blocktype.conf b322783b061a2e3d4412fa2f523fc69c [Errno 2] No such file or directory: u'/etc/fail2ban/action.d/iptables-blocktype.conf b322783b061a2e3d4412fa2f523fc69c' -- no debconf information -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
