I have the following set-up under which Zope occasionally dies.

Zope 2.2.2 (same happened with 2.2.0 and 2.2.1)
RedHat Linux 6.2
Apache 1.3.12 - with fastcgi/2.2.8 and OpenSSL/0.95a 

I'm running Zope with Fastcgi and using Apache rewrite rules to redirect
all URLs that 
contain "manage" to https. 

It seems to work fine except on occasion Zope will die with the
following error:

"ZServer uncaptured python exception, closing channel <FCGIChannel
connected 127.0.0.1:2198 at 87195b> (socket.error:(32, 'Broken pipe')
[path_to_Zope/Zserver/medusa/asynchat.py|initiate_send||211]
[path_to_Zope/Zserver/medusa/asynchat.py|send|274])

This doesn't always mean the server is dead but it is the only error I
can trap with 
debug turned on. I am starting the Zope server with the -Z option. 

Ideas. I'm about ready to start making the server more widely available
but cannot if
the server is unreliable.

Ideas, strategies, options? 

TIA

Ron Roeber





_______________________________________________
Zope maillist  -  [EMAIL PROTECTED]
http://lists.zope.org/mailman/listinfo/zope
**   No cross posts or HTML encoding!  **
(Related lists - 
 http://lists.zope.org/mailman/listinfo/zope-announce
 http://lists.zope.org/mailman/listinfo/zope-dev )

Reply via email to