On Tue, Jun 16, 2015 at 4:39 PM, Paul Kraus <[email protected]> wrote:
>
> [core:notice] [pid 45371:tid 139899616245632] AH00094: Command line:
> '/usr/sbin/apache2'
> [core:notice] [pid 45371:tid 139899616245632] AH00051: child pid 45375
> exit signal Segmentation fault (11), possible coredump in /etc/apache2
> [core:notice] [pid 45371:tid 139899616245632] AH00051: child pid 55064
> exit signal Segmentation fault (11), possible coredump in /etc/apache2
>
If Apache crashes when using mod_wsgi it is usually due to some python
module that has C speedups/extensions that do not cope well with mod_wsgi.
One common reason is that the module uses the simplified GIL API, which
only works in the main python interpreter and not in sub-interpreters
(which mod_wsgi uses).
In many cases using "WSGIApplicationGroup %{GLOBAL}" inside your
application configuration solves the issues.
It that doesn't help you might want to check you are not linking to
multiple versions of the same library, for example if you have PHP in
apache and also use MySQL in your python application you might end up with
two different mysql versions being linked one from PHP and the other from
python which leads to crashes. This can be checked by running "ldd" against
the apache2 modules to see which library they are linking to.
In any case when you get a segfault is 90% related to a python module
relying on C code which doesn't cope with mod_wsgi, ODBC might be a
candidate, try uninstall the python odbc library and run your code against
SQLITE to see if it still crashes.
--
You received this message because you are subscribed to the Google Groups
"TurboGears" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/turbogears.
For more options, visit https://groups.google.com/d/optout.
