Hi, Also, is there a correlation with 499 error codes with the error? I have been trying to figure out the 499 in the nginx acces logs.
On Fri, Oct 19, 2012 at 6:14 PM, David Montgomery <[email protected]> wrote: > Also...I am assuming I can remove from logs using --ignore-sigpipe? > > On Fri, Oct 19, 2012 at 6:13 PM, David Montgomery > <[email protected]> wrote: >> I have the carbon flag set for stats. Is there any way I can easily >> count the time of times this happens so i can shove into graphite? >> >> On Fri, Oct 19, 2012 at 5:21 PM, Andriy Kornatskyy >> <[email protected]> wrote: >>> >>> uWSGI process handled request but output to pipe (socket), which was closed >>> by peer, caused this error. In other words the client closed connection >>> prior to waiting response from server. >>> >>> May be a source of attack. Keep eye. >>> >>> Thanks. >>> >>> Andriy Kornatskyy >>> >>> >>> ---------------------------------------- >>>> Date: Fri, 19 Oct 2012 17:15:18 +0800 >>>> From: [email protected] >>>> To: [email protected] >>>> Subject: [uWSGI] IOError: write error >>>> >>>> Hi, >>>> >>>> I am seeing the below in the logs. I am trying to understand this but >>>> can it be interpreted that I responded to the request in 8ms but its >>>> an error not on me but on the client? Basically its not a me problem >>>> but a them problem? If the client did not disconnect then I would >>>> have had a success? >>>> >>>> address space usage: 383692800 bytes/365MB} {rss usage: 167038976 >>>> bytes/159MB} [pid: 16614|app: 0|req: 74184/222373] 74.125.191.16 () >>>> {36 vars in 481 bytes} [Fri Oct 19 10:07:07 2012] POST /bidder/ => >>>> generated 0 bytes in 8 msecs (HTTP/1.1 200) 1 headers in 59 bytes (1 >>>> switches on core 1760) >>>> SIGPIPE: writing to a closed pipe/socket/fd (probably the client >>>> disconnected) on request /bidder/ (ip 74.125.xxx.xxx) !!! >>>> Fri Oct 19 10:07:07 2012 - write(): Broken pipe [proto/uwsgi.c line >>>> 143] during POST /bidder/ (74.125.xxx.xxx) >>>> IOError: write error >>>> _______________________________________________ >>>> uWSGI mailing list >>>> [email protected] >>>> http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi >>> >>> _______________________________________________ >>> uWSGI mailing list >>> [email protected] >>> http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi _______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
