I'm experiencing occasional lockups of ZServer (currently being used in conjuction with PCGI and Apache). When this happens, I get no response at all from the http interface (Netscape eventually times out and says the document contains no data). I've looked in the ZServer log file, and the last entry corresponds to the last successful request that was served. When I kill z2.py, I get the following: Traceback (innermost last): File "z2.py", line 355, in ? zdaemon.run(sys.argv, os.path.join(INSTANCE_HOME, Zpid)) File "/home/controlpanel/Zope-2.0.0a4-src/lib/python/zdaemon.py", line 202, in run p,s = os.waitpid(pid, 0) KeyboardInterrupt Can any of the Zope gurus who have a better understanding of the Zope internals help to diagnose this problem? I'm using 2.0.0a4, and plan to upgrade to the latest beta this afternoon to see if that helps. Thanks, -jason ----------------- Jason Abate jason@hostway.com Hostway, Inc.
I'm experiencing the same kind of problems, although I'm using the Zope server (no Apache)... Netscape seems to lock up waiting for data infinitely. I can usually get around this problem by re-clicking on a url a couple of times, which resolves the problem for the moment. But after ZServer has gone into this state, it locks up again and again until ZServer is restarted... I'm using Zope-2.0.0b3-linux2-x86. jonas On Tue, Aug 10, 1999 at 12:33:56PM -0500, jason@brahms.siteprotect.com wrote:
I'm experiencing occasional lockups of ZServer (currently being used in conjuction with PCGI and Apache). When this happens, I get no response at all from the http interface (Netscape eventually times out and says the document contains no data).
I encounter the same problems from time to time. stephan On Wed, 11 Aug 1999, you wrote:
I'm experiencing the same kind of problems, although I'm using the Zope server (no Apache)... Netscape seems to lock up waiting for data infinitely. I can usually get around this problem by re-clicking on a url a couple of times, which resolves the problem for the moment. But after ZServer has gone into this state, it locks up again and again until ZServer is restarted... I'm using Zope-2.0.0b3-linux2-x86.
jonas
On Tue, Aug 10, 1999 at 12:33:56PM -0500, jason@brahms.siteprotect.com wrote:
I'm experiencing occasional lockups of ZServer (currently being used in conjuction with PCGI and Apache). When this happens, I get no response at all from the http interface (Netscape eventually times out and says the document contains no data).
_______________________________________________ Zope maillist - Zope@zope.org http://www.zope.org/mailman/listinfo/zope
(To receive general Zope announcements, see: http://www.zope.org/mailman/listinfo/zope-announce
For developer-specific issues, zope-dev@zope.org - http://www.zope.org/mailman/listinfo/zope-dev ) -- Stephan Richter iXL - Software Designer and Engineer
... Me too. I'm using CVS latest under Win32 with a testing script that uses tcl to grab various docs off the server on the same machine. Occasionally it locks up ZServer; what should one do when this happens to try and figure out what's going on? -- Robin Becker
At 11:23 AM 8/11/99 +0300, Jonas Juselius wrote:
I'm experiencing the same kind of problems, although I'm using the Zope server (no Apache)... Netscape seems to lock up waiting for data infinitely. I can usually get around this problem by re-clicking on a url a couple of times, which resolves the problem for the moment. But after ZServer has gone into this state, it locks up again and again until ZServer is restarted... I'm using Zope-2.0.0b3-linux2-x86.
jonas
On Tue, Aug 10, 1999 at 12:33:56PM -0500, jason@brahms.siteprotect.com wrote:
I'm experiencing occasional lockups of ZServer (currently being used in conjuction with PCGI and Apache). When this happens, I get no response at all from the http interface (Netscape eventually times out and says the document contains no data).
A number of folks have posted about Zope lock up issues. It is very important to me to resolve this issues. If any of you can reproduce a Zope lock up, please, please, please, submit this issue to the Collector, ASAP. Tracking down problems like these can be difficult. There are lots of things that can go wrong which could cause Zope to stop responding, for example serious problems in any of these areas could halt Zope: * ZServer * The Zope process itself * The object database When ZServer occasionally locks up for me, it usually because I did something that's causing the publishing process to hang. This happens when you are coding external methods or Python products and make certain kinds of mistakes that put Zope in a loop. If ZServer itself breaks usually you will get something written to the info log, or else ZServer will exit with a traceback. If you suspect that ZServer is the problem try running it with the -D switch so that the info logging goes to the STDOUT and so you can read the traceback in case it exits. If you think that your object database is messed up you can test things by using the scripts in the utilities directory. You can also use the monitor to poke around at objects and check out if their state is weird. In general if you've got an object database problem you should still be able to connect to the ZServer monitor and ftp servers which does not immediately rely on the object database. If Zope is completely unresponsive, then there's not a lot you can do except kill the process. If you can kill it in the foreground with a control-c then you will get a traceback which may give you some clue as to what was wrong. So to reiterate: If you can reproduce a lockup submit it to the Collector. If you are developing external methods or Products there is a good chance the your code is causing the problem. If not, poke around and see what you can find, and post your findings to the Zope list, with enough information we should be able to solve the problem. Good luck! -Amos
Amos Latteier wrote:
A number of folks have posted about Zope lock up issues. It is very important to me to resolve this issues.
I just checked in a fix for a bug that can cause ZServer to hang when there are competing write requests. If you are using the Zope public CVS, you should update ZServer/HTTPResponse.py to revision 1.9. This bug does not explain the problems reported involving just reads. Jim -- Jim Fulton mailto:jim@digicool.com Python Powered! Technical Director (888) 344-4332 http://www.python.org Digital Creations http://www.digicool.com http://www.zope.org Under US Code Title 47, Sec.227(b)(1)(C), Sec.227(a)(2)(B) This email address may not be added to any commercial mail list with out my permission. Violation of my privacy with advertising or SPAM will result in a suit for a MINIMUM of $500 damages/incident, $1500 for repeats.
participants (6)
-
Amos Latteier -
jason＠brahms.siteprotect.com -
Jim Fulton -
Jonas Juselius -
Robin Becker -
Stephan Richter