Deploy with wsgi causes python library to fail.

[Bohdan Anderson]

I can run in the testing server fine (python manage.py runserver 0.0.0.0:8000) but once I deploy to the server I'm not even getting the django error page in response to it's failure.
I looked into the apache log files and all I get is a generic error message "[notice] child pid 17364 exit signal Segmentation fault (11)".
I thought it might be because apache is run by a different user, so I rand django with the test server and it works fine for the apache user.

My question is what should my next steps be in debugging, has any one else encountered this before?

what I'm using is

Debian

MySQL

Apache

Django 

and the python package that is not working is librets

Any direction would be appreciated.

[Collin Anderson]

Hello,

Ouch.  Segmentation faults are never a good sign.

How do you know that it's librets that's not working?

You may want to open an issue at librets or ask on the mod-wsgi list.

Collin

[Tom Evans]

Get a core dump, (get debug symbols for python+httpd), run gdb on the
coredump, get a backtrace.

Is the suspected package installed as an egg by any chance?

Cheers

Tom