-->
Most Windows Sockets 2 functions do not return the specific cause of an error when the function returns. For information, see the Handling Winsock Errors topic.
The WSAGetLastError function returns the last error that occurred for the calling thread. When a particular Windows Sockets function indicates an error has occurred, this function should be called immediately to retrieve the extended error code for the failing function call. These error codes and a short text description associated with an error code are defined in the Winerror.h header file. The FormatMessage function can be used to obtain the message string for the returned error.
For information on how to handle error codes when porting socket applications to Winsock, see Error Codes - errno, h_errno and WSAGetLastError.
The following list describes the possible error codes returned by the WSAGetLastError function. Errors are listed in numerical order with the error macro name. Some error codes defined in the Winsock2.h header file are not returned from any function.
Return code/value | Description |
---|---|
|
|
|
|
|
|
|
|
|
|
| Overlapped operations will complete later.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Requirements
Header |
|
See also
If I am coding on Flask, then I sometimes get this error:
How To Fix Error 10053
Any ideas why this would happen (win8 x64, python27 x32)?
Matt Way23.9k99 gold badges6060 silver badges6969 bronze badges
Patrick BurnsPatrick Burns60144 gold badges1010 silver badges2626 bronze badges
7 Answers
From the Windows Sockets Error Codes list:
WSAECONNABORTED 10053
Software caused connection abort.
An established connection was aborted by the software in your host computer, possibly due to a data transmission time-out or protocol error.
Software caused connection abort.
An established connection was aborted by the software in your host computer, possibly due to a data transmission time-out or protocol error.
There was a timeout or other network-level error. This is your operating system closing the socket, nothing to do with Python or Flask, really.
It could be the remote browser stopped responding, the network connection died, or a firewall closed the connection because it was open too long, or any other number of reasons.
Martijn Pieters♦Martijn Pieters744k157157 gold badges26782678 silver badges24122412 bronze badges
Hello,This is an issue with the Python 2 implementation of the SocketServer module, it is not present in Python 3 (where the server keeps on serving).
Your have 3 options:
Don't use the built-in server for production systems (it is a development server after all). Use a proper WSGI server like gunicorn or uWSGI.
Enable threaded mode with app.run(threaded=True); the thread dies but a new one is created for future requests,
Upgrade to Python 3.
So whenever there is error like
Server would be restarted if you have done like app.run(threaded=True).
KeyurKeyur
I recently ran into this error message while trying to use Flask to serve audio files. I get this error message whenever the client closes the stream before the end of the stream. Flask continues to try to write data to the stream, but since the underlying socket has been disconnected, it can't. This isn't actually an error per se, but rather a message informing you that the connection to the client has been closed before Flask finished writing data to the stream.
NopNop
I have just experienced exactly the same problem. Contrary to the most upvoted answer, the issue has a lot to do with Python and Flask, and it is not a Windows issue.Very easy to reproduce:
- Click on a link within a flask application and then navigate to another page whilst the first one is still loading. Error appears every time and application crashes (needs restarting)
- The issue never happens if I allow the server to return the page completely.
Also, this has never happened with bottle micro-framework, for example.
If I find out how to solve the problem I will let you know
Tony SepiaTony Sepia1,37411 gold badge1616 silver badges2929 bronze badges
I met this problem when reading response from a web server. For my case, the problem was I close the socket connection too early that it broke the communications.So I sleep some seconds before receiving data and then close the socket connection.
It works for me.
Dabay WangDabay Wang
Medieval 2 total war indir. This error can occur regardless of Flask, Python 2, Python 3, or HTTP -- it can occur simply at the socket level and it will depend heavily on your exact situation.
As an example, my application uses an Ethernet device/appliance that uses raw sockets for command and control and I am using the
create_connection
method in the socket
module. I would consistently get 'Errno 10053' after trying to send a message after a period of traffic inactivity. Timing tests showed that this error would occur after trying to send a message after four minutes of inactivity. The following page indicates a 240 second = 4min timeout:The solution in my scenario was to ensure that messages to the device did not span more than four minutes. I simply send a small request message to the device every 60sec to avoid the 10053 error -- this acts as a protocol-level 'keep-alive' (unrelated to TCP keepalive). In this scenario, perhaps the issue is specific to the Ethernet device and the way they've implemented TCP. Nonetheless, a protocol-level 'keep-alive' may be a viable option in many cases.
rob_7ccrob_7cc
It's a PIPE error, which occurs if the server responds to a request and the client has already closed the connection. Browsers do that sometimes depending on usage.You can ignore those, web servers suited for production certainly will.
jayant singhjayant singh