Re: Apache Segfaults

On Feb 2, 3:47 am, Loafer <loafer...@gmail.com> wrote:
> Here's the setup:
>
> I have a Django website that is being run by Apache, and MySQL with no
> issues. I decided to implement some GIS features as an update. Since
> MySQL doesn't have much support for GIS, I decided to switch my
> database over to Postgres. After committing the changes to my SVN, and
> checking them out on my website, Apache now segfaults whenever I try
> and load my page. My code works fine on the manage.py development
> server though.
>
> I've literally spent the last 10 hours trying to figure out what is
> going on. Here's some information:
>
> Apache Log, Virtual Host Config, and django.wsgi file:http://dpaste.org/pJBc2/
> GDB Trace:http://dpaste.org/52pTk/

You seem to have some C-based module (psycopg2?) which isn't working
correctly under Apache, or more likely, with the Python you are using
when running under Apache. If you are copying the psycopg2 module (or
any other compiled C based module) from machine to machine things are
likely to break. The hint that this is a compiled module issue is
here:

warning: Selected architecture i386:x86-64 is not compatible with
reported target architecture i386
<SNIP>
(gdb) where
#0 0x00002aaab82998cd in ?? () from /usr/lib/python2.7/lib-dynload/
_ctypes.so

If you run the project using "development server" in the same machine
you get the Apache error do things work correctly?

- 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.