I forgot to mention... our neither our z2.log or stupid_log show anything upon freezing. afterwards the stupid_log shows the failed transaction cleanup, but that's it.
Hmmm... it might be useful to turn on detailed request logging (-M logging) in the start file (see z2.py). Attached is a script that I just checked into the trunk to do analysis of the file generated by the -M log. It can help you figure out if there's a pattern to the hangs (whether it happens on a particular method, whether it happens at heavy load time, whether it happens at a particular time of day, etc.) Do you think you'd be willing to play around with it a little bit to try to discover a pattern?
Tim
-----Original Message----- From: Tim McLaughlin Sent: Friday, April 27, 2001 12:41 PM To: 'zope-dev@zope.org'; 'chrisw@nipltd.com' Subject: [Zope-dev] Zope Server hanging :-(
Chris (and all),
We seem to be having similar crashing issues. And interestingly enough, they don't seem to show up on any of our servers except the 2.3.0 upgraded to 2.3.1.
1. Hangs on anything from Pythonscript or dtml 2. top shows no significant mem or cpu usage 3. threads are all unresponsive 4. restart usually yields a .trX file (an aborted transaction I suppose)
Any ideas? Maybe it was something "fixed" in 2.3.1? The causes seem to
be
somewhat different except that they all modify the ZODB....
Tim
_______________________________________________ Zope-Dev maillist - Zope-Dev@zope.org http://lists.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope )