|
thanks, this was the problem. This is occurring once in
a while. James Abbatiello wrote: Since the exception is being caught and reraised the exact line number of the crash is not present in the traceback. My best guess is that the very last line in your HOSTS_DENY file (/etc/hosts.deny or /etc/hosts.evil or whatever you use) looks like # DenyHosts: <timestamp> | <IP> and the actual line banning that IP that is supposed to appear immediately afterward is not there. If this is the case you should be able to add the missing line back in by hand. Or you can delete the comment line but then DenyHosts might add the entry back in on the next run and you'd have the wrong timestamp on it.In the long term, create_temp should be changed to check that it isn't running off the end of the array and that catch-and-reraise should probably be removed to improve future tracebacks. |
------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________ Denyhosts-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/denyhosts-user
