我用uwsgi,supervisor和Nginx部署django项目.
但是我已经在/etc/supervisord.conf中像上面一样添加了程序.
[program:JZAssist]
command=-E uwsgi --ini /home/work/xxxx/uwsgi.ini
directory=/home/work/xxxx
startsecs=0
stopwaitsecs=0
autostart=true
autorestart=true
我的uwsgi.ini内容是：
[uwsgi]
socket = :8000
chdir = /home/work/xxxx
module = xxxx.wsgi
master = true
processes = 4
vacuum = true
xxxx是我的项目名称.
我在cmd中运行supervisorctl -c /etc/supervisord.conf重新启动.
它显示
xxxx: ERROR (no such file)
/tmp/supervisord.log部分内容：
2017-02-24 23:31:41,433 INFO gave up: JZAssist entered FATAL state,too many start retries too quickly
2017-02-24 23:52:29,940 WARN Failed to clean up '/tmp/JZAssist-stderr---supervisor-goPZyS.log'
2017-02-24 23:52:29,940 WARN Failed to clean up '/tmp/JZAssist-stdout---supervisor-WtfJcp.log'
2017-02-24 23:52:57,535 WARN Failed to clean up '/tmp/JZAssist-stderr---supervisor-goPZyS.log'
2017-02-24 23:52:57,535 WARN Failed to clean up '/tmp/JZAssist-stdout---supervisor-WtfJcp.log'
2017-02-24 23:52:57,541 INFO RPC interface 'supervisor' initialized
2017-02-24 23:52:57,541 CRIT Server 'unix_http_server' running without any HTTP authentication checking
2017-02-24 23:52:57,542 INFO daemonizing the supervisord process
2017-02-24 23:52:57,543 CRIT could not write pidfile /tmp/supervisord.pid
2017-02-24 23:52:58,544 INFO spawnerr: can't find command '-E'
2017-02-24 23:52:59,546 INFO spawnerr: can't find command '-E'
2017-02-25 00:46:59,234 WARN Failed to clean up '/tmp/JZAssist-stderr---supervisor-goPZyS.log'
2017-02-25 00:46:59,234 WARN Failed to clean up '/tmp/JZAssist-stdout---supervisor-WtfJcp.log'
最佳答案
在您的command =行上,您已指定该程序以-E运行,而主管找不到该程序来执行.
原文链接：https://www.f2er.com/nginx/532477.html为作业创建文件时,命令行应作为shell命令可执行,并且不应依赖内部命令来执行给定的shell.例如,我遇到了一个以以下内容开头的问题：
源/ path / to / python / virtual / environment / bin / activate&& …
但源代码是内置的bash.我需要将其更改为：
bash -c’source / path / to / python / virtual / environment / bin / activate&& …
这样,主管可以找到并运行的可执行文件是bash.
就您而言,看来uwsgi应该是command =之后的第一件事.
您提到您在运行sudo时使用-E标志来保留环境变量,但是主管不需要sudo
