{"id":24919,"date":"2021-11-12T09:59:00","date_gmt":"2021-11-12T09:59:00","guid":{"rendered":"https:\/\/www.devopsschool.com\/blog\/?p=24919"},"modified":"2021-11-20T06:07:43","modified_gmt":"2021-11-20T06:07:43","slug":"supervisor-fatal-backoff-exited-too-quickly-process-log-may-have-details","status":"publish","type":"post","link":"https:\/\/www.devopsschool.com\/blog\/supervisor-fatal-backoff-exited-too-quickly-process-log-may-have-details\/","title":{"rendered":"[SOLVED] Laravel : Supervisor FATAL\/BACKOFF Exited too quickly (process log may have details)"},"content":{"rendered":"\n

Problem<\/span><\/h1>\n\n\n\n

I’m trying to use Laravel queues with a supervisor but the service is not working properly.<\/p>\n\n\n

<strong>My config \/etc\/supervisord.d\/laravel-worker.conf is:<\/strong>\n[program:laravel-worker]\nprocess_name=%(program_name)s_%(process_num)02<\/span>d\ncommand=\/usr\/bin\/php \/var<\/span>\/www\/my-project\/artisan queue:work --sleep=3<\/span> --tries=3<\/span>\nautostart=true<\/span>\nautorestart=true<\/span>\nuser=root:root\nnumprocs=8<\/span>\nredirect_stderr=true<\/span>\nstdout_logfile=\/var<\/span>\/www\/my-project\/worker.log<\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
<\/p>\n\n\n
<strong<\/span>><\/span>When I try to restart all programs:<\/strong<\/span>><\/span>\n$ sudo supervisorctl restart all\n$ laravel-worker:laravel-worker_00: ERROR (abnormal termination)\n$ laravel-worker:laravel-worker_01: ERROR (abnormal termination)<\/code><\/span>Code language:<\/span> HTML, XML<\/span> (<\/span>xml<\/span>)<\/span><\/small><\/pre>\n\n\n
<\/p>\n\n\n\n
When I try to check status:<\/strong>
$ sudo supervisorctl status
$ laravel-worker:laravel-worker_00:    BACKOFF   Exited too quickly (process log may have details)
$ laravel-worker:laravel-worker_00:    BACKOFF   Exited too quickly (process log may have details)<\/p>\n\n\n\n
<\/p>\n\n\n\n
Solution<\/span><\/h1>\n\n\n\n
In my case, the supervisor was exiting very fast because it was finishing before the startsecs and since startsecs wasn’t defined, it uses the default which is 1.<\/p>\n\n\n\n
Setting startsecs=0<\/strong><\/span><\/code> fixed my issue.<\/p>\n\n\n\n
<\/p>\n\n\n
<strong<\/span>><\/span>you need to add startsecs = 0 to your laravel-worker config like so:<\/strong<\/span>><\/span>\n[program:laravel-worker]     \nprocess_name=%(program_name)s_%(process_num)02d\ncommand=\/usr\/bin\/php \/var\/www\/my-project\/artisan queue:work --sleep=3 --tries=3\n.....\nstartsecs = 0<\/code><\/span>Code language:<\/span> HTML, XML<\/span> (<\/span>xml<\/span>)<\/span><\/small><\/pre>\n\n\n
<\/p>\n\n\n\n
startsecs<\/code> <\/strong><\/span>is default to 1s, if the program does not stay up for 1s it will see the startup as a failure. Set it to 0 so the program needn\u2019t stay running for any particular amount of time. You can check this GitHub issue for more info: https:\/\/github.com\/Supervisor\/supervisor\/issues\/212<\/a><\/p>\n\n\n\n
It would be better if you run the queue worker in daemon mode, use the –daemon flag: command=\/usr\/bin\/php \/var\/www\/my-project\/artisan queue:work database --daemon --sleep=3 --tries=3<\/code><\/p>\n\n\n\n
After you change the config file, you may need to run\u00a0supervisorctl reload<\/strong><\/span><\/code>\u00a0to allow the changes to take effect.<\/p>\n\n\n