On Wed, Jun 22, 2011 at 1:28 AM, Roberto De Ioris <[email protected]> wrote:
>
>> Ok, I've done a bit more debugging on this. It appears that when I try
>> to import pymongo the app just freezes until timeout. I'm not sure
>> what it's actually doing, but it doesn't respond to the web server.
>>
>> Are there any issues with importing Python modules that use C extensions?
>
> No, as uWSGI is a python c extension itself :)
>
>
> It could be related to recent discovered threading problem (there is a
> deadlock somewhere), but on OSX it got imported without problems.
>
> If you are under Linux, can you attach a strace to the process (run it
> without threads, without master and with single process) and send the
> output ?
It looks like it's just waiting on a select.
waitpid(-1, 0xbff3a510, WNOHANG) = 0
epoll_wait(7, {}, 1, 1000) = 0
time(NULL) = 1308777958
time(NULL) = 1308777958
waitpid(-1, 0xbff3a510, WNOHANG) = 0
epoll_wait(7, {}, 1, 1000) = 0
time(NULL) = 1308777959
time(NULL) = 1308777959
So weird.
>
>>
>> I'm also have a bit of an issue seeing 500s. I put some intentional
>> error conditions in my application to test with and I just get a
>> generic 500 response and no log message saying what it might have
>> been.
>
>
>
> i am not sure i have understand what your problem is: you do not see
> traceback in uWSGI logs during exceptions ?
I'll try to reproduce this, but it was while trying to debug this
issue. I was unable to see any sort of stack, I just got a generic 500
and that was it.
>
>>
>> Trey
>>
>> On Tue, Jun 21, 2011 at 8:36 AM, Roberto De Ioris <[email protected]>
>> wrote:
>>>
>>>
>>>
>>>
>>>>
>>>> Khabok, I added UWSGI_PYTHONPATH to the directives as a last ditch
>>>> effort. The CHDIR should take care of it automatically. I believe
>>>> PYHOME is for specifying the PYTHON_HOME which is used for virtual
>>>> environments. PYTHONPATH and PYHOME are not interchangeable.
>>>
>>> Exaclty, there is no UWSGI_PYTHONPATH and UWSGI_PYHOME is for dynamic
>>> virtualenv
>>>
>>>>
>>>> Both of these are secondary to the issue at hand. When I try to modify
>>>> the site path (regardless of how or which pythonpath is currently
>>>> setup) it blocks uWSGI from doing anything. Commenting out those lines
>>>> causes it to function immediately.
>>>
>>> looks like some sort of loop in loading. Can you try adding the module
>>> with --pythonpath se we can catch if the process got blocked ?
>>>
>>>
>>> --
>>> Roberto De Ioris
>>> http://unbit.it
>>> _______________________________________________
>>> 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
>>
>
>
> --
> Roberto De Ioris
> http://unbit.it
> _______________________________________________
> 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
