Have you ever seen a socket.error: [Errno 32] Broken pipe message when running a Python Web server and wondered what that means?
The rule is that when a process tries to write to a socket that has already received an RST packet, the SIGPIPE signal is sent to that process which causes the Broken pipe socket.error exception.
Here are two scenarios that you can try that cause SIGPIPE signal to be fired.
1. Server may send an RST packet to a client to abort the socket connection but the client ignores the packet and continues to write to the socket.
To test that behavior. install Cynic, run it
02.INFO [2012-06-08 05:06:37,040] server: Starting 'HTTPHtmlResponse' on port 2000
03.INFO [2012-06-08 05:06:37,040] server: Starting 'HTTPJsonResponse' on port 2001
04.INFO [2012-06-08 05:06:37,040] server: Starting 'HTTPNoBodyResponse' on port 2002
05.INFO [2012-06-08 05:06:37,040] server: Starting 'HTTPSlowResponse' on port 2003
06.INFO [2012-06-08 05:06:37,040] server: Starting 'RSTResponse' on port 2020
07.INFO [2012-06-08 05:06:37,040] server: Starting 'RandomDataResponse' on port 2021
08.INFO [2012-06-08 05:06:37,040] server: Starting 'NoResponse' on port 2022
09.INFO [2012-06-08 05:06:37,041] server: Starting 'LogRecordHandler' on port /tmp/_cynic.sockand then run the client1.py:
03.# connect to Cynic's RSTResponse service on port 2020
04.s = socket.socket(socket.AF_INET, socket.SOCK_STREAM)
07.# first read gets an RST packet
10.except socket.error as e:
14.# write after getting the RST causes SIGPIPE signal
15.# to be sent to this process which causes a socket.error
来自 “ ITPUB博客 ” ，链接：http://blog.itpub.net/301743/viewspace-733074/，如需转载，请注明出处，否则将追究法律责任。