Open hackel opened 7 years ago
Thank you. I'll try to fix it. Can you show me you supervisord config file or make sample with same issue?
Sure, here it is. FYI, just changing it to use {stop,start}ProcessGroup worked just fine.
[program:program-queue-worker]
process_name=%(program_name)s_%(process_num)02d
directory=/home/program
command=php artisan queue:work --delay=10 --sleep=10 --tries=1
autostart=true
autorestart=true
user=program
umask=0002
numprocs=4
redirect_stderr=true
stdout_logfile=/home/program/storage/logs/queue-worker.log
stdout_logfile_maxbytes=2MB
stdout_logfile_backups=2
[eventlistener:test_listener]
command = python -m touch_reload --socket unix:///var/run/supervisor.sock --file app --program program-queue-worker
events = TICK_5
directory = /home/program
#stderr_logfile = /tmp/test_listener.log
stderr_logfile = NONE
When firing up touch_reload, it is monitoring my directory fine, but whenever I change a file, it logs this error:
Obviously I have ensured that my "program-name" is correct. It is specified as:
[program:program-name]
, and this works fine to start/stop the supervisor process. I'm running supervisor 3.2.0, in case something changed with their API.Edit: I think I figured it out. I am running multiple processes and using
process_name=%(program_name)s_%(process_num)02d
, and this is what thesupervisor.stopProcess
method must be expecting. In my case, it would need to usestopProcessGroup
, apparently. Perhaps it would make sense to add a--program-group
option to account for this scenario.