I haven't seen any issues with daemons dying on any of the servers I
admin, so not sure on the exact cause.
FYI: for about 3 weeks, my internet connection had become increasingly
problematic (requiring my gateway device to be rebooted more-and-more
often-- as many as 20x an hour on Friday alone).
I replaced the faulty network device on Saturday and the connection should
be far more stable now.
So if the daemon dying has something to do with the connection being reset
after the connection had been established then the device replacement
may cure this issue. I know that if the connection can't be established
than the DH client logs the error and continues, however, not sure what
the xmlrpc layer does if the connection is successful but it is terminated
ungracefully (if it doesn't propagate an error condition and continues to
poll for data then perhaps this causes the daemon to hang). Obviously,
I'm speculating here because I haven't seen this issue myself.
Phil
On Mon, 9 Jun 2008, Robert Hardy wrote:
On Fri, 6 Jun 2008, René Berber wrote:
More info, with some debug data...
Today it happened again, DH got stuck and the log shows the lines we
have been seeing:
2008-06-06 19:24:02,597 - denyhosts : DEBUG no new denied hosts
2008-06-06 19:24:02,597 - denyhosts : DEBUG no new suspicious logins
That's as far as I have gone. Anyone with good ideas on how to continue
debugging this?
DH is hanging during either receiving hosts via xmlrpc or sending hosts via
xmlrpc. In your case it seems to hang in sending hosts, in mine (since I have
sending disabled) it hangs in receiving hosts.
It should timeout and keep going gracefully but it obviously doesn't. You
seem to get more debugging output with python 2.5, but I'm seeing the same
problem with python 2.4 and python 2.3.
The xmlrpc docs I've found so far are less than helpful in terms of
debugging the issue. I suspect the one obvious workaround is to disable
synchronization to avoid the hangs. I've now done this on all of my hosts.
It will probably take a week to tell if this solves the issue.
If it solves the problem I think I'll just leave syncronization disabled
everywhere. It's a nice feature, but if it's broken and the software does
the job without it, why enable it?
Regards,
Rob
-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
Denyhosts-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/denyhosts-user
