Python – uwsgi throws IO error caused by uwsgi_response_write_body_do broken pipe

djangopythonuwsgi

My application is a uwsgi+django setup. I use gevent to do performance testing and run 1200 requests concurrently. At this point, uwsgi will throw an IO error with the following log message:

uwsgi_response_write_body_do(): Broken pipe [core/writer.c line 260]
IOError: write error

Django 1.4.0
uwsgi: 1.9.13
python: 2.6
TCP Listen queue: 1000

What is the cause of this broken pipe error?

Best Answer

This can happen when NGINX started a request to uWSGI but uWSGI took too long to respond, then NGINX closes the connection to uWSGI. When uWSGI finally finishes, it tries to give it's response back to NGINX, but NGINX closed the connection earlier, so then uWSGI throws an I/O error.

So this could mean that your uWSGI process is taking too long.

Update:

uWSGI's Harakiri mode could be useful to automatically terminate such long taking processes if you want to: https://uwsgi-docs.readthedocs.io/en/latest/FAQ.html#what-is-harakiri-mode You might not want to do this because a process might be finishing some long query or something which is necessary.

Related Solutions

Python – How to test that a Python function throws an exception

Use TestCase.assertRaises (or TestCase.failUnlessRaises) from the unittest module, for example:

import mymod

class MyTestCase(unittest.TestCase):
    def test1(self):
        self.assertRaises(SomeCoolException, mymod.myfunc)

Django+uwsgi: uwsgi_response_write_body_do(): Broken pipe [core/writer.c line 248]

that error means the client (browser) disconnected before getting the full response. Check your webserver logs, maybe you hit a timeout

Best Answer

Related Solutions

Python – How to test that a Python function throws an exception

Django+uwsgi: uwsgi_response_write_body_do(): Broken pipe [core/writer.c line 248]

Related Topic