[Zope] zope_msg.log Message

[Tres Seaver]

Tony Rossignol <tonyr@ep.newtimes.com>
> 
> Does anyone have any insite into what this error message might be?
> 
> 2000-03-20T06:36:51 ERROR(200) ZServer uncaptured python exception,
> closing channel <FCGIChannel connected 206.138.64.10:1819 at 10c1b2f0>
>  (socket.error:(32, 'Broken pipe')
> [/usr/local/Zope-2.1.4-NT-0.1.6/ZServer/medusa/asynchat.py|initiate_send|211]
> [/usr/local/Zope-2.1.4-NT
> -0.1.6/ZServer/medusa/asyncore.py|send|237])
> ------
> 2000-03-20T06:36:51 ERROR(200) ZServer uncaptured python exception,
> closing channel <FCGIChannel connected 206.138.64.10:1819 at 10c1b2f0>
>  (socket.error:(32, 'Broken pipe')
> [/usr/local/Zope-2.1.4-NT-0.1.6/ZServer/medusa/asynchat.py|initiate_send|211]
> [/usr/local/Zope-2.1.4-NT
> -0.1.6/ZServer/medusa/asyncore.py|send|237])
> ------
> 
> And should I be worring about it?
> 
"Broken pipe" says that the peer process/thread on the other end of a pipe died
without shutting down the pipe cleanly.  You should be concerned, because these
are your "Zope" threads that are dying -- eventually, you will have none left to
service requests.

This problem is a symptom of something inside Zope which is killing off threads,
most likely an unhandled exception somewhere.  Try turning on the
STUPID_DEBUGGER_LOG and see if you get more enlightening log output.

-- 
=========================================================
Tres Seaver         tseaver@palladion.com    713-523-6582
Palladion Software  http://www.palladion.com