On 03/07/2014, at 4:10 AM, Alex Wu <[email protected]> wrote: > Once for awhile, we have seen a segmenation fault from wsgi 3.5 (latest > release)
The latest version of mod_wsgi is actually 4.2.5. https://github.com/GrahamDumpleton/mod_wsgi/releases Is it possible for you to upgrade, or are you stuck with using binary packages provided by your operating system. > (gdb) bt > #0 0x00007fecf9608751 in ?? () from /lib/x86_64-linux-gnu/libc.so.6 > #1 0x00007fecefaa43e6 in PyGrammar_RemoveAccelerators () from > /usr/lib/libpython2.7.so.1.0 > #2 0x00007fecef9c8641 in Py_Finalize () from /usr/lib/libpython2.7.so.1.0 > #3 0x00007fecefe42e32 in wsgi_python_term () at mod_wsgi.c:6167 > #4 0x00007fecefe4340a in wsgi_python_child_cleanup (data=<optimized out>) at > mod_wsgi.c:7208 > #5 0x00007fecf9b88a5c in run_cleanups (cref=0x7fecfbc30958) at > memory/unix/apr_pools.c:2352 > #6 0x00007fecf9b878eb in apr_pool_destroy (pool=0x7fecfbc30938) at > memory/unix/apr_pools.c:814 > #7 0x00007fecefe4d46c in wsgi_start_process (p=<optimized out>, > daemon=<optimized out>) at mod_wsgi.c:12245 > #8 0x00007fecefe4ea14 in wsgi_start_daemons (p=0x7fecfb7dd138) at > mod_wsgi.c:12446 > #9 wsgi_hook_init (pconf=0x7fecfb7dd138, ptemp=<optimized out>, > plog=<optimized out>, s=<optimized out>) at mod_wsgi.c:14017 > #10 0x00007fecfa49c113 in ap_run_post_config (pconf=0x7fecfb7dd138, > plog=0x7fecfb80a378, ptemp=0x7fecfb808348, s=0x7fecfb806538) at config.c:106 > #11 0x00007fecfa471993 in main (argc=15, argv=0x7fffe378fc78) at main.c:765 > > we run apache 2.5 with MPM worker. Not that this appears to be Apache related, but I haven't as yet tested mod_wsgi with Apache 2.5 development versions. Anyway, can describe where the Python installation you are using is installed. Are you truly using a version installed as the system wide Python. Strange problems can start to occur where mod_wsgi.so is picking up a libpython2.7.so corresponding to a system wide Python, as it is here, but you were trying to force mod_wsgi to use a different Python installation in a location such as /usr/local. If doing that and mod_wsgi isn't setup to find the right libpython2.7.so at run time and it is still using the system wide one, subtle issues can arise. Can you therefore indicate whether are setting and of the following: 1. WSGIPythonHome 2. WSGIPythonPath 3. python-home option to WSGIDaemonProcess 4. python-path option to WSGIDaemonProcess 5. Are you trying to use a Python virtual environment 6. If using the Python virtual environment, was the Python installation it depends on ever updated since the virtual environment was created If the answer is yes, what are they set to. Further, if you are manually updating sys.path in a WSGI script file, how is that being set and to what. 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 http://groups.google.com/group/modwsgi. For more options, visit https://groups.google.com/d/optout.
