----- Oryginalna wiadomość -----
> Od: "Roberto De Ioris" <[email protected]>
> Do: "uWSGI developers and users list" <[email protected]>
> Wysłane: czwartek, 3 maj 2012 14:42:46
> Temat: Re: [uWSGI] uwsgi IOError
>
> I definetely used the wrong words :)
> As you said, uWSGI knows about client disconnection at the first
> write()/writev().
>
> In previous versions, apps was not aware of disconnections and failed
> writes were ignored (you get only a series of SIGPIPE)
>
How do I prevent this error.
I am interested in print, that such event took place (client has disconnected
before sending him to answer), but something a bit too much:
2012-04-30 22:10:36 - SIGPIPE: writing to a closed pipe/socket/fd (probably the
client disconnected) on request / (ip ::ffff:178....) !!!
2012-04-30 22:10:36 - writev(): Broken pipe [proto/uwsgi.c line 122] during GET
/ (::ffff:178....)
Traceback (most recent call last):
File "./req.py", line 110, in __iter__
self.__start_response(self.response.status, self.response.get_headers())
IOError: write error
Enough to:
2012-04-30 22:10:36 - writev(): Broken pipe [proto/uwsgi.c line 122] during GET
/ (::ffff:178....)
Is the "ignore-sigpipe" solve the problem of excessive amounts of information
in the logs ?
Or maybe I need to wrap the start_response in try ?
--
Łukasz Wróblewski
http://www.nri.pl/ - Nowoczesne Rozwiązania Internetowe
http://www.hostowisko.pl/ - Profesjonalny i tani hosting
http://www.katalog-polskich-firm.pl/ - Najlepszy darmowy katalog firm
_______________________________________________
uWSGI mailing list
[email protected]
http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
