[uWSGI] vassal not starting up on socket?

Harry Percival harry at pythonanywhere.com
Tue Oct 1 17:24:41 CEST 2013


Yep, you nailed it.  I had just figured that out for myself.  Sorry to 
bother you everyone.



-- 
Harry Percival
Developer
harry at pythonanywhere.com

PythonAnywhere - a fully browser-based Python development and hosting 
environment
<http://www.pythonanywhere.com/>

PythonAnywhere LLP
17a Clerkenwell Road, London EC1M 5RD, UK
VAT No.: GB 893 5643 79
Registered in England and Wales as company number OC378414.
Registered address: 28 Ely Place, 3rd Floor, London EC1N 6TD, UK
-----Original Message----- 
From: Roberto De Ioris
Sent: Tuesday, October 01, 2013 4:22 PM
To: uWSGI developers and users list
Subject: Re: [uWSGI] vassal not starting up on socket?


> Strange. One of our vassals seems to be starting on port 5000 instead of
> listening on its socket.
>
> Vassal log:
>
>   2013-10-01 15:10:13 +0000 someuser.superhostingsite.com - uwsgi socket 0
> bound to UNIX address /var/sockets/someuser.superhostingsite.com/socket
> fd 4
>   2013-10-01 15:10:13 +0000 someuser.superhostingsite.com - Python
> version: 2.7.4 (default, Apr 19 2013, 18:30:41)  [GCC 4.7.3]
>   2013-10-01 15:10:13 +0000 someuser.superhostingsite.com - *** Python
> threads support is disabled. You can enable it with --enable-threads ***
>   2013-10-01 15:10:13 +0000 someuser.superhostingsite.com - Python main
> interpreter initialized at 0x1a341b0
>   2013-10-01 15:10:13 +0000 someuser.superhostingsite.com - your server
> socket listen backlog is limited to 100 connections
>   2013-10-01 15:10:13 +0000 someuser.superhostingsite.com - your mercy for
> graceful operations on workers is 60 seconds
>   2013-10-01 15:10:13 +0000 someuser.superhostingsite.com - setting
> request body buffering size to 65536 bytes
>   2013-10-01 15:10:13 +0000 someuser.superhostingsite.com - mapped 333872
> bytes (326 KB) for 1 cores
>   2013-10-01 15:10:13 +0000 someuser.superhostingsite.com - ***
> Operational MODE: single process ***
>   * Running on http://127.0.0.1:5000/
>   * Restarting with reloader
>   unable to load configuration from uwsgi
>   2013-10-01 15:10:14 +0000 someuser.superhostingsite.com - chdir(): No
> such file or directory [core/uwsgi.c line 1318]
>   2013-10-01 15:10:14 +0000 someuser.superhostingsite.com - VACUUM: unix
> socket /var/sockets/someuser.superhostingsite.com/socket removed.
>
> What’s all that “running on 127.0.0.1:5000” all about then? Vassal config
> is the same as everyone else that runs happily on their socket...
>
> Emperor log just shows
>
>   [uWSGI] getting INI configuration from someuser.superhostingsite.com.ini
>   2013-10-01 15:16:44 +0000 someuser.superhostingsite.com - [uwsgi-static]
> added check for /var/www/static
>   [...]
>   2013-10-01 15:16:45 +0000 EMPEROR - [emperor] removed uwsgi instance
> someuser.superhostingsite.com.ini
>
> Hmmm?
>
>
>

Someone is calling app.run() in its flask app, so it is starting the flask
embedded server taking control over uWSGI

-- 
Roberto De Ioris
http://unbit.it
_______________________________________________
uWSGI mailing list
uWSGI at lists.unbit.it
http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi 



More information about the uWSGI mailing list