uWSGI Emperor配置

时间:2015-06-03 22:22:00

标签: python flask uwsgi

我一直在努力使用uWSGI将烧瓶应用程序部署到我的服务器 皇帝模式整天都不知道为什么它不起作用。我在这里阅读了所有其他的uWSGI Emperor模式问题。问#uwsgi&没有回复的邮件列表。

我的设置是nginx(1.4.6-1ubuntu3.2),uWSGI == 2.0.10通过pip安装 进入virtualenv,Flask == 0.10.1和Python 3.4.0。监督是 负责启动皇帝进程。

当我手动绑定到TCP端口时,烧瓶应用程序本身正常工作,当我手动运行uwsgi时:

uwsgi -s /tmp/oauthsvc.sock -w wsgi --stats /tmp/oauthsvc-stats.sock

我注意到即使我认为我配置了附庸使用 unix socket,它在启动时报告它正在监听http://127.0.0.1:5000/

我用strace验证了nginx正在打开套接字和权限 该套接字是777:

srwxrwxrwx 1 oauthsvc oauthsvc 0 Jun  3 18:34 /tmp/oauthsvc.sock
srwxrwxrwx 1 oauthsvc oauthsvc 0 Jun  3 18:08 /tmp/oauthsvc-stats.sock

但这种联系最终只是超时。

我的配置&一些日志输出如下。

nginx配置非常简单:

server {                                                                    
    listen 80;                                                              
    server_name default;                                                    

    location = /robots.txt  { access_log off; log_not_found off; }          
    location = /favicon.ico { access_log off; log_not_found off; }          

    location / {                                                            
        include uwsgi_params;                                               
        uwsgi_pass unix:/tmp/oauthsvc.sock;                                 
    }                                                                       
} 

supervisor使用以下命令启动emporer进程:

[program:oauthsvc-emperor]                                                      
command=/services/oauthsvc/services/oauthsvc/bin/uwsgi --emperor /services/oauthsvc/etc/uwsgi/vassals --die-on-term --uid 1005 --gid 1005 --logto /services/oauthsvc/var/log/uwsgi/emperor.log
user=oauthsvc                                                                   
autostart=true                                                                  
autorestart=true                                                                
redirect_stderr=true 

vassal的ini文件如下:

[uwsgi]                                                                         
# do not turn on master mode when spawned by emperor                            
# http://stackoverflow.com/questions/15055002/uwsgi-master-with-emperor-spawns-two-emperors
#master = true                                                                  
protocol = uwsgi                                                                
socket = /tmp/oauthsvc.sock                                                     
stats = /tmp/oauthsvc-stats.sock                                                
daemonize = /services/oauthsvc/var/log/uwsgi/oauthsvc.log                       
chdir = /services/oauthsvc/services/oauthsvc/oauthsvc-server                    
wsgi-file = wsgi.py                                                             
callable = app                                                                  
chmod-socket = 777                                                              
uid = 1005                                                                      
gid = 1005                                                                      
virtualenv = /services/oauthsvc/services/oauthsvc                               
# PYTHONHOME                                                                    
home = /services/oauthsvc/services/oauthsvc                                     
#env =                                                                           
processes = 4
vacuum = true                                                                   
# If you start uWSGI without threads, the Python GIL will not be enabled, so    
# threads generated by your application will never run unless you include:      
enable-threads = true
harakiri = 30

最后,wsgi.py:

#!/usr/bin/env python3                                                          

from oauthsvc.flask.server import parse_args, configured_app                    

args = parse_args()                                                             
app = configured_app(args.config, debug=args.debug)                             
app.run()  

皇帝记录:

*** Starting uWSGI 2.0.10 (64bit) on [Wed Jun  3 18:34:25 2015] ***
compiled with version: 4.8.2 on 03 June 2015 18:32:12
os: Linux-3.13.0-48-generic #80-Ubuntu SMP Thu Mar 12 11:16:15 UTC 2015
nodename: ip-10-0-1-224
machine: x86_64
clock source: unix
pcre jit disabled
detected number of CPU cores: 1
current working directory: /
detected binary path: /services/oauthsvc/src/bs-oauth-svc.2015-06-03.183113/bin/uwsgi
*** WARNING: you are running uWSGI without its master process manager ***
your processes number limit is 30038
your memory page size is 4096 bytes
detected max file descriptor number: 1024
*** starting uWSGI Emperor ***
*** has_emperor mode detected (fd: 6) ***
[uWSGI] getting INI configuration from oauthsvc.ini

附庸日志:

*** Starting uWSGI 2.0.10 (64bit) on [Wed Jun  3 18:34:25 2015] ***
compiled with version: 4.8.2 on 03 June 2015 18:32:12
os: Linux-3.13.0-48-generic #80-Ubuntu SMP Thu Mar 12 11:16:15 UTC 2015
nodename: ip-10-0-1-224
machine: x86_64
clock source: unix
pcre jit disabled
detected number of CPU cores: 1
current working directory: /services/oauthsvc/etc/uwsgi/vassals
detected binary path: /services/oauthsvc/src/bs-oauth-svc.2015-06-03.183113/bin/uwsgi
chdir() to /services/oauthsvc/services/oauthsvc/oauthsvc-server
your processes number limit is 30038
your memory page size is 4096 bytes
 *** WARNING: you have enabled harakiri without post buffering. Slow upload could be rejected on post-unbuffered webservers ***
detected max file descriptor number: 1024
lock engine: pthread robust mutexes
thunder lock: disabled (you can enable it with --thunder-lock)
uwsgi socket 0 bound to UNIX address /tmp/oauthsvc.sock fd 3
Python version: 3.4.0 (default, Apr 11 2014, 13:08:40)  [GCC 4.8.2]
Set PythonHome to /services/oauthsvc/services/oauthsvc
Python main interpreter initialized at 0x135d4d0
python threads support enabled
your server socket listen backlog is limited to 100 connections
your mercy for graceful operations on workers is 60 seconds
mapped 363840 bytes (355 KB) for 4 cores
*** Operational MODE: preforking ***
 * Running on http://127.0.0.1:5000/ (Press CTRL+C to quit)

1 个答案:

答案 0 :(得分:0)

Brian在uWSGI邮件列表上为我解决了这个问题。答案是:不要在wsgi.py文件中调用app.run()!我知道这会让人感到尴尬。