Appreciate the quick reply! As I read somewhere else the reason seems to be that uwsgi was compiled with a 'system' version rather than the python virtualenv version. I didn't try your solution, I recompiled uwsgi after having deleted libxml2 from my system and the app works without complaining. I've also found that the xml file was used to set multiple pythonpath's so I can easily add them on the ini file instead.
Best, Markos On Wed, Nov 23, 2016 at 7:03 PM, Roberto De Ioris <[email protected]> wrote: > > > Dear all, > > > > I'm using uwsgi on a Plone app using unweb.recipe.uwsgi. > > Uwsgi 2.0.14 compiles without warnings but when I try to serve the app it > > segfaults ...I believe it has to do with lxml but has no clues to support > > this and most important find a solution. Any suggestions are highly > > welcome. > > > > Regards, > > Markos > > > > > > > > uwsgi segfault traceback > > > > > > 2016-11-23 18:01:51,641 WARNI [OFS.Uninstalled][uWSGIWorker4Core0] Could > > not import class 'CSCachingPolicyManager' from module > > 'Products.CacheSetup.content.caching_policy_manager' > > !!! uWSGI process 22311 got Segmentation Fault !!! > > *** backtrace of 22311 *** > > /store/emsite/4.5.1/bin/uwsgi(uwsgi_backtrace+0x30) [0x469f50] > > /store/emsite/4.5.1/bin/uwsgi(uwsgi_segfault+0x21) [0x46a2f1] > > /lib/x86_64-linux-gnu/libc.so.6(+0x350e0) [0x7fee0d4490e0] > > /usr/lib/x86_64-linux-gnu/libxml2.so.2(xmlDictOwns+0xf) [0x7fee0e27965f] > > /usr/lib/x86_64-linux-gnu/libxml2.so.2(xmlSAX2Characters+0x27f) > > [0x7fee0e27c5af] > > /store/emsite/4.5.1/eggs/lxml-2.3-py2.7-linux-x86_64.egg/lxm > l/etree.so(+0x19b7ae) > > [0x7fee0424d7ae] > > /store/emsite/4.5.1/eggs/lxml-2.3-py2.7-linux-x86_64.egg/lxm > l/etree.so(htmlParseChunk+0xf61) > > [0x7fee0424fd71] > > /store/emsite/4.5.1/eggs/lxml-2.3-py2.7-linux-x86_64.egg/lxm > l/etree.so(+0xa8649) > > [0x7fee0415a649] > > /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyEval_EvalFrameEx+0x5462) > > [0x7fee0db6ce02] > > /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyEval_EvalCodeEx+0x820) > > [0x7fee0dbe0190] > > /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyEval_EvalFrameEx+0x57d1) > > [0x7fee0db6d171] > > /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyEval_EvalCodeEx+0x820) > > [0x7fee0dbe0190] > > /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyEval_EvalFrameEx+0x57d1) > > [0x7fee0db6d171] > > /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyEval_EvalFrameEx+0x58dd) > > [0x7fee0db6d27d] > > /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyEval_EvalFrameEx+0x58dd) > > [0x7fee0db6d27d] > > /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyEval_EvalCodeEx+0x820) > > [0x7fee0dbe0190] > > /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyEval_EvalFrameEx+0x57d1) > > [0x7fee0db6d171] > > /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyEval_EvalCodeEx+0x820) > > [0x7fee0dbe0190] > > /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyEval_EvalFrameEx+0x57d1) > > [0x7fee0db6d171] > > /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyEval_EvalCodeEx+0x820) > > [0x7fee0dbe0190] > > /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(+0x13932c) > [0x7fee0db2f32c] > > /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyObject_Call+0x43) > > [0x7fee0db37be3] > > /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(+0x1840e5) > [0x7fee0db7a0e5] > > /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyObject_Call+0x43) > > [0x7fee0db37be3] > > /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(+0x184966) > [0x7fee0db7a966] > > /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyObject_Call+0x43) > > [0x7fee0db37be3] > > /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyEval_EvalFrameEx+0x3aa2) > > [0x7fee0db6b442] > > /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyEval_EvalCodeEx+0x820) > > [0x7fee0dbe0190] > > /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(+0x13932c) > [0x7fee0db2f32c] > > /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyObject_Call+0x43) > > [0x7fee0db37be3] > > /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(+0x1840e5) > [0x7fee0db7a0e5] > > /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyObject_Call+0x43) > > [0x7fee0db37be3] > > /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(+0x184966) > [0x7fee0db7a966] > > /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyObject_Call+0x43) > > [0x7fee0db37be3] > > /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyEval_EvalFrameEx+0x3aa2) > > [0x7fee0db6b442] > > /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyEval_EvalCodeEx+0x820) > > [0x7fee0dbe0190] > > /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(+0x13932c) > [0x7fee0db2f32c] > > /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyObject_Call+0x43) > > [0x7fee0db37be3] > > /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(+0x1840e5) > [0x7fee0db7a0e5] > > /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyObject_Call+0x43) > > [0x7fee0db37be3] > > /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(+0x184966) > [0x7fee0db7a966] > > /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyObject_Call+0x43) > > [0x7fee0db37be3] > > /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyEval_CallObj > ectWithKeywords+0x47) > > [0x7fee0dbdf6e7] > > /store/emsite/4.5.1/bin/uwsgi(python_call+0x11) [0x4811a1] > > /store/emsite/4.5.1/bin/uwsgi(uwsgi_request_wsgi+0x101) [0x483231] > > /store/emsite/4.5.1/bin/uwsgi(wsgi_req_recv+0xa2) [0x41f742] > > /store/emsite/4.5.1/bin/uwsgi(simple_loop_run+0xc4) [0x4661d4] > > /store/emsite/4.5.1/bin/uwsgi(uwsgi_ignition+0x195) [0x46a545] > > /store/emsite/4.5.1/bin/uwsgi(uwsgi_worker_run+0x26d) [0x46ed4d] > > /store/emsite/4.5.1/bin/uwsgi() [0x46f32c] > > /store/emsite/4.5.1/bin/uwsgi(_start+0) [0x41edde] > > /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf5) [0x7fee0d435b45] > > /store/emsite/4.5.1/bin/uwsgi() [0x41ee07] > > *** end of backtrace *** > > /store/emsite/4.5.1/eggs/Products.CMFCore-2.2.6-py2.7.egg/ > Products/CMFCore/DirectoryView.py:493: > > UserWarning: DirectoryView plumi_content_custom_templates refers to a > > non-existing path 'plumi.content:skins/plumi_content_custom_templates' > > (self.id, reg_key), UserWarning) > > DAMN ! worker 4 (pid: 22311) died, killed by signal 11 :( trying respawn > > ... > > Respawned uWSGI worker 4 (new pid: 22362) > > mapping worker 4 to CPUs: 3 > > > > ------------------- > > Configuration: > > > > > As you do not use xml in uWSGi you could try disablign it from the build: > > UWSGI_PROFILE_OVERRIDE="xml=false" pip install uwsgi > > Let me know if this fixes the issue > > -- > Roberto De Ioris > http://unbit.com > _______________________________________________ > uWSGI mailing list > [email protected] > http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi >
_______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
