[prev in list] [next in list] [prev in thread] [next in thread] 

List:       uwsgi
Subject:    [uWSGI] segmentation fault
From:       lukasz () czuja ! pl (=?UTF-8?B?xYF1a2FzeiBDenVqYQ==?=)
Date:       2011-07-03 17:39:00
Message-ID: 4E10A934.3090800 () czuja ! pl
[Download RAW message or body]



W dniu 25.06.2011 10:30, Roberto De Ioris pisze:
>> Hello,
>>
>> W dniu 23.06.2011 11:42, Roberto De Ioris pisze:
>>>> Yep, it works without<threads>.
>>>>
>>>> If it helps,<enable-threads>   is fine and nothing explodes when I
>>>> launch a pack of "ScaleWorker" threads in post_fork_hook.
>>>>
>>>> -Schmidty
>>>>
>>> I have finally found the deadlock. As soon as i will came back from
>>> europython i will fix it.
>> Glad to hear. Do you want me to check on the bug I experienced with
>> --lazy mode and wrote couple posts ago?
>
>
> The problem raises because some of the checks in module loading simply
> call exit(1) on errors. This triggers a reload.
>
> A good part of this issue should be fixed in current tip, but after the
> 0.9.8.1 release i will focus on allowing uWSGI to survive to all of the
> loading errors in dynamic mode.
OK, I switched to 0.9.8.1, the error there seems as you say partially 
resolved (dont mind the timespamps), so while starting the app

(some python programming error occurs while creating app, then...)
> 2011-03-07 19:33:11 - DAMN ! worker 1 (pid: 5334) died :( trying 
> respawn ...
> 2011-03-07 19:33:11 - Loading paste environment: 
> config:/path/to/project.ini
> 2011-03-07 19:33:11 - Respawned uWSGI worker 1 (new pid: 5341)

then after trying to stop it:

> 2011-03-07 19:26:52 - SIGINT/SIGQUIT received...killing workers...
> 2011-03-07 19:26:52 - SIGINT/SIGQUIT received...killing workers...
> 2011-03-07 19:26:52 - SIGINT/SIGQUIT received...killing workers...
> 2011-03-07 19:26:52 - SIGINT/SIGQUIT received...killing workers...
> 2011-03-07 19:26:52 - worker 1 (pid: 5031) is taking too much time to 
> die...NO MERCY !!!
> 2011-03-07 19:26:52 - SIGINT/SIGQUIT received...killing workers...
> 2011-03-07 19:26:52 - goodbye to uWSGI.

message about killing workers appears very fast (utilizing quite a lot 
of cpu) and finally it stops. Do you want the config also ?

>> Any success on how to implement PyPy support in uWSGI ?
>
> The idea si having a pretty standard pypy environment running on the uWSGI
> python_plugin. Pratically the python plugin will import pypy and will load
> the wsgi code in it. In theory it should work, in practice no-one knows :)
>

any ETA ? :)

Regards.

-- 
Pozdrawiam,

?ukasz Czuja

Programista / Analityk / Architekt IT


[prev in list] [next in list] [prev in thread] [next in thread]