You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am unable to start resque:scheduler process in the background by using the BACKGROUND=yes flag. The command which i am using is: BACKGROUND=yes /usr/bin/bundle exec /usr/bin/rake environment resque:scheduler RAILS_ENV=development
resque:scheduler process starts successfully after running this but the rake process doesn't exit as it should after providing the BACKGROUND=yes flag. After the schedules get loaded, instead of running the scheduler in the background, jobs start getting enqueued in the foreground:
Strange thing to note here is that this issue doesn't appear when using rails3 application. The rake process exits and resque:scheduler starts running in the background as soon as the schedules get loaded.
These are the OS and package versions i'm using:
OS - Amazon Linux 2
resque:scheduler - 4.2.0
ruby - 2.1.6
rails - 4.2.11
The text was updated successfully, but these errors were encountered:
I am unable to start resque:scheduler process in the background by using the
BACKGROUND=yes
flag. The command which i am using is:BACKGROUND=yes /usr/bin/bundle exec /usr/bin/rake environment resque:scheduler RAILS_ENV=development
resque:scheduler process starts successfully after running this but the rake process doesn't exit as it should after providing the BACKGROUND=yes flag. After the schedules get loaded, instead of running the scheduler in the background, jobs start getting enqueued in the foreground:
Checked this on a different terminal:
Strange thing to note here is that this issue doesn't appear when using rails3 application. The rake process exits and resque:scheduler starts running in the background as soon as the schedules get loaded.
These are the OS and package versions i'm using:
The text was updated successfully, but these errors were encountered: