Forums

Can someone explain me what these errors may be due?

Error Log:

2015-01-03 16:11:34,595 :OSError: write error 2015-01-03 16:11:34,603 :RuntimeError: generator ignored GeneratorExit 2015-01-03 16:38:52,410 :OSError: write error 2015-01-03 16:38:52,415 :RuntimeError: generator ignored GeneratorExit 2015-01-03 16:51:01,541 :OSError: write error 2015-01-03 16:51:01,542 :RuntimeError: generator ignored GeneratorExit

Server Log:

2015-01-03 16:11:34 Sat Jan 3 16:11:34 2015 - uwsgi_response_writev_headers_and_body_do(): Broken pipe [core/writer.c line 287] during POST /calendario (10.190.154.117) 2015-01-03 16:14:38
2015-01-03 16:32:15
2015-01-03 16:33:44
2015-01-03 16:38:52 Sat Jan 3 16:38:52 2015 - SIGPIPE: writing to a closed pipe/socket/fd (probably the client disconnected) on request /calendario (ip 10.190.154.117) !!! 2015-01-03 16:38:52 Sat Jan 3 16:38:52 2015 - uwsgi_response_writev_headers_and_body_do(): Broken pipe [core/writer.c line 287] during POST /calendario (10.190.154.117) 2015-01-03 16:41:17
2015-01-03 16:42:00
2015-01-03 16:43:10
2015-01-03 16:49:29
2015-01-03 16:50:10
2015-01-03 16:51:01
2015-01-03 16:51:01
2015-01-03 16:51:01 Sat Jan 3 16:51:01 2015 - SIGPIPE: writing to a closed pipe/socket/fd (probably the client disconnected) on request /prenotazione-singola-manuale?data_cella=2015-10-18&camera=6 (ip 10.190.154.117) !!! 2015-01-03 16:51:01 Sat Jan 3 16:51:01 2015 - uwsgi_response_write_headers_do(): Broken pipe [core/writer.c line 229] during POST /prenotazione-singola-manuale?data_cella=2015-10-18&camera=6 (10.190.154.117)

They usually mean that the web browser disconnected before the request was finished. This could be if your views take a long time to finish or if your users are impatient or if you're making AJAX requests that are being interrupted.

Thanks. I'd like to keep this from happening in the future. Would buying a higher tier help? Or perhaps some configuration on my part?

A certain number of errors like that are unavoidable -- for example, if someone accesses your website from their cellphone and then their signal dies because they've moved out of coverage while your site is sending data back to them, then the connection will be broken and you'll see an error in your logs.

That said, you're seeing quite a lot of them. That might happen if your site is taking a long time to respond to certain requests -- if that happens, then sometimes people give up and go to another page, or close the browser tab, or whatever, which will show up in the same way.

If you take a look at your access logs, you'll see that each hit has a field at the end saying how many seconds serving the view took. Perhaps you could look at that (and compare with the errors in the server log) and see if there are any specific views that are taking longer than you'd expect? It might be that some optimisation of those views will make things better. Good things to look for when speeding things like that up are database indexes (if DB queries are the slow thing) or eliminating dependencies on potentially-slow external APIs (if those might be the culprit).