(Timeout::Error) "execution expired"

[rubydev]

Hello, I have problem with redis connection. Often return this error:

A Timeout::Error occurred in #:

  execution expired
  .bundle/ruby/1.9/gems/redis-2.2.2/lib/redis/connection/ruby.rb:26:in `initialize'

-------------------------------
Backtrace:
-------------------------------

  .bundle/ruby/1.9/gems/redis-2.2.2/lib/redis/connection/ruby.rb:26:in `initialize'
  .bundle/ruby/1.9/gems/redis-2.2.2/lib/redis/connection/ruby.rb:26:in `new'
  .bundle/ruby/1.9/gems/redis-2.2.2/lib/redis/connection/ruby.rb:26:in `block in connect'
  .bundle/ruby/1.9/gems/redis-2.2.2/lib/redis/connection/ruby.rb:128:in `with_timeout'
  .bundle/ruby/1.9/gems/redis-2.2.2/lib/redis/connection/ruby.rb:25:in `connect'
  .bundle/ruby/1.9/gems/redis-2.2.2/lib/redis/client.rb:227:in `establish_connection'
  .bundle/ruby/1.9/gems/redis-2.2.2/lib/redis/client.rb:23:in `connect'
  .bundle/ruby/1.9/gems/redis-2.2.2/lib/redis/client.rb:247:in `ensure_connected'
  .bundle/ruby/1.9/gems/redis-2.2.2/lib/redis/client.rb:137:in `block in process'
  .bundle/ruby/1.9/gems/redis-2.2.2/lib/redis/client.rb:206:in `logging'
  .bundle/ruby/1.9/gems/redis-2.2.2/lib/redis/client.rb:136:in `process'
  .bundle/ruby/1.9/gems/redis-2.2.2/lib/redis/client.rb:46:in `call'
  .bundle/ruby/1.9/gems/redis-2.2.2/lib/redis.rb:681:in `block in del'
  /usr/local/lib/ruby/1.9/monitor.rb:211:in `mon_synchronize'
  .bundle/ruby/1.9/gems/redis-2.2.2/lib/redis.rb:680:in `del'
  app/models/result.rb:77:in `check'
  app/jobs/shopcheck.rb:8:in `perform'
  .bundle/ruby/1.9/gems/resque-1.19.0/lib/resque/job.rb:127:in `perform'
  .bundle/ruby/1.9/gems/resque-1.19.0/lib/resque/worker.rb:163:in `perform'
  .bundle/ruby/1.9/gems/resque-1.19.0/lib/resque/worker.rb:130:in `block in work'
  .bundle/ruby/1.9/gems/resque-1.19.0/lib/resque/worker.rb:116:in `loop'
  .bundle/ruby/1.9/gems/resque-1.19.0/lib/resque/worker.rb:116:in `work'
  .bundle/ruby/1.9/gems/resque-pool-0.2.0/lib/resque/pool.rb:314:in `block in spawn_worker!'
  .bundle/ruby/1.9/gems/resque-pool-0.2.0/lib/resque/pool.rb:309:in `fork'
  .bundle/ruby/1.9/gems/resque-pool-0.2.0/lib/resque/pool.rb:309:in `spawn_worker!'
  .bundle/ruby/1.9/gems/resque-pool-0.2.0/lib/resque/pool.rb:288:in `block in spawn_missing_workers_for'
  .bundle/ruby/1.9/gems/resque-pool-0.2.0/lib/resque/pool.rb:287:in `times'
  .bundle/ruby/1.9/gems/resque-pool-0.2.0/lib/resque/pool.rb:287:in `spawn_missing_workers_for'
  .bundle/ruby/1.9/gems/resque-pool-0.2.0/lib/resque/pool.rb:273:in `block in maintain_worker_count'
  .bundle/ruby/1.9/gems/resque-pool-0.2.0/lib/resque/pool.rb:271:in `each'
  .bundle/ruby/1.9/gems/resque-pool-0.2.0/lib/resque/pool.rb:271:in `maintain_worker_count'
  .bundle/ruby/1.9/gems/resque-pool-0.2.0/lib/resque/pool.rb:191:in `start'
  .bundle/ruby/1.9/gems/resque-pool-0.2.0/lib/resque/pool.rb:65:in `run'
  .bundle/ruby/1.9/gems/resque-pool-0.2.0/lib/resque/pool/tasks.rb:17:in `block (2 levels) in '
  .bundle/ruby/1.9/gems/rake-0.9.2.2/lib/rake/task.rb:205:in `call'
  .bundle/ruby/1.9/gems/rake-0.9.2.2/lib/rake/task.rb:205:in `block in execute'
  .bundle/ruby/1.9/gems/rake-0.9.2.2/lib/rake/task.rb:200:in `each'
  .bundle/ruby/1.9/gems/rake-0.9.2.2/lib/rake/task.rb:200:in `execute'
  .bundle/ruby/1.9/gems/rake-0.9.2.2/lib/rake/task.rb:158:in `block in invoke_with_call_chain'
  /usr/local/lib/ruby/1.9/monitor.rb:211:in `mon_synchronize'
  .bundle/ruby/1.9/gems/rake-0.9.2.2/lib/rake/task.rb:151:in `invoke_with_call_chain'
  .bundle/ruby/1.9/gems/rake-0.9.2.2/lib/rake/task.rb:144:in `invoke'
  .bundle/ruby/1.9/gems/resque-pool-0.2.0/lib/resque/pool/cli.rb:110:in `start_pool'
  .bundle/ruby/1.9/gems/resque-pool-0.2.0/lib/resque/pool/cli.rb:16:in `run'
  .bundle/ruby/1.9/gems/resque-pool-0.2.0/bin/resque-pool:5:in `'
  .bundle/ruby/1.9/bin/resque-pool:19:in `load'
  .bundle/ruby/1.9/bin/resque-pool:19:in `'

in Rails app from rake task. Thanks for reply!
m.

[rbhughes]

rubydev, check your app's config/resque.yml to ensure it has the correct server/port.

[pietern]

I agree that the error that is raised here does not convey what the underlying problem is and should be made more clear. I addressed this in #176, at 6ee268c#L1R263.