Hi Trishank,
did you try to run in debug mode to see what happens?
env SSHGUARD_DEBUG="" /usr/local/sbin/sshguard ...
The messages there are quite explicit: your blocking backend
fails with some error when run.
On Dec 28, 2009, at 22:56 , Trishank Karthik Kuppusamy wrote:
> Hello,
>
> I have sshguard-1.4 installed on OS X 10.6.2 with the "tail log" and
> "ipfw" setup.
>
> Every time I start sshguard, it would eventually exit in the near future.
> I think the following output may point to the reason:
>
> ...
> Dec 22 15:14:18 hostname sshguard[7993]: Releasing 121.52.215.180 after
> 466 seconds.
> Dec 22 15:15:27 hostname sshguard[7993]: Releasing 121.52.215.180 after
> 535 seconds.
> Dec 22 15:15:27 hostname sshguard[7993]: Release command failed. Exited: -1
> ...
> Dec 26 13:21:21 hostname sshguard[27412]: Releasing 220.162.241.11 after
> 441 seconds.
> Dec 26 13:22:06 hostname sshguard[27412]: Releasing 220.162.241.11 after
> 486 seconds.
> Dec 26 13:22:06 hostname sshguard[27412]: Release command failed. Exited: -1
> ...
>
> It appears to *sometimes* release, more than once, the same IP address.
> Could someone tell us whether this is expected behaviour?
> If not, then what is a solution?
> Thanks for your time.
>
> ------------------------------------------------------------------------------
> This SF.Net email is sponsored by the Verizon Developer Community
> Take advantage of Verizon's best-in-class app development support
> A streamlined, 14 day to market process makes app distribution fast and easy
> Join now and get one step closer to millions of Verizon customers
> http://p.sf.net/sfu/verizon-dev2dev
> _______________________________________________
> Sshguard-users mailing list
> Ssh...@li...
> https://lists.sourceforge.net/lists/listinfo/sshguard-users
|
