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

Thanks to Jim, Theune, Dieter and all others who weighed in on this thread. The problem: ZEO Clients would lock up randomly requiring restart. The hints: Lots of 'Connection timed out' and 'No route to host' in ZEO Server log files. The solution: The machine the ZEO server was running

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

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

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: (113, 'No

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

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 10 Apr 2007, at 20:19, Alan Runyan wrote: 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') File

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

ETHERNET CARD: 05:00.0 Ethernet controller: Broadcom Corporation NetXtreme II BCM5708 Gigabit Ethernet (rev 11) - I have turned down transaction timeout to 15 seconds. - I currently have 11 ZEO Clients up; but showing below (seems strange) sometimes the clients are 6 or 7.. - Have not

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

Alan Runyan wrote: Do you have anything that is committing very large transactions? No. In fact; these clients could be running in read only mode. As far as I'm concerned. How does data get into the ZEO storage then? cheers, Chris -- Simplistix - Content Management, Zope Python

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

How does data get into the ZEO storage then? We have 10 ZEO clients that are for public consumption READ ONLY. We have a separate ZEO client that is writing that is on a separate box. The website got slashdoted this morning and we had 4 zeo clients go out. Basically waiting for the zeo server

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

Alan Runyan wrote: The website got slashdoted this morning [...] Just FYI: Varnish didnt go over 3% CPU during the traffic surge; over 200 req/second. Off topic: 200 requests a second seems a bit light for a slashdotting, any more details you can divulge there? -- Benji York Senior

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

On Apr 10, 2007, at 2:19 PM, Alan Runyan wrote: ... For Jim: We did not adjust the transaction timeout. Would that have helped in the case of READ's? Possibly, I'm not sure and I don't have time now to dig. It might be worth trying, however: The customer was posting content throughout

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

Alan Runyan wrote: We have 10 ZEO clients that are for public consumption READ ONLY. We have a separate ZEO client that is writing that is on a separate box. I'd put money on the client doing the writing causing problems. That or client side cache thrash caused by zcatalog or similar ;-) The

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

I'ev not had anything but bad experiences with pound myself, lvs seems a much more preferable alternative... We have not had such negative experiences with pound. data = self.socket.recv(buffer_size) error: (113, 'No route to host') That *is* very odd, anything other than pound being

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

Alan Runyan wrote: data = self.socket.recv(buffer_size) error: (113, 'No route to host') That *is* very odd, anything other than pound being used for load balancing or traffic shaping? This has to be a major problem maker in the system. Pound is simply round robin connections to pool of

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

On 10 Apr 2007, at 21:39, Chris Withers wrote: I'd look at the switches and maybe even the nics and cables :-S And if you are doing that, also check your network to make sure all IP addresses are unique. (..but I'm not a sysadmin.) And neither am I! --r Russ Ferriday - Topia Systems -

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

On Apr 3, 2007, at 4:13 PM, Alan Runyan wrote: Hi guys. Running Zope 2.9.6 with ZODB 3.6.2 on Python 2.4 Having lots of lockups. Still? ... typical client zeo configuration: May We see the ZEO config? Jim -- Jim Fulton mailto:[EMAIL PROTECTED]

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

Hi guys. Running Zope 2.9.6 with ZODB 3.6.2 on Python 2.4 Having lots of lockups. Have approximately 12 zeo clients on 2 machines connecting to a single zeo server. All on local network. Disks and network is monitored by competent hosting company. All looks healthy except zeo communication.