Re: Deploy with wsgi causes python library to fail.

On Wed, Oct 29, 2014 at 1:44 PM, Bohdan Anderson
<bohdan.anderson@gmail.com> wrote:
> 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.

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

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscribe@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/CAFHbX1KZAEjp3Vd%3D_jhQ8rucuiFix5ik3yQKAhP5ZV6Y7N6w7w%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.