From: Peter V. <sku...@gm...> - 2014-11-14 19:52:05
|
Hi all, anybody seeing/saw similar messages? Once this occur the SSH isn't accessible at least our Zabbix monitoring reporting that. Jun 4 21:31:43 server sshguard[8003]: Releasing <B0><EB><C0>^A after 1372366479 seconds. Jun 4 21:31:43 server sshguard[8003]: Setting environment: SSHG_ADDR=4;SSHG_ADDRKIND=4;SSHG_SERVICE=100. Jun 4 21:31:43 server sshguard[8003]: Run command "case $SSHG_ADDRKIND in 4) exec /sbin/iptables -D sshguard -s $SSHG_ADDR -j DROP ;; 6) exec /sbin/ip6tables -D sshguard -s $SSHG_ADDR -j DROP ;; *) exit -2 ;; esac": exited 1. Jun 4 21:31:43 server sshguard[8003]: Release command failed. Exited: -1 System information: - Debian Squeeze LTS - iptables 1.4.8-3 - sshguard 1.4-2 - linux-image 2.6.32-48squeeze8 Was this bug fixed already? Are the IPs checked for validity before they are blocked? Could be that it was related to some bug in kernel. Sorry for a little late reporting. Hope that somebody would be able to explain what could happen and make us sure all is fixed in new versions. -- Peter Viskup |