> Another one of my developmemnt servers has started doing this now.. This > time, it's unrelated to any sort of lag/delay in response: > > Sat Aug 6 15:50:12 2011 - write(): Broken pipe > [plugins/python/wsgi_subhandler.c line 189] > Sat Aug 6 15:50:14 2011 - write(): Broken pipe > [plugins/python/wsgi_subhandler.c line 189] > Sat Aug 6 15:50:16 2011 - write(): Broken pipe > [plugins/python/wsgi_subhandler.c line 189] > Sat Aug 6 15:50:18 2011 - writev(): Broken pipe > [plugins/python/wsgi_headers.c line 182] > Sat Aug 6 15:50:18 2011 - write(): Broken pipe > [plugins/python/wsgi_subhandler.c line 189] > Sat Aug 6 15:50:30 2011 - write(): Broken pipe > [plugins/python/wsgi_subhandler.c line 189] > > PY-Execution-Time: 0.178904056549 > PY-Execution-Time: 0.279319047928 > PY-Execution-Time: 0.212793111801 > PY-Execution-Time: 0.19362783432 > PY-Execution-Time: 0.18998003006 > PY-Execution-Time: 0.230093002319
> > Any ideas? If uWSGI is not blocked this could be a simple disconnecting client, otherwise remember that you can send SIGUSR2 to workers to know what they are doing (and eventually call strace on it) -- Roberto De Ioris http://unbit.it _______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
