Re: [uWSGI] why? DAMN ! worker 1 (pid: 10705) died :( trying respawn ...

2019-04-10 Thread Roberto De Ioris

> I used gunicorn on the same file with pypy3 and pypy3 . Worked out of the
> box with the same code.  uwsgi with python2.7 works. I am gathering that
> devs  tend to prefer gunicorn for this reason because uwsgi is iffy with
> pypy
>
>

Hi, the pypy embedding api is something experimental by years in pypy
itself and afaik
the uWSGI pypy plugin has not got any update from 2015. Adding gevent to
the configuration is something impossible because uWSGI has its gevent
plugin based on the CPython api. If you want to use gevent with pypy in
uWSGI, you need to implement an ad-hoc c-layer or stick with pure-python
WSGI servers (like gunicorn)

Best

-- 
Roberto De Ioris
http://unbit.com
___
uWSGI mailing list
uWSGI@lists.unbit.it
http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi


Re: [uWSGI] why? DAMN ! worker 1 (pid: 10705) died :( trying respawn ...

2019-04-10 Thread David Montgomery
I used gunicorn on the same file with pypy3 and pypy3 . Worked out of the
box with the same code.  uwsgi with python2.7 works. I am gathering that
devs  tend to prefer gunicorn for this reason because uwsgi is iffy with
pypy

On Wed, Apr 10, 2019 at 9:03 PM Mikko Ohtamaa 
wrote:

>
>
> Why uWSGI?  I dont understand.  I am trying to run bottle with the
>> gevent loop with pypy2.
>>
>
> My gut feeling is that it
>
> 1) Either fails to load .py file
>
> 2) Starting Python dies due to an import error or other initialisation
> error
>
> In both cases it makes sense to check 1) Python entry point and path 2)
> PYTHONPATH 3) virtualenv.
>
> Br,
> Mikko
>
>
>>
>> I mean my code simply works if I run with built in server
>>
>> Here is my entry point in bottle:
>>
>> if __name__ == *"__main__"*:
>>
>> # Interactive mode
>>
>> run(host=*'localhost'*, port=8049,debug=True)  #,reloader=True
>>
>> else:
>>
>> # Mod WSGI launch
>>
>> os.chdir(os.path.dirname(__file__))
>>
>> application = default_app()
>>
>> uwsgi:
>>
>>   pidfile: /var/run/pixel.pid
>>
>>   loop: gevent
>>
>>   gevent: 20
>>
>>   b: 32768
>>
>>   listen: 1024
>>
>>   socket: 127.0.0.1:8030
>>
>>   processes: 4
>>
>>   master: true
>>
>>   enable-threads: true
>>
>>   pypy-lib: /opt/pypy/bin/libpypy-c.so
>>
>>   logto2: /tmp/pixel.log
>>
>>   touch-reload: /var/geoaiServerPixel/app.py
>>
>>   master-fifo: /tmp/uwsgi_api_master_fifo
>>
>>   pypy-wsgi-file: /var/geoaiServerPixel/app.py
>>
>>   pypy-pp: [/var/geoaiServerPixel]
>>
>>
>>
>> your processes number limit is 64064
>>
>> your memory page size is 4096 bytes
>>
>> detected max file descriptor number: 10
>>
>> lock engine: pthread robust mutexes
>>
>> thunder lock: disabled (you can enable it with --thunder-lock)
>>
>> uwsgi socket 0 bound to TCP address 127.0.0.1:8030 fd 3
>>
>> uWSGI running as root, you can use --uid/--gid/--chroot options
>>
>> *** WARNING: you are running uWSGI as root !!! (use the --uid flag) ***
>>
>> Initialized PyPy with Python 2.7.13 (990cef41fe11, Mar 21 2019, 12:14:52)
>>
>> [PyPy 7.1.0 with GCC 6.2.0 20160901]
>>
>> PyPy Home: /opt/pypy
>>
>> added [/var/geoaiServerPixel] to pythonpath
>>
>> uWSGI running as root, you can use --uid/--gid/--chroot options
>>
>> *** WARNING: you are running uWSGI as root !!! (use the --uid flag) ***
>>
>> your server socket listen backlog is limited to 1024 connections
>>
>> your mercy for graceful operations on workers is 60 seconds
>>
>> mapped 364600 bytes (356 KB) for 4 cores
>>
>> *** Operational MODE: preforking ***
>>
>> *** no app loaded. going in full dynamic mode ***
>>
>> uWSGI running as root, you can use --uid/--gid/--chroot options
>>
>> *** WARNING: you are running uWSGI as root !!! (use the --uid flag) ***
>>
>> *** uWSGI is running in multiple interpreter mode ***
>>
>> spawned uWSGI master process (pid: 10689)
>>
>> spawned uWSGI worker 1 (pid: 10705, cores: 1)
>>
>> unavailable loop engine !!!
>>
>> spawned uWSGI worker 2 (pid: 10706, cores: 1)
>>
>> unavailable loop engine !!!
>>
>> spawned uWSGI worker 3 (pid: 10707, cores: 1)
>>
>> unavailable loop engine !!!
>>
>> spawned uWSGI worker 4 (pid: 10710, cores: 1)
>>
>> DAMN ! worker 1 (pid: 10705) died :( trying respawn ...
>>
>> unavailable loop engine !!!
>>
>> Respawned uWSGI worker 1 (new pid: 10711)
>>
>> DAMN ! worker 2 (pid: 10706) died :( trying respawn ...
>>
>> unavailable loop engine !!!
>>
>> Respawned uWSGI worker 2 (new pid: 10712)
>>
>> DAMN ! worker 3 (pid: 10707) died :( trying respawn ...
>>
>> unavailable loop engine !!!
>>
>> Respawned uWSGI worker 3 (new pid: 10715)
>>
>> DAMN ! worker 4 (pid: 10710) died :( trying respawn ...
>>
>> unavailable loop engine !!!
>>
>> Respawned uWSGI worker 4 (new pid: 10716)
>>
>> DAMN ! worker 1 (pid: 10711) died :( trying respawn ..
>> ___
>> uWSGI mailing list
>> uWSGI@lists.unbit.it
>> http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
>>
> ___
> uWSGI mailing list
> uWSGI@lists.unbit.it
> http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
>
___
uWSGI mailing list
uWSGI@lists.unbit.it
http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi


Re: [uWSGI] why? DAMN ! worker 1 (pid: 10705) died :( trying respawn ...

2019-04-10 Thread Mikko Ohtamaa
Why uWSGI?  I dont understand.  I am trying to run bottle with the
> gevent loop with pypy2.
>

My gut feeling is that it

1) Either fails to load .py file

2) Starting Python dies due to an import error or other initialisation error

In both cases it makes sense to check 1) Python entry point and path 2)
PYTHONPATH 3) virtualenv.

Br,
Mikko


>
> I mean my code simply works if I run with built in server
>
> Here is my entry point in bottle:
>
> if __name__ == *"__main__"*:
>
> # Interactive mode
>
> run(host=*'localhost'*, port=8049,debug=True)  #,reloader=True
>
> else:
>
> # Mod WSGI launch
>
> os.chdir(os.path.dirname(__file__))
>
> application = default_app()
>
> uwsgi:
>
>   pidfile: /var/run/pixel.pid
>
>   loop: gevent
>
>   gevent: 20
>
>   b: 32768
>
>   listen: 1024
>
>   socket: 127.0.0.1:8030
>
>   processes: 4
>
>   master: true
>
>   enable-threads: true
>
>   pypy-lib: /opt/pypy/bin/libpypy-c.so
>
>   logto2: /tmp/pixel.log
>
>   touch-reload: /var/geoaiServerPixel/app.py
>
>   master-fifo: /tmp/uwsgi_api_master_fifo
>
>   pypy-wsgi-file: /var/geoaiServerPixel/app.py
>
>   pypy-pp: [/var/geoaiServerPixel]
>
>
>
> your processes number limit is 64064
>
> your memory page size is 4096 bytes
>
> detected max file descriptor number: 10
>
> lock engine: pthread robust mutexes
>
> thunder lock: disabled (you can enable it with --thunder-lock)
>
> uwsgi socket 0 bound to TCP address 127.0.0.1:8030 fd 3
>
> uWSGI running as root, you can use --uid/--gid/--chroot options
>
> *** WARNING: you are running uWSGI as root !!! (use the --uid flag) ***
>
> Initialized PyPy with Python 2.7.13 (990cef41fe11, Mar 21 2019, 12:14:52)
>
> [PyPy 7.1.0 with GCC 6.2.0 20160901]
>
> PyPy Home: /opt/pypy
>
> added [/var/geoaiServerPixel] to pythonpath
>
> uWSGI running as root, you can use --uid/--gid/--chroot options
>
> *** WARNING: you are running uWSGI as root !!! (use the --uid flag) ***
>
> your server socket listen backlog is limited to 1024 connections
>
> your mercy for graceful operations on workers is 60 seconds
>
> mapped 364600 bytes (356 KB) for 4 cores
>
> *** Operational MODE: preforking ***
>
> *** no app loaded. going in full dynamic mode ***
>
> uWSGI running as root, you can use --uid/--gid/--chroot options
>
> *** WARNING: you are running uWSGI as root !!! (use the --uid flag) ***
>
> *** uWSGI is running in multiple interpreter mode ***
>
> spawned uWSGI master process (pid: 10689)
>
> spawned uWSGI worker 1 (pid: 10705, cores: 1)
>
> unavailable loop engine !!!
>
> spawned uWSGI worker 2 (pid: 10706, cores: 1)
>
> unavailable loop engine !!!
>
> spawned uWSGI worker 3 (pid: 10707, cores: 1)
>
> unavailable loop engine !!!
>
> spawned uWSGI worker 4 (pid: 10710, cores: 1)
>
> DAMN ! worker 1 (pid: 10705) died :( trying respawn ...
>
> unavailable loop engine !!!
>
> Respawned uWSGI worker 1 (new pid: 10711)
>
> DAMN ! worker 2 (pid: 10706) died :( trying respawn ...
>
> unavailable loop engine !!!
>
> Respawned uWSGI worker 2 (new pid: 10712)
>
> DAMN ! worker 3 (pid: 10707) died :( trying respawn ...
>
> unavailable loop engine !!!
>
> Respawned uWSGI worker 3 (new pid: 10715)
>
> DAMN ! worker 4 (pid: 10710) died :( trying respawn ...
>
> unavailable loop engine !!!
>
> Respawned uWSGI worker 4 (new pid: 10716)
>
> DAMN ! worker 1 (pid: 10711) died :( trying respawn ..
> ___
> uWSGI mailing list
> uWSGI@lists.unbit.it
> http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
>
___
uWSGI mailing list
uWSGI@lists.unbit.it
http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi


Re: [uWSGI] why? DAMN ! worker 1 (pid: 10705) died :( trying respawn ...

2019-04-10 Thread David Montgomery
ps my works with python 2.7 with gevent loop.  If pypy does not work with
uWSGI please advice since it appears that gunicon is supported and does not
have to setup issues that uWSGI has

Thanks

On Wed, Apr 10, 2019 at 7:47 PM David Montgomery 
wrote:

> Hi,
>
> Why uWSGI?  I dont understand.  I am trying to run bottle with the
> gevent loop with pypy2.
>
> I mean my code simply works if I run with built in server
>
> Here is my entry point in bottle:
>
> if __name__ == *"__main__"*:
>
> # Interactive mode
>
> run(host=*'localhost'*, port=8049,debug=True)  #,reloader=True
>
> else:
>
> # Mod WSGI launch
>
> os.chdir(os.path.dirname(__file__))
>
> application = default_app()
>
> uwsgi:
>
>   pidfile: /var/run/pixel.pid
>
>   loop: gevent
>
>   gevent: 20
>
>   b: 32768
>
>   listen: 1024
>
>   socket: 127.0.0.1:8030
>
>   processes: 4
>
>   master: true
>
>   enable-threads: true
>
>   pypy-lib: /opt/pypy/bin/libpypy-c.so
>
>   logto2: /tmp/pixel.log
>
>   touch-reload: /var/geoaiServerPixel/app.py
>
>   master-fifo: /tmp/uwsgi_api_master_fifo
>
>   pypy-wsgi-file: /var/geoaiServerPixel/app.py
>
>   pypy-pp: [/var/geoaiServerPixel]
>
>
>
> your processes number limit is 64064
>
> your memory page size is 4096 bytes
>
> detected max file descriptor number: 10
>
> lock engine: pthread robust mutexes
>
> thunder lock: disabled (you can enable it with --thunder-lock)
>
> uwsgi socket 0 bound to TCP address 127.0.0.1:8030 fd 3
>
> uWSGI running as root, you can use --uid/--gid/--chroot options
>
> *** WARNING: you are running uWSGI as root !!! (use the --uid flag) ***
>
> Initialized PyPy with Python 2.7.13 (990cef41fe11, Mar 21 2019, 12:14:52)
>
> [PyPy 7.1.0 with GCC 6.2.0 20160901]
>
> PyPy Home: /opt/pypy
>
> added [/var/geoaiServerPixel] to pythonpath
>
> uWSGI running as root, you can use --uid/--gid/--chroot options
>
> *** WARNING: you are running uWSGI as root !!! (use the --uid flag) ***
>
> your server socket listen backlog is limited to 1024 connections
>
> your mercy for graceful operations on workers is 60 seconds
>
> mapped 364600 bytes (356 KB) for 4 cores
>
> *** Operational MODE: preforking ***
>
> *** no app loaded. going in full dynamic mode ***
>
> uWSGI running as root, you can use --uid/--gid/--chroot options
>
> *** WARNING: you are running uWSGI as root !!! (use the --uid flag) ***
>
> *** uWSGI is running in multiple interpreter mode ***
>
> spawned uWSGI master process (pid: 10689)
>
> spawned uWSGI worker 1 (pid: 10705, cores: 1)
>
> unavailable loop engine !!!
>
> spawned uWSGI worker 2 (pid: 10706, cores: 1)
>
> unavailable loop engine !!!
>
> spawned uWSGI worker 3 (pid: 10707, cores: 1)
>
> unavailable loop engine !!!
>
> spawned uWSGI worker 4 (pid: 10710, cores: 1)
>
> DAMN ! worker 1 (pid: 10705) died :( trying respawn ...
>
> unavailable loop engine !!!
>
> Respawned uWSGI worker 1 (new pid: 10711)
>
> DAMN ! worker 2 (pid: 10706) died :( trying respawn ...
>
> unavailable loop engine !!!
>
> Respawned uWSGI worker 2 (new pid: 10712)
>
> DAMN ! worker 3 (pid: 10707) died :( trying respawn ...
>
> unavailable loop engine !!!
>
> Respawned uWSGI worker 3 (new pid: 10715)
>
> DAMN ! worker 4 (pid: 10710) died :( trying respawn ...
>
> unavailable loop engine !!!
>
> Respawned uWSGI worker 4 (new pid: 10716)
>
> DAMN ! worker 1 (pid: 10711) died :( trying respawn ..
>
___
uWSGI mailing list
uWSGI@lists.unbit.it
http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi


[uWSGI] why? DAMN ! worker 1 (pid: 10705) died :( trying respawn ...

2019-04-10 Thread David Montgomery
Hi,

Why uWSGI?  I dont understand.  I am trying to run bottle with the
gevent loop with pypy2.

I mean my code simply works if I run with built in server

Here is my entry point in bottle:

if __name__ == *"__main__"*:

# Interactive mode

run(host=*'localhost'*, port=8049,debug=True)  #,reloader=True

else:

# Mod WSGI launch

os.chdir(os.path.dirname(__file__))

application = default_app()

uwsgi:

  pidfile: /var/run/pixel.pid

  loop: gevent

  gevent: 20

  b: 32768

  listen: 1024

  socket: 127.0.0.1:8030

  processes: 4

  master: true

  enable-threads: true

  pypy-lib: /opt/pypy/bin/libpypy-c.so

  logto2: /tmp/pixel.log

  touch-reload: /var/geoaiServerPixel/app.py

  master-fifo: /tmp/uwsgi_api_master_fifo

  pypy-wsgi-file: /var/geoaiServerPixel/app.py

  pypy-pp: [/var/geoaiServerPixel]



your processes number limit is 64064

your memory page size is 4096 bytes

detected max file descriptor number: 10

lock engine: pthread robust mutexes

thunder lock: disabled (you can enable it with --thunder-lock)

uwsgi socket 0 bound to TCP address 127.0.0.1:8030 fd 3

uWSGI running as root, you can use --uid/--gid/--chroot options

*** WARNING: you are running uWSGI as root !!! (use the --uid flag) ***

Initialized PyPy with Python 2.7.13 (990cef41fe11, Mar 21 2019, 12:14:52)

[PyPy 7.1.0 with GCC 6.2.0 20160901]

PyPy Home: /opt/pypy

added [/var/geoaiServerPixel] to pythonpath

uWSGI running as root, you can use --uid/--gid/--chroot options

*** WARNING: you are running uWSGI as root !!! (use the --uid flag) ***

your server socket listen backlog is limited to 1024 connections

your mercy for graceful operations on workers is 60 seconds

mapped 364600 bytes (356 KB) for 4 cores

*** Operational MODE: preforking ***

*** no app loaded. going in full dynamic mode ***

uWSGI running as root, you can use --uid/--gid/--chroot options

*** WARNING: you are running uWSGI as root !!! (use the --uid flag) ***

*** uWSGI is running in multiple interpreter mode ***

spawned uWSGI master process (pid: 10689)

spawned uWSGI worker 1 (pid: 10705, cores: 1)

unavailable loop engine !!!

spawned uWSGI worker 2 (pid: 10706, cores: 1)

unavailable loop engine !!!

spawned uWSGI worker 3 (pid: 10707, cores: 1)

unavailable loop engine !!!

spawned uWSGI worker 4 (pid: 10710, cores: 1)

DAMN ! worker 1 (pid: 10705) died :( trying respawn ...

unavailable loop engine !!!

Respawned uWSGI worker 1 (new pid: 10711)

DAMN ! worker 2 (pid: 10706) died :( trying respawn ...

unavailable loop engine !!!

Respawned uWSGI worker 2 (new pid: 10712)

DAMN ! worker 3 (pid: 10707) died :( trying respawn ...

unavailable loop engine !!!

Respawned uWSGI worker 3 (new pid: 10715)

DAMN ! worker 4 (pid: 10710) died :( trying respawn ...

unavailable loop engine !!!

Respawned uWSGI worker 4 (new pid: 10716)

DAMN ! worker 1 (pid: 10711) died :( trying respawn ..
___
uWSGI mailing list
uWSGI@lists.unbit.it
http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi