thilo, a few months ago you posted http://lists.zope.org/pipermail/zope-dev/2000-February/003202.html about an intermittent fastcgi protocol error. I'm just setting up zope with fastcgi and i am experiencing the same problem. i restarted zope, and the problem went away. my socket is located in /tmp/fcgi/, so i'm wondering if it needs to be moved out of the temp directory or ??? What did you do to fix this problem? ---scott
The problem was in the file ZServer/FCGIServer.py. It was fixed in CVS version 1.5.4.1 and I think in the main branch starting with version 1.7. I don't know which version of the file Zope 2.1.6 uses, but if you download from CVS at least FCGIServer.py version 1.7, that should eliminate the problem. I did that several months ago and haven't had a single FCGI problem since. I hope this helps. _______________________ Ron Bickers Logic Etc, Inc. rbickers@logicetc.com
-----Original Message----- From: zope-admin@zope.org [mailto:zope-admin@zope.org]On Behalf Of Scott Thomason Sent: Tuesday, April 18, 2000 12:39 PM To: mezger@innominate.de; zope@zope.org Subject: [Zope] zope fastcgi protocol error
thilo, a few months ago you posted http://lists.zope.org/pipermail/zope-dev/2000-February/003202.html about an intermittent fastcgi protocol error. I'm just setting up zope with fastcgi and i am experiencing the same problem. i restarted zope, and the problem went away. my socket is located in /tmp/fcgi/, so i'm wondering if it needs to be moved out of the temp directory or ???
What did you do to fix this problem? ---scott
Ah, someone else using FastCGI. We are also using FastCGI and have this error appear in zope_msg.log frequently: 2000-04-18T16:34:05 ERROR(200) ZServer uncaptured python exception, closing channel <FCGIChannel connected 206.138.64.10:1621 at dceec08> (socket.error:(32, 'Broken pipe') [/usr/local/Zope-2.1.6-NT-1.0.2/ZServer/medusa/asynchat.py|initiate_send|211] [/usr/local/Zope-2.1.6-NT-1.0.2/ZServer/medusa/asyncore.py|send|237]) Have you seen this error? And is it one that concerns you? We have frequent restarts, but this particular error does not appear to be related. I was just wondering what your experience has been. Thanks. -- ------------------------------- tonyr@ep.newtimes.com Director of Web Technology New Times, Inc. -------------------------------
It seems I saw this error early on when trying to get FCGI setup, but I don't recall the circumstances. I haven't seen it since I cleared up the invalid version error problems, so I'm afraid I can't help with this one. _______________________ Ron Bickers Logic Etc, Inc. rbickers@logicetc.com
-----Original Message----- From: toros@newtimes.com [mailto:toros@newtimes.com]On Behalf Of Tony Rossignol Sent: Tuesday, April 18, 2000 1:26 PM To: Ron Bickers; zope@zope.org Subject: Re: [Zope] zope fastcgi protocol error
Ah, someone else using FastCGI. We are also using FastCGI and have this error appear in zope_msg.log frequently:
2000-04-18T16:34:05 ERROR(200) ZServer uncaptured python exception, closing channel <FCGIChannel connected 206.138.64.10:1621 at dceec08> (socket.error:(32, 'Broken pipe') [/usr/local/Zope-2.1.6-NT-1.0.2/ZServer/medusa/asynchat.py|initiat e_send|211] [/usr/local/Zope-2.1.6-NT-1.0.2/ZServer/medusa/asyncore.py|send|237])
Have you seen this error? And is it one that concerns you? We have frequent restarts, but this particular error does not appear to be related. I was just wondering what your experience has been.
Thanks.
participants (3)
-
Ron Bickers -
Scott Thomason -
Tony Rossignol