search

ramkrishanbhatt / modwsgi

Automatically exported from code.google.com/p/modwsgi
0 stars 0 forks source link

mod_wsgi 2.0 sometimes displays blank page #80

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
Sometimes I see blank page instead of page I would like to see. I don't
know how to reproduce this problem exactly but I will assist as much as I can.

Situation:
I have virtual machine with 256 Mb RAM. There are about 180Mb that can be
used by Apache. I have 4 sites running on mod_wsgi: two pylons application,
trac site and mercurial site.

I have not experiences such problems with mod_wsgi 1.2.

I see Segmentation faul message in log:
[Mon Apr 28 09:26:42 2008] [info] mod_wsgi (pid=13543): Create interpreter
'trac.sandbox.lt|'.
[Mon Apr 28 09:26:45 2008] [notice] child pid 13543 exit signal
Segmentation fault (11)
[Mon Apr 28 09:26:46 2008] [info] mod_wsgi (pid=15378): Attach interpreter ''.
[Mon Apr 28 09:26:49 2008] [info] mod_wsgi (pid=15378): Create interpreter
'hg.sandbox.lt|'.
[Mon Apr 28 09:27:01 2008] [info] mod_wsgi (pid=15378): Create interpreter
'skaityta.lt|'.

Original issue reported on code.google.com by dalius.d...@gmail.com on 28 Apr 2008 at 9:37

GoogleCodeExporter commented 8 years ago 
The mod_wsgi daemon process is crashing, this is evident from 'exit signal 
Segmentation fault (11)'. When the 
daemon process crashes after headers have been sent, but prior to any response 
content being sent, then you 
will see a blank page.

Crashes can be caused by various shared library conflicts, or third party C 
extension modules not designed to 
work properly in secondary sub interpreters. Read through:

  http://code.google.com/p/modwsgi/wiki/ApplicationIssues

for examples of what to look for.

Use of mod_python at same time as mod_wsgi may also be an issue. Read through:

  http://code.google.com/p/modwsgi/wiki/InstallationIssues

You can try and debug problem by getting stack trace from gdb using techniques 
for debugging daemon 
process with gdb as described in:

  http://code.google.com/p/modwsgi/wiki/DebuggingTechniques

BTW, crashing processes is covered by FAQ entry in:

  http://code.google.com/p/modwsgi/wiki/FrequentlyAskedQuestions

If you can't from this come up with a solution, then post any gdb traceback you 
can get here. If you have 
trouble with trying to get a traceback, then take discussion over to mod_wsgi 
discussion group on Google 
groups.

Original comment by Graham.Dumpleton@gmail.com on 28 Apr 2008 at 11:15

GoogleCodeExporter commented 8 years ago 
Please close this issue. expat version mismatch case.

Original comment by dalius.d...@gmail.com on 28 Apr 2008 at 11:57

GoogleCodeExporter commented 8 years ago

Original comment by Graham.Dumpleton@gmail.com on 28 Apr 2008 at 12:00