Tony Rossignol wrote:
Tres Seaver wrote:
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]) ------
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.
Thanks for the reply. One problem, I can't find anything on the STUPID_DEBUGGER_LOG, is it the same as STUPID_FILE_LOGGER? Or is this an undocumented option?
D'oh! The environment variable which Zope checks for is STUPID_LOG_FILE: * If it is set to a blank string, Zope writes the verbose logging to stderr; * If it is a non-blank string, Zope opens it as a file and writes the verbose logging there; * Otherwise, Zope suppresses the verbose logging.
I'm guessing that these 'Broken pipe' errors might be what is causing zope to periodically restart itself.
Ayup, there have been several threads reporting such restarts lately -- have you been following them? (some were on the zope-dev list, I think).
Again thanks.
Sorry for the confusion! Tres. -- ========================================================= Tres Seaver tseaver@palladion.com 713-523-6582 Palladion Software http://www.palladion.com