Re: Apache Segfaults
On Feb 2, 4:21 am, Alex Kopp <loafer...@gmail.com> wrote:
> Yes, the development server works fine on the server I am getting the
> apache error. The server is ubuntu and everything is installed either via
> apt-get or pip. I'm not copying any modules from machine to machine.
This is out of my expertise area... But, some other guesses & hints
below:
- Maybe a threading issue? If you disable multi-threaded mode of
mod_wsgi in Apache conf does the segfault still happen? mod_wsgi
documentation tells you how to do this.
- Next, I would maybe alter the installed Django to do debug printing
from various places (most notably, before the import of psycopg2 in
django/db/backends/psycopg2/base.py and in settings.py so that we can
see if even settings.py get imported, ever). This way you can likely
"bisect" the place where the error happens.
- Next (or alternatively), try to create a minimal Django project,
adding your dependencies one at a time until you hit the error.
- It seems a little suspicious this happens under apache, but not
under dev-server. Are there any differences in the Python used, or in
the path used?
Unfortunately this is all the help I can give you.
- Anssi
--
You received this message because you are subscribed to the Google Groups "Django users" group.
To post to this group, send email to django-users@googlegroups.com.
To unsubscribe from this group, send email to django-users+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
0 Comments:
Post a Comment
Subscribe to Post Comments [Atom]
<< Home