Hi, On Tue, Aug 21, 2012 at 3:28 PM, Roberto De Ioris <[email protected]> wrote: > > Il giorno 21/ago/2012, alle ore 11:43, Janoš Guljaš <[email protected]> ha > scritto: > >> On Tue, Aug 21, 2012 at 6:33 AM, Roberto De Ioris <[email protected]> wrote: >>> >>>> Hi Roberto, >>>> >>>> This is the log with a backtrace in it: >>>> >>>> $ uwsgi --plugins python26,http --uid janos --gid janos -s >>>> /tmp/wiki.sock --chmod-socket 666 --wsgi-file >>>> /usr/share/moin/server/moin.wsgi --http 0.0.0.0:3031 >>>> *** Starting uWSGI 1.2.3-debian (32bit) on [Mon Aug 20 22:30:28 2012] *** >>>> compiled with version: 4.7.1 on 16 July 2012 21:23:39 >>>> detected number of CPU cores: 2 >>>> current working directory: /home/janos >>>> detected binary path: /usr/bin/uwsgi-core >>>> *** WARNING: you are running uWSGI without its master process manager *** >>>> your memory page size is 4096 bytes >>>> detected max file descriptor number: 1024 >>>> lock engine: pthread robust mutexes >>>> uWSGI http bound on 0.0.0.0:3031 fd 3 >>>> spawned uWSGI http 1 (pid: 1972) >>>> chmod() socket to 666 for lazy and brave users >>>> uwsgi socket 0 bound to UNIX address /tmp/wiki.sock fd 6 >>>> Python version: 2.6.8 (unknown, Jun 28 2012, 18:31:35) [GCC 4.7.1] >>>> *** Python threads support is disabled. You can enable it with >>>> --enable-threads *** >>>> Python main interpreter initialized at 0xa05a558 >>>> your server socket listen backlog is limited to 100 connections >>>> *** Operational MODE: single process *** >>>> 2012-08-20 22:30:29,214 WARNING MoinMoin.log:139 using logging >>>> configuration read from built-in fallback in MoinMoin.log module! >>>> WSGI app 0 (mountpoint='') ready in 0 seconds on interpreter 0xa05a558 >>>> pid: 1971 (default app) >>>> *** uWSGI is running in multiple interpreter mode *** >>>> spawned uWSGI worker 1 (and the only) (pid: 1971, cores: 1) >>>> 2012-08-20 22:30:33,454 INFO MoinMoin.config.multiconfig:93 using farm >>>> config: /etc/moin/farmconfig.py >>>> 2012-08-20 22:30:33,482 INFO MoinMoin.config.multiconfig:127 using >>>> wiki config: /etc/moin/mywiki.py >>>> !!! uWSGI process 1971 got Segmentation Fault !!! >>>> *** backtrace of 1971 *** >>>> uwsgi(uwsgi_backtrace+0x2a) [0x8079dfa] >>>> uwsgi(uwsgi_segfault+0x2a) [0x8079eea] >>>> [0xb7734400] >>>> /usr/lib/libpython2.6.so.1.0(PyObject_RichCompare+0x46) [0xb6cfc966] >>>> /usr/lib/libpython2.6.so.1.0(PyEval_EvalFrameEx+0x2e26) [0xb6d5c0d6] >>>> /usr/lib/libpython2.6.so.1.0(PyEval_EvalCodeEx+0x871) [0xb6d5fc91] >>>> /usr/lib/libpython2.6.so.1.0(PyEval_EvalCode+0x63) [0xb6d5fe33] >>>> /usr/lib/libpython2.6.so.1.0(PyEval_EvalFrameEx+0x53ca) [0xb6d5e67a] >>>> /usr/lib/libpython2.6.so.1.0(PyEval_EvalCodeEx+0x871) [0xb6d5fc91] >>>> /usr/lib/libpython2.6.so.1.0(PyEval_EvalFrameEx+0x4715) [0xb6d5d9c5] >>>> /usr/lib/libpython2.6.so.1.0(PyEval_EvalCodeEx+0x871) [0xb6d5fc91] >>>> /usr/lib/libpython2.6.so.1.0(PyEval_EvalFrameEx+0x4715) [0xb6d5d9c5] >>>> /usr/lib/libpython2.6.so.1.0(PyEval_EvalCodeEx+0x871) [0xb6d5fc91] >>>> /usr/lib/libpython2.6.so.1.0(PyEval_EvalFrameEx+0x4715) [0xb6d5d9c5] >>>> /usr/lib/libpython2.6.so.1.0(PyEval_EvalCodeEx+0x871) [0xb6d5fc91] >>>> /usr/lib/libpython2.6.so.1.0(PyEval_EvalFrameEx+0x4715) [0xb6d5d9c5] >>>> /usr/lib/libpython2.6.so.1.0(PyEval_EvalCodeEx+0x871) [0xb6d5fc91] >>>> /usr/lib/libpython2.6.so.1.0(PyEval_EvalFrameEx+0x4715) [0xb6d5d9c5] >>>> /usr/lib/libpython2.6.so.1.0(PyEval_EvalCodeEx+0x871) [0xb6d5fc91] >>>> /usr/lib/libpython2.6.so.1.0(PyEval_EvalFrameEx+0x4715) [0xb6d5d9c5] >>>> /usr/lib/libpython2.6.so.1.0(PyEval_EvalFrameEx+0x49fb) [0xb6d5dcab] >>>> /usr/lib/libpython2.6.so.1.0(PyEval_EvalCodeEx+0x871) [0xb6d5fc91] >>>> /usr/lib/libpython2.6.so.1.0(+0x5dac7) [0xb6ce5ac7] >>>> /usr/lib/libpython2.6.so.1.0(PyObject_Call+0x60) [0xb6cb9800] >>>> /usr/lib/libpython2.6.so.1.0(+0x4048b) [0xb6cc848b] >>>> /usr/lib/libpython2.6.so.1.0(PyObject_Call+0x60) [0xb6cb9800] >>>> /usr/lib/libpython2.6.so.1.0(+0x940e4) [0xb6d1c0e4] >>>> /usr/lib/libpython2.6.so.1.0(PyObject_Call+0x60) [0xb6cb9800] >>>> /usr/lib/libpython2.6.so.1.0(PyEval_EvalFrameEx+0x29cd) [0xb6d5bc7d] >>>> /usr/lib/libpython2.6.so.1.0(PyEval_EvalCodeEx+0x871) [0xb6d5fc91] >>>> /usr/lib/libpython2.6.so.1.0(+0x5dac7) [0xb6ce5ac7] >>>> /usr/lib/libpython2.6.so.1.0(PyObject_Call+0x60) [0xb6cb9800] >>>> /usr/lib/libpython2.6.so.1.0(+0x4048b) [0xb6cc848b] >>>> /usr/lib/libpython2.6.so.1.0(PyObject_Call+0x60) [0xb6cb9800] >>>> /usr/lib/libpython2.6.so.1.0(+0x940e4) [0xb6d1c0e4] >>>> /usr/lib/libpython2.6.so.1.0(PyObject_Call+0x60) [0xb6cb9800] >>>> /usr/lib/libpython2.6.so.1.0(PyEval_CallObjectWithKeywords+0x5b) >>>> [0xb6d58cab] >>>> /usr/lib/uwsgi/plugins/python26_plugin.so(python_call+0x3e) [0xb6f27d8e] >>>> /usr/lib/uwsgi/plugins/python26_plugin.so(uwsgi_request_subhandler_wsgi+0x4aa) >>>> [0xb6f2b9fa] >>>> /usr/lib/uwsgi/plugins/python26_plugin.so(uwsgi_request_wsgi+0x11b) >>>> [0xb6f2a31b] >>>> uwsgi(wsgi_req_recv+0x79) [0x8054889] >>>> uwsgi(simple_loop+0x134) [0x80749d4] >>>> uwsgi(uwsgi_ignition+0x185) [0x807a375] >>>> uwsgi(uwsgi_start+0x2eba) [0x807dc2a] >>>> uwsgi(main+0xff9) [0x8054219] >>>> /lib/i386-linux-gnu/i686/cmov/libc.so.6(__libc_start_main+0xe6) >>>> [0xb72e1e46] >>>> uwsgi() [0x8054329] >>>> *** end of backtrace *** >>>> >>>> >>> >>> The segfault is on the python side, can you try adding --enable-threads ? >> >> There is the same backtrace log with threads support enabled >> (--enable-threads). >> _______________________________________________ >> > > > I was not able to reproduce the problem, can you try with another python > version ?
It looks like that the issue is only with python 2.6. If there cached files in pages/*/cache, that are created by any other python version (using uwsgi python plugin != 2.6) and then changing the plugin to python 2.6, it raises a segmentation fault. > > Is this an ARM system ? No, it is x86 32 bit system. > > -- > Roberto De Ioris > http://unbit.it > JID: [email protected] > > _______________________________________________ > uWSGI mailing list > [email protected] > http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi Regards, Janos _______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
