Worth adding that we run nginx in front and it's buffering of small
requests coupled with using X-Accel-Redirect to deliver file content has
resulted in never having this specific issue.

J
On Apr 4, 2014 8:02 AM, "Graham Dumpleton" <[email protected]>
wrote:

> Can also be caused when you have long running requests and for some reason
> the Apache child worker processes that are proxying to the mod_wsgi daemon
> processes are forcibly restarted or crash.
>
> Describe how you have mod_wsgi configured and whether you are using daemon
> mode or not. Also provide your Apache MPM settings and what you have
> MaxRequestsPerChild directive set to.
>
> Oh, and because the IOError is 'failed to write', is nothing to do with
> uploads, but the writing back of the response for a web request to the HTTP
> client.
>
> This can be caused by you simply hitting reload on your browser before the
> page has been completed loaded.
>
> Gaham
>
> On 04/04/2014, at 10:44 PM, Bart <[email protected]> wrote:
>
> > From vague memory, those may be clients that disconnect before they
> > have received all data.
> > Could that make sense for your case?
> >
> >
> >
> >
> > On Thu, Apr 3, 2014 at 5:26 PM, Lee Hinde <[email protected]> wrote:
> >> I get these errors daily. Googling them suggests errors in file
> uploads, but
> >> my app doesn't do that (at this install). Then I noticed in the log
> that the
> >> error came from my ip address. If I look at the access log I wasn't
> doing
> >> anything that generated errors on my end.
> >>
> >> [Tue Apr 01 17:17:22 2014] [error] [client myipaddress] mod_wsgi
> >> (pid=58411): Exception occurred processing WSGI script
> >> '/Users/recenroll/Sites/virtual/recenroll/recenroll/recenroll/wsgi.py'.
> >> [Tue Apr 01 17:17:22 2014] [error] [client myipaddress] IOError: failed
> to
> >> write data
> >>
> >> I'm reading up now on expanding logging errors. But I'm throwing this
> out
> >> there in case there's somewhere else I should be looking.
> >>
> >> --
> >> You received this message because you are subscribed to the Google
> Groups
> >> "modwsgi" group.
> >> To unsubscribe from this group and stop receiving emails from it, send
> an
> >> email to [email protected].
> >> To post to this group, send email to [email protected].
> >> Visit this group at http://groups.google.com/group/modwsgi.
> >> For more options, visit https://groups.google.com/d/optout.
> >
> > --
> > You received this message because you are subscribed to the Google
> Groups "modwsgi" group.
> > To unsubscribe from this group and stop receiving emails from it, send
> an email to [email protected].
> > To post to this group, send email to [email protected].
> > Visit this group at http://groups.google.com/group/modwsgi.
> > For more options, visit https://groups.google.com/d/optout.
>
> --
> You received this message because you are subscribed to the Google Groups
> "modwsgi" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> To post to this group, send email to [email protected].
> Visit this group at http://groups.google.com/group/modwsgi.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"modwsgi" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/modwsgi.
For more options, visit https://groups.google.com/d/optout.

Reply via email to