Redis will not time out. Try installing the SystemTimer gem.

WARNING: Could not find a good alternative for performing time outs — connecting to Redis will not time out. Try installing the SystemTimer gem.
rake aborted!
undefined method `get’ for nil:NilClass

WARNING: Could not find a good alternative for performing time outs — connecting to Redis will not time out. Try installing the SystemTimer gem.rake aborted!undefined method `get’ for nil:NilClass

sudo gem install system_timer

If that doesn’t work and you follow the resque configuration guide from http://github.com/defunkt/resque which uses config/initializers/resque.rb make sure you have upgraded all your gems (make sure you update rubygems itself) and if you are running Ubuntu/Debian I suggest you install redis from source and configure monit to start and monitor it.

Posted on July 27, 2010 at 3:03 pm by Jordan Carter · Permalink
In: Ruby on Rails, Server Config · Tagged with: , ,

2 Responses

  1. Written by Petr Kaleta
    on July 27, 2010 at 8:23 pm
    Permalink

    I got exactly the same problem, after running each rake task it says “WARNING: Could not find a good alternative for performing time outs — connecting to Redis will not time out. Try installing the SystemTimer gem.
    ” but no error after that.

    system_timer is installed on my machine. All gems are updated.

    Any suggestion?

  2. Written by Jordan Carter
    on August 4, 2010 at 10:33 am
    Permalink

    I found that I had the wrong version of the gems.
    Once that was fixed I noticed that I had followed the instructions on github and setup a redis config/init script which held environment specific configurations. I then noticed that I didn’t have an environment config for development, which is why it was throwing the error. Would have been nice for it to throw a different error tho.

Leave a Reply