Skip to content
This repository

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
Browse code

Beefed up 'If you get a segmentation fault' section in docs/modpython…

….txt

git-svn-id: http://code.djangoproject.com/svn/django/trunk@2311 bcc190cf-cafb-0310-a4f2-bffc1f526a37
  • Loading branch information...
commit e9a1e9fed66ba0424b7afa2c13b6ab62ea79efee 1 parent c1dded6
Adrian Holovaty authored February 16, 2006

Showing 1 changed file with 28 additions and 5 deletions. Show diff stats Hide diff stats

  1. 33  docs/modpython.txt
33  docs/modpython.txt
@@ -202,9 +202,32 @@ read, but it's how mod_python does things.)
202 202
 If you get a segmentation fault
203 203
 ===============================
204 204
 
205  
-If Apache causes a segmentation fault, it's probably because you're running
206  
-mod_python and mod_php in the same Apache instance, with MySQL as your database
207  
-backend. This is a known mod_python issue, not a Django issue, and there's more
208  
-information in the `mod_python FAQ entry`.
209  
-
  205
+If Apache causes a segmentation fault, there are two probable causes, neither
  206
+of which has to do with Django itself.
  207
+
  208
+    1. It may be because your Python code is importing the "pyexpat" module,
  209
+       which may conflict with the version embedded in Apache. For full
  210
+       information, see `Expat Causing Apache Crash`_.
  211
+    2. It may be because you're running mod_python and mod_php in the same
  212
+       Apache instance, with MySQL as your database backend. In some cases,
  213
+       this causes a known mod_python issue due to version conflicts in PHP and
  214
+       the Python MySQL backend. There's full information in the
  215
+       `mod_python FAQ entry`_.
  216
+
  217
+If you continue to have problems setting up mod_python, a good thing to do is
  218
+get a barebones mod_python site working, without the Django framework. This is
  219
+an easy way to isolate mod_python-specific problems. `Getting mod_python Working`_
  220
+details this procedure.
  221
+
  222
+The next step should be to edit your test code and add an import of any
  223
+Django-specific you're using -- your views, your models, your URLconf, your RSS
  224
+configuration, etc. Put these imports in your test handler function and access
  225
+your test URL in a browser. If this causes a crash, you've confirmed it's the
  226
+importing of Django code that causes the problem. Gradually reduce the set of
  227
+imports until it stops crashing, so as to find the specific module that causes
  228
+the problem. Drop down further into modules and look into their imports, as
  229
+necessary.
  230
+
  231
+.. _Expat Causing Apache Crash: http://www.dscpl.com.au/articles/modpython-006.html
210 232
 .. _mod_python FAQ entry: http://modpython.org/FAQ/faqw.py?req=show&file=faq02.013.htp
  233
+.. _Getting mod_python Working: http://www.dscpl.com.au/articles/modpython-001.html

0 notes on commit e9a1e9f

Please sign in to comment.
Something went wrong with that request. Please try again.