The BrokenPipeError is normal as said phantom because the reading process (head) terminates and closes its end of the pipe while the writing process (python) still tries to write. Is is an abnormal condition, and the python scripts receives a BrokenPipeError – more exactly, the Python interpreter receives a system SIGPIPE signal that it catches … Read more
This isn’t really an issue with your site, more with the Django devserver: see this Django ticket. To put it bluntly, just ignore it as it is a known error, and won’t be fixed. In that ticket’s comments a quite clear explanation is given: According to many sources the ‘Broken Pipe’ is a normal browser … Read more
It can take time for the network close to be observed – the total time is nominally about 2 minutes (yes, minutes!) after a close before the packets destined for the port are all assumed to be dead. The error condition is detected at some point. With a small write, you are inside the MTU … Read more
Assuming that you are using the standard socket module, you should be catching the socket.error: (32, ‘Broken pipe’) exception (not IOError as others have suggested). This will be raised in the case that you’ve described, i.e. sending/writing to a socket for which the remote side has disconnected. import socket, errno, time # setup socket to … Read more
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 … Read more
You generally want to ignore the SIGPIPE and handle the error directly in your code. This is because signal handlers in C have many restrictions on what they can do. The most portable way to do this is to set the SIGPIPE handler to SIG_IGN. This will prevent any socket or pipe write from causing … Read more