Hi Luiz, I cc'ed the zope mail list on this question... That message appears when a browser breaks the current connection before the response is returned, and it's normal under most circumstances. It may or may not have anything to do with your Zope stability problem. A good thing to do would be to turn on detailed logging via the "-M" switch to z2.py. After you gather information in the log, use the script at http://www.zope.org/Members/mcdonc/HowTos/DEBUG-LOG to figure out what requests aren't returning. See if there's a pattern. - C ----- Original Message ----- From: "Luiz Antonio B. Silva" <labs@planetarium.com.br> To: "Amos Latteier" <amos@digicool.com>; <zdp@zope.org> Sent: Tuesday, April 10, 2001 10:07 AM Subject: [ZDP] socket.error 32 'Broken pipe' Hi. I´m noticing a problem with Zope. It crashes sometimes (with some frequence, to be honest) with aparently no reason. Its the 2.3.1 final version instaled on a Linux Red Hat. Watching the console I got a lot of the folowing error: 2001-04-09T14:41:11 ERROR(200) ZServer uncaptured python exception, closing channel <zhttp_channel connected 111.222.33.44:62517 at 881f588 channel#: 224 requests:2> (socket.error:(32, 'Broken pipe') [/opt/zope2.3.1/ZServer/medusa/asynchat.py|handle_read|80] [/opt/zope2.3.1/ZServer/medusa/http_server.py|recv|405] [/opt/zope2.3.1/ZServer/medusa/asyncore.py|recv|301]) Could someone tell me what´s wrong or what could I do? Thanks in advance Labs _______________________________________________ ZDP maillist - ZDP@zope.org http://lists.zope.org/mailman/listinfo/zdp