Yes i am using mod_wsgi/3.3. And I am not sure about WSGIDaemonProcess/WSGIProcessGroup directives, but yes there is nothing defined in apache as such.
in Apache it defines only: WSGIScriptAlias /web /op/ww/web/apps.wsgi After you said then i tried to refresh the page frequently but i am not getting this error. But when i check the log, it is coming every now and then. As this application is using by big audiance, so not sure what is the root cause. Its basically a bug tracking system. I am not able to reproduce it in my development environment. So not sure what is the root cause of this issue. Thanks, On Wed, Jul 6, 2011 at 2:02 AM, Graham Dumpleton <[email protected] > wrote: > On 6 July 2011 05:09, kamal sharma <[email protected]> wrote: > > Thanks for the quick response. > > Here are the version details: > > Apache/2.2.16 > > mod_wsgi/3.3 > > Python/2.6.6 > > So do we need to change anywhere or only upgrade mod_wsgi/3.3 will solve > > this problem. BTW what version i have to install? > > But you say you have mod_wsgi 3.3 already. Am confused. > > BTW, what mod_wsgi mode are you using? Embedded or Daemon? > > If you don't know what I am talking about, are you using > WSGIDaemonProcess/WSGIProcessGroup directives? > > Also indicate whether the behaviour I described seems to match what > you are doing, or whether you are saying that you get this message on > every single page refresh and not if/just when interrupting rendering > of the current page. > > Graham > > > Thanks, > > > > On Tue, Jul 5, 2011 at 11:03 PM, Graham Dumpleton > > <[email protected]> wrote: > >> > >> You would only be seeing this if you refresh a page before the > >> response from a prior request had been completely written back by the > >> web application. > >> > >> What the error is saying is that while writing back a response, the > >> socket connection from the client browser was severed prematurely > >> before the client had read all the response. This would occur where > >> you pressed refresh in a browser before waiting for original page to > >> be completely returned and drawn in the browser. > >> > >> So, it should be an isolated action due to conscious action on the > >> part of the user. You should not be seeing this on ever request. > >> > >> That you are even seeing this suggests you are perhaps using an older > >> version of mod_wsgi as the message is suppressed in most cases with > >> mod_wsgi 3.X. > >> > >> The original issue about the messages that can be generated when > >> browser closes connection early can be seen at: > >> > >> http://code.google.com/p/modwsgi/issues/detail?id=29&can=1 > >> > >> What version of mod_wsgi are you using? > >> > >> Graham > >> > >> On 6 July 2011 03:15, pankaj <[email protected]> wrote: > >> > Hi, > >> > > >> > Whenever i refresh the web page then i got below error in Apache error > >> > log file. I have googled about this issue, but did not find the proper > >> > solution for this issue. > >> > > >> > mod_wsgi (pid=9655): Exception occurred processing WSGI script > '/x/y/z/ > >> > web/apps.wsgi'. > >> > IOError: failed to write data > >> > > >> > my apps.wsgi script looks like this: > >> > > >> > import os, sys > >> > # figure out where on disk this gnatatui install is hiding > >> > base_path = __file__.split('/web/apps.wsgi')[0] > >> > > >> > # and add it to sys.path > >> > for path in ('/op/ww/dj/django-trunk', base_path): > >> > if path not in sys.path: > >> > sys.path.append(path) > >> > > >> > os.environ['DJANGO_SETTINGS_MODULE'] = 'web.settings' > >> > > >> > import django.core.handlers.wsgi > >> > > >> > _application = django.core.handlers.wsgi.WSGIHandler() > >> > > >> > def application(environ, start_response): > >> > > >> > base_url = environ['SCRIPT_NAME'][1:] # drop leading slash > >> > if base_url != 'web': > >> > from django.conf import settings > >> > settings.BASE_URL = base_url > >> > > >> > # Adjust PATH_INFO to get around a Djago bug. See: > >> > # http://code.google.com/p/modwsgi/wiki/IntegrationWithDjango > >> > environ['PATH_INFO'] = environ['SCRIPT_NAME'] + > >> > environ['PATH_INFO'] > >> > return _application(environ, start_response) > >> > > >> > > >> > Please let me know if you need any more info. > >> > > >> > Any help will be highly appreciate. > >> > > >> > Thanks. > >> > > >> > -- > >> > You received this message because you are subscribed to the Google > >> > Groups "modwsgi" group. > >> > To post to this group, send email to [email protected]. > >> > To unsubscribe from this group, send email to > >> > [email protected]. > >> > For more options, visit this group at > >> > http://groups.google.com/group/modwsgi?hl=en. > >> > > >> > > >> > >> -- > >> You received this message because you are subscribed to the Google > Groups > >> "modwsgi" group. > >> To post to this group, send email to [email protected]. > >> To unsubscribe from this group, send email to > >> [email protected]. > >> For more options, visit this group at > >> http://groups.google.com/group/modwsgi?hl=en. > >> > > > > > > -- > You received this message because you are subscribed to the Google Groups > "modwsgi" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/modwsgi?hl=en. > > -- You received this message because you are subscribed to the Google Groups "modwsgi" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/modwsgi?hl=en.
