Ad

How Can I Learn More About Why My Laravel Queued Job Failed?

- 1 answer

The Situation

I'm using Laravel Queues to process large numbers of media files, an individual job is expected to take minutes (lets just say up to an hour).

I am using Supervisor to run my queue, and I am running 20 processes at a time. My supervisor config file looks like this:

[program:duplitron-worker]
process_name=%(program_name)s_%(process_num)02d
command=php /var/www/duplitron/artisan queue:listen database --timeout=0 --memory=500 --tries=1
autostart=true
autorestart=true
user=duplitron
numprocs=20
redirect_stderr=true
stdout_logfile=/var/www/duplitron/storage/logs/duplitron-worker.log

In my duplitron-worker.log I noticed Failed: Illuminate\Queue\[email protected] occurs occasionally and I would like to better understand what exactly is failing. Nothing appears in my laravel.log file (which is where exceptions would normally appear).

The Question

Is there a handy way for me to learn more about what is causing my job to fail?

Ad

Answer

In the newer Laravel versions there's an exception column in the failed_jobs table that has all the info you need. Thanks cdarken and Toskan for pointing this out!

==== OLD METHOD BELOW

Here's what I always do, but first - make sure you have a failed-jobs table! It's well documented, look it up :)

  1. Run the php artisan queue:failed command to list all the failed jobs, and pick the one you're after. Write the ID down.

  2. Then, make sure to stop your queue with supervisorctl stop all duplitron-worker:

  3. Lastly, make sure your .env setting for APP_DEBUG = true.

  4. Then run php artisan queue:retry {step_job_1_id}

  5. Now manually runphp artisan queue:listen --timeout=XXX

If the error is structural (and most are), you should get the failure with debug stack in your log file.

Good luck with debugging :-)

Ad
source: stackoverflow.com
Ad