The thing to do here is to turn on "big M" logging (use the -M switch to z2.py)... this details all the transactions between clients and Zope. Then use the "requestprofiler.py" script that ships with Zope 2.4 (in the "utilities" directory) to give you a profile of the big M logs for the right before a hang... do this for a few days to determine if you can spot a pattern to the hangs. Roman V. Isaev wrote:
A glitch :( It happens in zope 2.3.3 (python 1.5.2) and zope 2.4.0 (python 2.1.1) under OpenBSD 2.7. After a day or two of normal work zope simply stops responding to HTTP requests. When I telnet to 80 port it connects, but nothing else happens. What to do? How to know where it handgs and why? Is it possible to attach to zope process and see what's going there?..
-- Chris McDonough Zope Corporation http://www.zope.org http://www.zope.com "Killing hundreds of birds with thousands of stones"