Upstart產生多個uWSGI Emperor進程

Question

當uWSGI通過Upstart啓動時，我有兩個獨立的Emperor實例（如手動運行，見下文）。

新貴創建多個皇帝過程：

# ps ax | grep -i emper                              
    888 ?  S  0:53 uwsgi /etc/uwsgi/emperor.ini 
    896 ?  S  0:33 uwsgi /etc/uwsgi/emperor.ini 
    904 ?  S  0:52 uwsgi /etc/uwsgi/emperor.ini 
    905 ?  S  0:34 uwsgi /etc/uwsgi/emperor.ini 
    ... 

當我殺死所有的皇帝和手動我有工人站點的兩個皇帝的進程中運行它：

# pstree -up | less 
    ... 
    -uwsgi(16347)---uwsgi(16348)-+-uwsgi(16349,web)-+-uwsgi(16358) 
    |        |     |-uwsgi(16360) 
    |        |     |-uwsgi(17058) 
    |        |     |-uwsgi(17261) 
    |        |     |-uwsgi(17410) 
    |        |     |-uwsgi(17488) 
    |        |     |-uwsgi(17750) 
    |        |     `-uwsgi(17770) 
    |        `-uwsgi(16350,web)-+-uwsgi(16361) 
    |            |-uwsgi(16362) 
    |            |-uwsgi(16363) 
    |            |-uwsgi(16364) 
    |            |-uwsgi(16365) 
    |            |-uwsgi(16366) 
    |            |-uwsgi(16367) 
    |            `-uwsgi(16368) 

我對皇帝暴發戶配置：

# Emperor uWSGI script 

description "uWSGI Emperor" 
start on runlevel [2345] 
stop on runlevel [06] 

respawn 

exec uwsgi /etc/uwsgi/emperor.ini 

我的uWSGI Emperor配置：

[uwsgi] 
    emperor-tyrant = true 
    emperor = %dvassals 
    emperor-pidfile = %demperor.pid 
    emperor-stats = %demperor.stat.sock 
    vassals-include = %dvassals-default.ini 
    touch-logrotate = %p 
    touch-reload = %p 
    touch-reload = %dvassals-default.ini 
    log-date = true 
    log-truncate = true 
    daemonize = /var/log/uwsgi/emperor.log 

可能是我在Upstart配置錯了嗎？ 日誌並沒有幫助我。

Answer 1

需要更改daemonize至logto。

更多關於uWSGI回購信息的問題：https://github.com/unbit/uwsgi/issues/1510