Quantcast
Channel: Active questions tagged redis+ruby-on-rails - Stack Overflow
Viewing all articles
Browse latest Browse all 873

Not able to configure redis and resque in rails 4.1.6 app

$
0
0

I started with installing redis correctly and I guess that part is done pretty much correctly. I used this https://www.digitalocean.com/community/tutorials/how-to-install-and-secure-redis-on-ubuntu-18-04 for redis and it works as fine as mentioned in the article (redis-cli works pretty fine).I have resque gem in my app but when I try to fire QUEUE=* rake resque:work, it keeps on printing the below texts in loop for a long long time and then shuts down automatically.

/home/sayan/Documents/primary_sales/lib/tasks/resque.rake:6:in `<top (required)>'/home/sayan/.rvm/gems/ruby-2.3.8@batman/gems/activesupport-4.1.6/lib/active_support/dependencies.rb:241:in `load'/home/sayan/.rvm/gems/ruby-2.3.8@batman/gems/activesupport-4.1.6/lib/active_support/dependencies.rb:241:in `block in load'/home/sayan/.rvm/gems/ruby-2.3.8@batman/gems/activesupport-4.1.6/lib/active_support/dependencies.rb:232:in `load_dependency'/home/sayan/.rvm/gems/ruby-2.3.8@batman/gems/activesupport-4.1.6/lib/active_support/dependencies.rb:241:in `load'/home/sayan/.rvm/gems/ruby-2.3.8@batman/gems/railties-4.1.6/lib/rails/engine.rb:654:in `block in run_tasks_blocks'/home/sayan/.rvm/gems/ruby-2.3.8@batman/gems/railties-4.1.6/lib/rails/engine.rb:654:in `each'/home/sayan/.rvm/gems/ruby-2.3.8@batman/gems/railties-4.1.6/lib/rails/engine.rb:654:in `run_tasks_blocks'/home/sayan/.rvm/gems/ruby-2.3.8@batman/gems/railties-4.1.6/lib/rails/application.rb:384:in `run_tasks_blocks'/home/sayan/.rvm/gems/ruby-2.3.8@batman/gems/railties-4.1.6/lib/rails/engine.rb:449:in `load_tasks'

I have done some changes in the config files but I dont think they are doing much. Please suggest the recommended config changes for the rails app as well.


Viewing all articles
Browse latest Browse all 873

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>