Re: [Zope-dev] yes, segv11 and Broken pipes

2001-12-10 Thread John Ziniti

Wasn't this the problem where asyncore.py is not
catching the operating system's EINTR.  I used to
get these all the time, and was able to stop it
using a modified asyncore which loops on an OS
select() call, restarting the call if it catches
EINTR from the OS ... I can send a modified
asyncore.py for anyone who wants to give it a
try??

Ziniti

Jens Quade wrote:

 Dirk Datzert [EMAIL PROTECTED] writes:
 
 
Its a Linux 2.2.19. What does IIRC means ?

 
 If I remember correctly. I could fix the problem (or a similar one)
 last summer by changing the Linux kernel. 
 
 http://mailman.beehive.de/pipermail/zope/2001-June/000590.html
 http://mailman.beehive.de/pipermail/zope/2001-November/000923.html
 
 
 
 
 
 ___
 Zope-Dev maillist  -  [EMAIL PROTECTED]
 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  -  [EMAIL PROTECTED]
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 )



Re: [Zope-dev] yes, segv11 and Broken pipes

2001-12-09 Thread 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 [EMAIL PROTECTED] 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  -  [EMAIL PROTECTED]
  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  -  [EMAIL PROTECTED]
 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  -  [EMAIL PROTECTED]
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 )



Re: [Zope-dev] yes, segv11 and Broken pipes

2001-12-09 Thread Jens Quade

Chris McDonough [EMAIL PROTECTED] writes:

 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 [EMAIL PROTECTED] 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
  

Do you use Linux Kernel 2.2.17 (IIRC)? Updating or downgrading to
another version should fix the problem then.

regards,
jens



___
Zope-Dev maillist  -  [EMAIL PROTECTED]
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 )



Re: [Zope-dev] yes, segv11 and Broken pipes

2001-12-09 Thread Dirk Datzert

Its a Linux 2.2.19. What does IIRC means ?

Dirk
- Original Message -
From: Jens Quade [EMAIL PROTECTED]
To: Chris McDonough [EMAIL PROTECTED]
Cc: Dirk Datzert [EMAIL PROTECTED]; Leonardo Rochael
Almeida [EMAIL PROTECTED]; [EMAIL PROTECTED]
Sent: Monday, December 10, 2001 12:28 AM
Subject: Re: [Zope-dev] yes, segv11 and Broken pipes


 Chris McDonough [EMAIL PROTECTED] writes:

  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,
 
  
   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
 Do you use Linux Kernel 2.2.17 (IIRC)? Updating or downgrading to
 another version should fix the problem then.




___
Zope-Dev maillist  -  [EMAIL PROTECTED]
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 )



Re: [Zope-dev] yes, segv11 and Broken pipes

2001-12-09 Thread Dario Lopez-Kästen

From: Dirk Datzert [EMAIL PROTECTED]


 Its a Linux 2.2.19. What does IIRC means ?

IIRC means If I Recall Correctly, IIRC :-)

And these problems occur also on solaris, so there's nothing linux centric
about them.

/dario

- 
Dario Lopez-Kästen Systems Developer  Chalmers Univ. of Technology
[EMAIL PROTECTED]  ICQ will yield no hitsIT Systems  Services


___
Zope-Dev maillist  -  [EMAIL PROTECTED]
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 )