fabricecw's avatar

Jobs won't dispatch via Queue Worker

Hey

I have some problems with the Forge queue daemon. The dispatched jobs aren't fired to the queue suddenly. I can't discover what's the reason for it, maybe fresh deployed code from GitHub or just after a certain time.

Forge Worker configuration: Connection: beanstalkd Queue: default Timeout: 0 Sleep: 10 Tries: Any Environment: production (Run worker as daemon)

The Queue Worker Status is always "RUNNING".

If I execute php artisan queue:listen and dispatch a job, it won't listed. I flushed the queue, restarted the queue (via terminal and the Forge GUI) and checked for failed jobs (no entries).

Then, I tried to clear the config cache and application cache. But still the same problem.

The only way to bring the worker up again is to reboot the whole server... Anyone an idea what that could be?

Thanks and regards,

0 likes
2 replies
afrayedknot's avatar

Are you sure your queue tube is default? What is in your configuration?

And is your application pushing to the default tube, or is it pushing to something else like - i.e. Queue()->on('email');?

adnan.shabbir's avatar

Faced same problem and my connection to queue was database.

  • Use job callback for failed queues
  • Check the logs for errors
  • When you changed something in your code you need to Flush the queue to have its impact
  • Try to start the queue as a demon queue:work

Please or to participate in this conversation.