Hi, I had problems running Django with mod_python, so I had the possibility to investigate and obtain some detailed info, which I'd like to share here.
I'd like to suggest "Expat Causing Apache Crash", which explains problems caused due to mismatches in the version of the "expat" library embedded into Python and that linked into Apache, how to verifying if expat is the problem and finally a resolution. (http://www.dscpl.com.au/articles/modpython-006.html) Another reading is mod_python FAQ Entry - mod_python and MySQLDb won't work together (http://www.modpython.org/FAQ/faqw.py?req=show&file=faq02.013.htp) Then, a good way to obtain useful information that can be used to ask for help is - first of all - check if mod_python works alone, without involve Django. The procedure is detailed here: http://www.dscpl.com.au/articles/modpython-001.html. Again, it's useful to locate which is the problematic module (if it's true that an imported module causes the crash) that make the segmentation fault happen. For this I'd like to cite textually the answer I had on mod_python mailing list (here is the whole thread, in case anyone would care to read it, http://www.modpython.org/pipermail/mod_python/2005-December/019647.html): "Next step then would be to import into the handler of your test code, the module which you specify needs to be imported in order to make use of Django. If done in the test handler function, accessing the test URL will cause it to be imported and if it does crash at that point you have confirmed that it is the actual import of the Django stuff that is the problem. If that is confirmed, then look internally at Django and see what module it imports, and instead of importing the Django top level module, import what it imports. Gradually reduce the set of imports until it stops crashing so as to find the specific module that causes the problem. Drop down further into modules and look at their imports as necessary. This sort of process of elimination is the only way you are going to be able to narrow it down. Unless you can determine precisely which module is the issue, we aren't really going to be able to help." This is all I gathered around. HTH, regards --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" 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/django-users -~----------~----~----~----~------~----~------~--~---
