communication error and socket error - cherrypy-users

Message from discussion communication error and socket error

fumanchu

More options Jun 27, 2:48 pm

From: fumanchu <fuman...@aminus.org>

Date: Sat, 27 Jun 2009 11:48:55 -0700 (PDT)

Local: Sat, Jun 27 2009 2:48 pm

Subject: Re: communication error and socket error

  Reply to author
  |
  Forward
  | Print
  | View thread
  | Show original
  | Report this message
  | Find messages by this author
  

On Jun 27, 2:23 am, todor_k <todo...@ecocoms.com> wrote:

> in web2py Web Framework group we posted a thread for a "communication
> and socket error"

> http://groups.google.com/group/web2py/browse_frm/thread/e9e96414e7648...

> It seems that this could be an cherrypy wsgiserver issue and Massimo
> Di Pierro suggested to bring the thread up in cherrypy mailing list.

A broken pipe error (EPIPE, 32) occurs in this case because the server
encountered some other error, and tried to send a "500 Internal Server
Error" response. While trying to write *that* data to the socket, the
client's TCP stack sent a RST packet because they had already closed
the socket.

Unfortunately, there's a line of code in the SSL_fileobject for
handling errors which reads:

if is_reader and errnum in socket_errors_to_ignore:
return ""

EPIPE is definitely in the list of socket errors to ignore, but I
can't recall why we would only ignore them on reads and not writes
when using SSL. In this case, we certainly should be ignoring the
error. You might try removing the text "is_reader and" and see what
else breaks because of it.

Robert Brewer
fuman...@aminus.org

Reply to author Forward