Just wondering if this is what other people are seeing. Frequently (once a day?), ZServer goes out to lunch and I get the following error message: (102) failure during connect <!-- Connection refused pcgi-wrapper-version 2.0a5 --> or sometimes, ZServer will completely die and the non-ZServer version of Zope will start instead (what is it called, pcgi publisher?) which of course has the wrong content because I am working on ZServer/ODB3. In my apache error log, this is the last entry: [Wed Jul 14 19:27:51 1999] [error] [client 206.183.203.132] Premature end of script headers: /home/sites/home/web/zope/cgi-bin/Zope.cgi I have to manually restart z2.py to get it back. I am starting Z2.py with the -Z option to start the watcher thread, which apparently isn't working or doesn't think ZServer is having problems. Is this because it's still Alpha? Currently, ZServer dies way too often to use in a production site. Here is the command I'm using to start Zope: python z2.py -u zope -Z var/mgr.pid & Is this the correct usage of the -Z option? I'm currently using Zope 2.0a4 on Linux/mips. Thanks, Alex Rice | alrice@swcp.com | http://www.swcp.com/~alrice Current Location: N. Rio Grande Bioregion, Southwestern USA
At 08:15 PM 7/14/99 -0600, Alex Rice wrote:
Just wondering if this is what other people are seeing. Frequently (once a day?), ZServer goes out to lunch and I get the following error message:
(102) failure during connect <!-- Connection refused pcgi-wrapper-version 2.0a5 -->
This error means that the pcgi wrapper cannot connect to the pcgi server.
or sometimes, ZServer will completely die and the non-ZServer version of Zope will start instead (what is it called, pcgi publisher?) which of course has the wrong content because I am working on ZServer/ODB3.
You can prevent this by not including information about the pcgi publisher in your PCGI info file. All you really need when using ZServer as your pcgi publisher is the pid file and the socket file directives. You don't need the pcgi publisher and pcgi exe directives.
In my apache error log, this is the last entry:
[Wed Jul 14 19:27:51 1999] [error] [client 206.183.203.132] Premature end of script headers: /home/sites/home/web/zope/cgi-bin/Zope.cgi
All this means is that the pcgi wrapper failed.
I have to manually restart z2.py to get it back. I am starting Z2.py with the -Z option to start the watcher thread, which apparently isn't working or doesn't think ZServer is having problems.
Hmm. When you start ZServer does a zdaemon process start? Do you get any logging messages from zdaemon.
Is this because it's still Alpha? Currently, ZServer dies way too often to use in a production site.
I've found ZServer to be fairly stable. My goal is to have is pretty darn solid by the time Zope 2 is final. Clearly you are having problems, but without more information, it's hard to tell what is responsible.
Here is the command I'm using to start Zope: python z2.py -u zope -Z var/mgr.pid &
Is this the correct usage of the -Z option?
Yes. Note: for debugging purposes, you may want to run ZServer in the foreground so you can see tracebacks that may crop up if it fails.
I'm currently using Zope 2.0a4 on Linux/mips.
Cool. I am very motivated to get ZServer working as well as possible. In your case I need more information about what is failing in order to help you correct your configuration or fix any problems that ZServer may have. Is there any particular pattern to when Zope fails? Is anything written to the ZServer log? Is anything written to the stdout? Does only the PCGI server stop, or do all medusa servers stop? Does the Zope process actually quit, or does it just stop responding? What about the zdaemon process? At this point we may want to take this discussion offline. Also, for everyone out there whose still reading this, I suggest filing bugs in the Collector, in addition to just mailing them to the list :-) Thanks! -Amos
On Thu, 15 Jul 1999 10:09:31 -0700, Amos Latteier <amos@aracnet.com> said: Amos> I am very motivated to get ZServer working as well as possible. In Amos> your case I need more information about what is failing in order Amos> to help you correct your configuration or fix any problems that Amos> ZServer may have. OK, here are some more data points in addition to my other mail from yesterday. It seems to be the pCGI layer of ZServer which is dying. BTW, unrelated note, I'm very impressed with ZServer's performance. I was testing out an external method which was cpu bound, meanwhile the server was totally reponsive to other requests. That's cool. Amos> Is there any particular pattern to when Zope fails? Is anything Amos> written to the ZServer log? Is anything written to the stdout? Amos> Does only the PCGI server stop, or do all medusa servers stop? Amos> Does the Zope process actually quit, or does it just stop Amos> responding? What about the zdaemon process? Currently, the server is responding with the Temporarily Unavailable message. However, it seems like it's just the pcgi wrapper which is dead, because the ZServer is still repsonding on all other ports: Here are some sessions that illustrate what's going on. I still didn't see if there were any tracebacks. I will have to redirect output when I start it. Processes: 3244 ? S 0:00 python z2.py -u zope -Z var/mgr.pid (this is the var/mgr.pid process) 6393 ? S 0:17 /usr/local/bin/python z2.py -u zope -Z var/mgr.pid (this is the var/pcgi.pid process) 6402 ? S 0:00 /usr/local/bin/python z2.py -u zope -Z var/mgr.pid 6403 ? S 0:02 /usr/local/bin/python z2.py -u zope -Z var/mgr.pid 6404 ? S 0:01 /usr/local/bin/python z2.py -u zope -Z var/mgr.pid 6405 ? S 0:00 /usr/local/bin/python z2.py -u zope -Z var/mgr.pid 6406 ? S 0:00 /usr/local/bin/python z2.py -u zope -Z var/mgr.pid -------------------------------------------------------------------- % telnet zope.swcp.com 80 Trying 198.59.115.167... Connected to cobalt.swcp.com. Escape character is '^]'. GET /manage/ HTTP/1.0 HOST: zope.swcp.com [a pause here, and I see Zope.cgi as a process] HTTP/1.1 503 Service Unavailable Date: Fri, 16 Jul 1999 16:18:23 GMT Server: Apache/1.3.3 Cobalt (Unix) (Red Hat/Linux) Expires: Thu, 01 Dec 1994 16:00:00 GMT Pragma: nocache Connection: close Content-Type: text/html <HTML> <HEAD> <TITLE>Temporarily Unavailable</TITLE> </HEAD> <BODY BGCOLOR="#FFFFFF"> <TABLE BORDER="0" WIDTH="100%"> <TR> <TD WIDTH="10%"> <CENTER> <B><FONT SIZE="+6" COLOR="#77003B">!</FONT></B> </CENTER> </TD> <TD WIDTH="90%"><BR> <FONT SIZE="+2">Temporarily Unavailable</FONT> <P> The resource you requested is temporarily unavailable - please try again later . </TD> </TR> </TABLE> (102) failure during connect <!-- Connection refused pcgi-wrapper-version 2.0a5 --> </BODY></HTML>Connection closed by foreign host. ---------------------------------------------------------------------------- % telnet zope.swcp.com 9221 Trying 198.59.115.167... Connected to cobalt.swcp.com. Escape character is '^]'. 220 cobalt.swcp.com FTP server (Medusa Async V1.5 [experimental]) ready. quit 221 Goodbye. Connection closed by foreign host. ---------------------------------------------------------------------------- % telnet zope.swcp.com 9673 Trying 198.59.115.167... Connected to cobalt.swcp.com. Escape character is '^]'. GET / HTTP/1.0 HTTP/1.0 200 OK Server: Zope/(unreleased version) ZServer/1.1b1 Date: Fri, 16 Jul 1999 16:23:19 GMT Connection: close Content-Type: text/x-unknown-content-type Content-Length: 0 Connection closed by foreign host. ---------------------------------------------------------------------------- % telnet zope.swcp.com 9999 Trying 198.59.115.167... Connected to cobalt.swcp.com. Escape character is '^]'. 932142247.383 ---------------------------------------------------------------------------- -- Alex Rice | alrice@swcp.com | http://www.swcp.com/~alrice Current Location: N. Rio Grande Bioregion, Southwestern USA
participants (2)
-
Alex Rice -
Amos Latteier