On Apr 12, 2007, at 1:17 PM, Alan Runyan wrote:

I find the 'No route to host' disturbing although
these have not happened over the past 24 hours.  This has:
2007-04-12T00:17:45 ERROR ZEO.zrpc.Connection(S)
( Error caught in asyncore
Traceback (most recent call last):
File "/usr/local/python-2.4.4/lib/python2.4/asyncore.py", line 69, in read
 File "/usr/local/python-2.4.4/lib/python2.4/asyncore.py", line 391,
in handle_read_event
File "/usr/local/zope/lib/python/ZEO/zrpc/smac.py", line 147, in handle_read
   d = self.recv(8192)
File "/usr/local/python-2.4.4/lib/python2.4/asyncore.py", line 343, in recv
   data = self.socket.recv(buffer_size)
error: (110, 'Connection timed out')

which is frustrating.  as i understand zeoserver is taking too long to
communicate to zeoclient and zeoclient times out.

I don't know what the source of the "Connection timed out'" error is. The error at this point in the code is very puzzline. There has been a select call and select returned indicating that the socket was ready to be read. There should be no delay at all. That's the whole point of using an asynchronous network library.

  shouldnt it retry /

The server is closing the connection with the client, which should cause the client to reconnect.

Do you see any log messages on the clients at times corresponding to these server log messages?


Jim Fulton                      mailto:[EMAIL PROTECTED]                Python 
CTO                             (540) 361-1714                  
Zope Corporation        http://www.zope.com             http://www.zope.org

For more information about ZODB, see the ZODB Wiki:

ZODB-Dev mailing list  -  [EMAIL PROTECTED]

Reply via email to