22

If I am coding on Flask, then I sometimes get this error:

Traceback (most recent call last): File "C:\Python27\lib\SocketServer.py", line 284, in _handle_request_noblock self.process_request(request, client_address) File "C:\Python27\lib\SocketServer.py", line 310, in process_request self.finish_request(request, client_address) File "C:\Python27\lib\SocketServer.py", line 323, in finish_request self.RequestHandlerClass(request, client_address, self) File "C:\Python27\lib\SocketServer.py", line 640, in __init__ self.finish() File "C:\Python27\lib\SocketServer.py", line 693, in finish self.wfile.flush() File "C:\Python27\lib\socket.py", line 303, in flush self._sock.sendall(view[write_offset:write_offset+buffer_size]) error: [Errno 10053] ��������� �� ����� ����-

Any ideas why this would happen (win8 x64, python27 x32)?

Improve this question
3
  • 1
    What exactly are you doing at the time that you get this error? Commented Jul 25, 2013 at 9:55
  • 1
    work :) - google chrome+pycharm, i re no firewolls, anti virus and etc. Commented Jul 25, 2013 at 13:14
  • 1
    Worked for me adding threaded=True in app.run, app.run(threaded=True). Commented Feb 6, 2018 at 10:52

7 Answers 7

Reset to default
27

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.

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.

Improve this answer
Sign up to request clarification or add additional context in comments.

11 Comments

but i havent firewolls, anti virus and etc.
I was listing some of the possibilities.
That is impossible for us to tell. You didn't include any information as to what you were doing at the time, your platform, your network setup, your client, etc. We are stuck with giving you generic information about the error code.
@MartijnPieters I was wondering the same thing. You might want to check this post:stackoverflow.com/a/20421867/2290820
@vipin: you can certainly get socket errors too when your database socket has been closed, but in the case of the OP the traceback is due to the HTTP client having closed the connection.
|
9

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 

error: [Errno 10053] An established connection was aborted by the software in your host machine

Server would be restarted if you have done like app.run(threaded=True).

Improve this answer

1 Comment

using python 3.6 and I'm havinf this error. Any clue to why?
5

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.

Improve this answer

Comments

4

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

Improve this answer

1 Comment

As promised, here is the solution: stackoverflow.com/questions/40247025/…
2

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.

time.sleep(10) data = s.recv(1024) s.close()

It works for me.

Improve this answer

Comments

2

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:

https://support.microsoft.com/en-us/help/170359/how-to-modify-the-tcp-ip-maximum-retransmission-time-out

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.

Improve this answer

Comments

1

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.

Improve this answer

Comments

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.