简体   繁体   中英

configure supervisor on amazon ec2 giving spawn error unknown error making dispatchers for 'app_name': EACCES

I've seen this post Unable to start service with nohup due to 'INFO spawnerr: unknown error making dispatchers for 'app_name': EACCES' and tried the answer but it doesn't work

I'm using the Amazon AMI, and since Amazon doesn't have apt-get, I had to use easy_install to install supervisor. here is my /etc/supervisord.conf

[program:awesome]

command     = /srv/awesome/www/app.py
directory   = /srv/awesome/www
user        = ec2-user
startsecs   = 3

redirect_stderr         = true
stdout_logfile_maxbytes = 50MB
stdout_logfile_backups  = 10
stdout_logfile          = /srv/awesome/log/app.log

my app files are placed under /srv/awesome/www/ and the owner set to ec2-user which is the same user when I ran whoami. I first ran

supervisord -c /etc/supervisord.conf

which gave me

Another program is already listening on a port that one of our HTTP servers is configured to use. Shut this program down first before starting supervisord.

I entered the command

sudo unlink /tmp/supervisor.sock

which resolved it, then I did

supervisorctl start awesome

which spawn the error, I've tried reloading, stop and start but none works

我切换到 ubuntu 而不是 amazon AMI,一切都解决了

The technical post webpages of this site follow the CC BY-SA 4.0 protocol. If you need to reprint, please indicate the site URL or the original address.Any question please contact:yoyou2525@163.com.

 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM