How to prevent errno 32 broken pipe

Question

Currently I am using an app built in python  When I run it in personal computer  it works without problems    However  when I move it into a production server  It keeps showing me the error attached as below     I ve done some research and I got the reason that the end user browser stops the connection while the server is still busy sending data    I wonder why did it happen and what is the root cause that prevents it from running properly in production server  while it works on my personal computer  Any advice is appreciated      Exception happened during processing of request from   127 0 0 1   34226  Traceback  most recent call last     File   usr lib python2 7 SocketServer py   line 284  in  handle request noblock     self process request request  client address    File   usr lib python2 7 SocketServer py   line 310  in process request     self finish request request  client address    File   usr lib python2 7 SocketServer py   line 323  in finish request     self RequestHandlerClass request  client address  self    File   usr lib python2 7 SocketServer py   line 641  in   init       self finish     File   usr lib python2 7 SocketServer py   line 694  in finish     self wfile flush     File   usr lib python2 7 socket py   line 303  in flush     self  sock sendall view write offset write offset buffer size   error   Errno 32  Broken pipe

User · Accepted Answer

Your server process has received a SIGPIPE writing to a socket  This usually happens when you write to a socket fully closed on the other  client  side  This might be happening when a client program doesn t wait till all the data from the server is received and simply closes a socket  using close function     In a C program you would normally try setting to ignore SIGPIPE signal or setting a dummy signal handler for it  In this case a simple error will be returned when writing to a closed socket  In your case a python seems to throw an exception that can be handled as a premature disconnect of the client

User · Answer

It depends on how you tested it  and possibly on differences in the TCP stack implementation of the personal computer and the server   For example  if your sendall always completes immediately  or very quickly  on the personal computer  the connection may simply never have broken during sending  This is very likely if your browser is running on the same machine  since there is no real network latency      In general  you just need to handle the case where a client disconnects before you re finished  by handling the exception   Remember that TCP communications are asynchronous  but this is much more obvious on physically remote connections than on local ones  so conditions like this can be hard to reproduce on a local workstation   Specifically  loopback connections on a single machine are often almost synchronous

User · Answer

The broken pipe error usually occurs if your request is blocked or takes too long and after request-side timeout  it ll close the connection and then  when the respond-side  server  tries to write to the socket  it will throw a pipe broken error

User · Answer

This might be because you are using two method for inserting data into database and this cause the site to slow down   def add subscriber request  email None       if request method     POST           email   request POST  email field           e   Subscriber objects create email email  save     lt               return HttpResponseRedirect          else          return HttpResponseRedirect        In above function  the error is where arrow is pointing   The correct implementation is below   def add subscriber request  email None       if request method     POST           email   request POST  email field           e   Subscriber objects create email email          return HttpResponseRedirect          else          return HttpResponseRedirect

[python] How to prevent errno 32 broken pipe?

Examples related to python

Examples related to broken-pipe