-
-
Notifications
You must be signed in to change notification settings - Fork 289
ERROR: No worker found for queue
Pablo Cantero edited this page Sep 1, 2018
·
1 revision
If you use standard Shoryuken workers by include Shoryuken::Worker
, and do not use ActiveJob, a commit in version 3.2.3 stopped eager loading the entire application. In this case, you must use the -r
option to require your jobs specifically while starting Shoryuken.
Example:
bundle exec shoryuken \
-R \
-P /var/app/containerfiles/pids/shoryuken.pid \
-C /var/app/current/config/shoryuken.yml \
-L /var/app/containerfiles/logs/shoryuken.log \
-r /var/app/current/app/jobs \
-d