Your file needs to be executable. So either: You should chmod +x it to set the executable bit. Put a shebang at the start of the file. Not having this is what caused the ENOEXEC. or Modify your config file to something like command=sh /var/application/start_tester.
You should run supervisorctl with -c as well. From the documentation (my emphasis): The Supervisor configuration file is conventionally named supervisord.conf. It is used by both supervisord and supervisorctl. If either application is started without the -c option (the option which is used to tell the application the configuration filename explicitly), the application will look … Read more
first of all, type this on your console or terminal ps -ef | grep supervisord You will get some pid of supervisord just like these root 2641 12938 0 04:52 pts/1 00:00:00 grep –color=auto supervisord root 29646 1 0 04:45 ? 00:00:00 /usr/bin/python /usr/local/bin/supervisord if you get output like that, your pid is the second … Read more
You have to start supervisord before you can use supervisorctl. In my case: sudo supervisord -c /etc/supervisor/supervisord.conf sudo supervisorctl -c /etc/supervisor/supervisord.conf
supervisord supports process groups. You can group processes into named groups and manage them collectively. [unix_http_server] file=%(here)s/supervisor.sock [supervisord] logfile=supervisord.log pidfile=supervisord.pid [program:cat1] command=cat [program:cat2] command=cat [program:cat3] command=cat [group:foo] programs=cat1,cat3 [supervisorctl] serverurl=unix://%(here)s/supervisor.sock [rpcinterface:supervisor] supervisor.rpcinterface_factory = supervisor.rpcinterface:make_main_rpcinterface supervisorctl command can be called with a group name: supervisorctl restart foo: as well as with multiple process names: supervisorctl restart … Read more