[Zope-dev] yes, segv11 and Broken pipes

[Chris McDonough]

These failure reports are alarming, but I haven't seen
anything like them, and of course we can't fix what we can't
find.  If anybody can make the problem recur repeatably, we
can almost certainly fix it.

Sorry,

- C


On Sun, 09 Dec 2001 10:03:36 +0100
 Dirk Datzert <Dirk.Datzert@rasselstein-hoesch.de> wrote:
> Hello,
> 
> I can report the same failure:
> 
> First there is a OSerror signal 11 and from that point on
> there will be OSerror errno
> 32 Borken pipe until Zope is restarted.
> 
> Our System is:
> 
> Zope 2.4.3 (from source 2.4.1 with update 2.4.x_to_2.4.3,
> python 2.1.1, Apache 1.3.12
> 
> is there a solution out ?
> 
> Regards,
> Dirk
> 
> Leonardo Rochael Almeida schrieb:
> 
> > For the record, I also get Broken pipes on the
> segfaulting zope, but
> > then again, I get broken pipes in ALL my Zopes (and we
> got a bunch of
> > those here at Hiperlógica). So I don't believe they
> correlate.
> >
> > On Fri, 2001-12-07 at 19:20, Dieter Maurer wrote:
> > > =?iso-8859-1?Q?Dario_Lopez-K=E4sten?= writes:
> > >  > Well, sorry to disapoint everybody, but we have
> the same signal 11 restarts
> > >  > here.
> > >  > ...
> > >  > Also, for the record we usually get a bunch of
> these quite often:
> > >  >
> > >  > 2001-11-04T09:04:33 ERROR(200) ZServer uncaptured
> > >  >   python exception, closing channel <zhttp_channel
> connected
> > >  >   XXX.XXX.XXX.XXX:2181 at fb4edc channel#: 2286
> requests:4>
> > >  >   (socket.error:(32, 'Broken pipe')
> > >  >
> > >  > [/usr/local/zope/dist/Zope-2.4.1/ZServer/medusa/asynchat.py|initiate_send|21
> > >  > 4] [/usr/local/zope/dist/Zope-2.4.1/ZServer/medusa/http_server.py|send|414]
> > >  > [/usr/local/zope/sw/Python2.1.1/lib/python2.1/asyncore.py|send|330])
> > >  >
> > >  >
> > >  > We were seeing the same error
> (asyncore.py|send|330, etc) on solaris.
> > > They should be harmless:
> > >
> > >   They happen when the client closes the connection
> before
> > >   ZServer delivered the full response.
> > >
> > >   However, many people reporting about crashes also
> reported about
> > >   these error messages. Maybe, the Pyton socket
> module lacks
> > >   a "Py_INCREF" for this kind of error?
> > >
> >
> > _______________________________________________
> > Zope-Dev maillist  -  Zope-Dev@zope.org
> > http://lists.zope.org/mailman/listinfo/zope-dev
> > **  No cross posts or HTML encoding!  **
> > (Related lists -
> >  http://lists.zope.org/mailman/listinfo/zope-announce
> >  http://lists.zope.org/mailman/listinfo/zope )
> 
> 
> _______________________________________________
> Zope-Dev maillist  -  Zope-Dev@zope.org
> http://lists.zope.org/mailman/listinfo/zope-dev
> **  No cross posts or HTML encoding!  **
> (Related lists - 
>  http://lists.zope.org/mailman/listinfo/zope-announce
>  http://lists.zope.org/mailman/listinfo/zope )