First, you seem to be using gevent 1.0. The latest version is 1.1.1 and it contains many fixes and improvements to pywsgi. I highly encourage you to upgrade.
Second, on this particular issue, a broken pipe from this location means that the client socket disconnected while the request was in progress, and pywsgi is unable to send the application response. This *should not* cause any problems with future requests. As far as pywsgi is concerned, each client socket is distinct. One of the changes in gevent 1.1.1 is to adjust the logging of events like this to more correctly reflect that it's a client problem and not all that uncommon.
Off the top of my head, the only reasons I can think of for not being able to serve future requests are
(1) some application state got corrupted and the application simply stops running the callable;
(2) the upstream proxy decided that the pywsgi server was "down" because it took so long to handle the request, and so it's stopped passing them on; or
(3) the actual pywsgi listening socket that accepts the client connections in the first place went down somehow (but that's not this error and is quite unlikely).
> --
> You received this message because you are subscribed to the Google Groups "gevent: coroutine-based Python network library" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to
gevent+un...@googlegroups.com.
> For more options, visit
https://groups.google.com/d/optout.