> On 4 Jan 2016, at 7:59 AM, Graham Dumpleton <[email protected]> > wrote: > > >> On 4 Jan 2016, at 6:12 AM, Mike Panoff <[email protected] >> <mailto:[email protected]>> wrote: >> >> [Sun Jan 03 12:52:36.749621 2016] [wsgi:info] [pid 32285] [client >> 70.117.108.188:54845] mod_wsgi (pid=32285, process='', >> application='app.mydomain.com <http://app.mydomain.com/>|'): Loading WSGI >> script '/home/www-data/web2py/wsgihandler.py'. >> [Sun Jan 03 12:52:37.838996 2016] [core:notice] [pid 21975] AH00052: child >> pid 32285 exit signal Segmentation fault (11) > The log messages above indicate that you are not running with: > > WSGIApplicationGroup %{GLOBAL} > > This is because the ‘application’ should be showing as an empty string if it > was. > > Show your mod_wsgi configuration so can see how you set things up. > > As Mike pointed out, not using the main interpreter context and using C > extension modules which don’t work properly in sub interpreters is the > primary cause of crashes. > > In addition to check your configuration and showing us what you are using, > also provide output from ‘pip freeze’. Can then try and identify what third > party package for Python you are using which is known to crash when used in > sub interpreters.
BTW, you should avoid using embedded mode as you are as well. Better to use daemon mode. If you think you are using daemon mode, then there truly is something not right about your configuration. Graham -- You received this message because you are subscribed to the Google Groups "modwsgi" 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 https://groups.google.com/group/modwsgi. For more options, visit https://groups.google.com/d/optout.
