[Zope] Re: Zope and FastCGI

Mon, 20 Dec 1999 10:55:57 -0500

Unfortunately not.

I've been reading a lot of documentation on Zope and Python (being new to
them both), and I'm getting closer to being able to do something about it
myself.  But until then, I'll have to rely on someone else.  Maybe as more
people start to use FastCGI and realize something is broken, it'll become a
priority.

_______________________

Ron

> -----Original Message-----
> From: Jochen Haeberle [mailto:listen@MIDRAS.de]
> Sent: Monday, December 20, 1999 5:39 AM
> To: Ron Bickers; zope@zope.org
> Subject: [Zope] Re: Zope and FastCGI
>
>
> Hi ron,
>
> did you get any reply to your very detailed report, yet??
>
> At 23:12 Uhr -0500 08.12.1999, Ron Bickers wrote:
> >I have this same problem.  A while back I sent the following
> information to
> >Scott Robertson but haven't heard anything either way.  It looks like a
> >problem with Zope/FCGI as opposed to mod_fcgi or Apache.  #2
> looks like some
> >important information, but I'm new to Zope and Python, so what do I know.
> >:-)
> >
> >==================================
> >
> >After further research, I have the following info from the
> FastCGI mailing
> >list and from a debug output from Zope.
> >
> >1) The FastCGI mailing list has this to offer:
> >
> >"Errors about an invalid version usually means the app printed something
> >to stdout (or maybe even stderr) when it shouldn't, and/or
> without the FCGI
> >wrapper functions in place. Thus, instead of the process manager seeing
> >some text from the app's FastCGI protocol like it expects, it sees the
> >output of your program instead, and that causes the error."
> >
> >2) When this error occurred with ZServer running with debug (-D), the
> >following output was sent:
> >
> >1999-11-09T04:52:50 ERROR(200) ZServer uncaptured python
> exception, closing
> >channel <FCGIChannel connected 127.0.0.1:3341 at 84ce480>
> (socket.error:(32,
> >'Broken pipe')
> >[/usr/share/zope/ZServer/medusa/asynchat.py|initiate_send|211]
> >[/usr/share/zope/ZServer/medusa/asyncore.py|send|237])
> >
> >3) Also, the following is a copy/paste of the text as seen in the browser
> >window when the error occurs:
> >
> >HTTP/1.1 200 OK
> >Date: Tue, 09 Nov 1999 04:36:11 GMT
> >Server: Apache/1.3.9 (Unix) mod_fastcgi/2.2.3 PHP/3.0.12
> >X-Powered-By: Zope (www.zope.org), Python (www.python.org)
> >Content-Length: 4022
> >Set-Cookie: tree-s="eJyLjlZ3hANPW3UdhWgkEfdidBEPX1v1WDAAALMKDz4"
> >Connection: close
> >Content-Type: text/html
> >
> ><!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
> ><HTML><HEAD>
> ><TITLE>200 OK</TITLE>
> ></HEAD><BODY>
> ><H1>OK</H1>
> >The server encountered an internal error or
> >misconfiguration and was unable to complete
> >your request.<P>
> >Please contact the server administrator,
> >  webmaster@logicetc.com and inform them of the time the error occurred,
> >and anything you might have done that may have
> >caused the error.<P>
> >More information about this error may be available
> >in the server error log.<P>
> ><HR>
> ><ADDRESS>Apache/1.3.9 Server at test.logicetc.com Port 80</ADDRESS>
> ></BODY></HTML>
> >
> >--------------------
> >
> >I have seen these same random errors running on Linux/Apache
> 1.3.9 as well
> >as FreeBSD 3.2/Apache 1.3.6 both with mod_fcgi October 6 SNAP.
> It seems the
> >FastCGI mailing list points to the FastCGI application
> (Zserver/FCGI in this
> >case, I guess) as the probable source of the problem.
>
>