由于发生了"INFO spawnerr:无法为'app_name'派遣调度程序:EACCES"的错误,无法通过nohup启动服务 [英] Unable to start service with nohup due to 'INFO spawnerr: unknown error making dispatchers for 'app_name': EACCES'
本文介绍了由于发生了"INFO spawnerr:无法为'app_name'派遣调度程序:EACCES"的错误,无法通过nohup启动服务的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!
问题描述
我正在尝试与主管一起启动服务,但出现一条错误消息
I'm trying to start a service with supervisor, but I get an error saying
INFO spawnerr:未知的"app_name"调度程序错误:EACCES
INFO spawnerr: unknown error making dispatchers for 'app_name': EACCES
这是我的supervisord.conf文件:
Here's my supervisord.conf file:
[supervisord]
logfile=/tmp/supervisord.log
logfile_maxbytes=50MB ; change these depending on how many logs
logfile_backups=10 ; you want to keep
loglevel=info
pidfile=/tmp/supervisord.pid
nodaemon=true
minfds=1024
minprocs=200
[rpcinterface:supervisor]
supervisor.rpcinterface_factory = supervisor.rpcinterface:make_main_rpcinterface
[supervisorctl]
serverurl=unix:///tmp/supervisor.sock socket
[program:myscript]
command= python -u /home/ubuntu/appfolder/app_name.py
autostart=true
autorestart=unexpected
redirect_stderr=true
stdout_logfile=/var/log/app_name.log
推荐答案
我遇到了同样的问题-芹菜子程序日志被写入应用文件夹下的logs子文件夹中,结果证明我将所有者设置为>> whoami
)
I had the same issue - the celery sub program logs were being written in the logs subfolder under my app folder and turns out I had set the owner to www-user
while I was debugging an issue with Nginx. I changed the owner of the app folder back to ubuntu (>> whoami
)
sudo chown -R ubuntu:ubuntu /var/www/myapp/
使其正常工作.
这篇关于由于发生了"INFO spawnerr:无法为'app_name'派遣调度程序:EACCES"的错误,无法通过nohup启动服务的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!
查看全文