Re: [ZODB-Dev] more lockup information / zope2.9.6+zodb 3.6.2

2007-04-12 Thread Alan Runyan
> Storage: 1 > Server started: Wed Apr 11 10:56:50 2007 > Clients: 10 > Clients verifying: 0 > Active transactions: -1 Huh? You're owing the system a transaction. However, by looking at the code briefly, this might happen if tpc_abort() and _abort() kind of overlap. And you did have two aborts at

Re: [ZODB-Dev] more lockup information / zope2.9.6+zodb 3.6.2

2007-04-12 Thread Jim Fulton
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) (172.16.235.120:54881) Error caught in asyncore Traceback (most recent call last): File

Re: [ZODB-Dev] more lockup information / zope2.9.6+zodb 3.6.2

2007-04-12 Thread Dieter Maurer
Alan Runyan wrote at 2007-4-11 11:31 -0500: ... ZEO lockups ... PeterZ <[EMAIL PROTECTED]> reported today very similar problems in "[EMAIL PROTECTED]". He, too, gets: > File "/opt/zope/Python-2.4.3/lib/python2.4/asyncore.py", line 343, in recv >data = self.socket.recv(buffer_size) >error: (