Are you, by chance, using Intel E1000 NICs? See "Fighting the
hardware" in Jodok's write-up: http://www.lovelysystems.com/batlogg/
2007/03/30/the-decathlon-of-computer-science/
Stefan
On 10. Apr 2007, at 20:19, Alan Runyan wrote:
I am seeing something *very* strange in zeo.log:
2007-04-10T12:20:53 ERROR ZEO.zrpc.Connection(S)
(172.16.235.120:49351) Erro
r caught in asyncore
Traceback (most recent call last):
File "/usr/local/python-2.4.4/lib/python2.4/asyncore.py", line 69,
in read
obj.handle_read_event()
File "/usr/local/python-2.4.4/lib/python2.4/asyncore.py", line
391, in han
dle_read_event
self.handle_read()
File "/usr/local/zope/lib/python/ZEO/zrpc/smac.py", line 147, in
handle_re
ad
d = self.recv(8192)
File "/usr/local/python-2.4.4/lib/python2.4/asyncore.py", line
343, in rec
v
data = self.socket.recv(buffer_size)
error: (113, 'No route to host')
but several more of these:
2007-04-10T13:55:36 ERROR ZEO.zrpc.Connection(S)
(172.16.235.119:44322) Erro
r caught in asyncore
Traceback (most recent call last):
File "/usr/local/python-2.4.4/lib/python2.4/asyncore.py", line 69,
in read
obj.handle_read_event()
File "/usr/local/python-2.4.4/lib/python2.4/asyncore.py", line
391, in han
dle_read_event
self.handle_read()
File "/usr/local/zope/lib/python/ZEO/zrpc/smac.py", line 147, in
handle_re
ad
d = self.recv(8192)
File "/usr/local/python-2.4.4/lib/python2.4/asyncore.py", line
343, in rec
v
data = self.socket.recv(buffer_size)
error: (110, 'Connection timed out')
--
Anything that, in happening, causes itself to happen again,
happens again. --Douglas Adams
_______________________________________________
For more information about ZODB, see the ZODB Wiki:
http://www.zope.org/Wikis/ZODB/
ZODB-Dev mailing list - ZODB-Dev@zope.org
http://mail.zope.org/mailman/listinfo/zodb-dev
