vertolet's avatar

Lumen supervisor

Hi,

I'm facing a problem with supervisor. Sometimes it starts to clone processes in queue till it starts crashing. Is it possible to find out why?

0 likes
2 replies
salmon's avatar

I would have a look at the supervisor logs to see what is going on.

tail -f /var/log/supervisor/worker.log

You should be able to i.e. set the amount of processes in your configuration

i.e.


[program:laravel-worker]
process_name=%(program_name)s_%(process_num)02d
command=php /var/www/web-app/artisan queue:work --daemon --sleep=3 --tries=1
autostart=true
autorestart=true
user=www-data
numprocs=4
redirect_stderr=true
stdout_logfile=/var/log/supervisor/worker.log

Make sure your supervisor deamon is started by using the following command supervisord docs

supervisord

To view the Supervisors status, use this command

supervisorctl status all

If you want to restart/refresh supervisor just run.

supervisorctl stop all
supervisorctl start all
vertolet's avatar

Hi, thank you for your reply. Here is information that you've asked :

  1. number of prcesses is set to 1, so there is not connection with this
  2. worker log is showing nothing - because in period when supervisor started to "loosing control" of child process - there were no jobs for processing.

according starting / ending supervisord - i've done it according to docs.

additionaly : usualy I see that supervisor "hosts" processes, but - when supervisor "loosing control" all process are out of supervisor control and just using supervisorctl stop all is not helping

Please or to participate in this conversation.