Rubytastic
Rubytastic

Reputation: 15491

resque no longer starts "Can't assign requested address - connect(2)"

Since a few days I'm unable to start resque I have tried debugging this issue on all kinds of ways to no result ! anyone knows a solution? kind regards

This is the log output from:

 bundle exec rake resque:start

log:

bundle exec rake resque:start --trace
** Invoke resque:start (first_time)
** Invoke resque:workers:start (first_time)
** Execute resque:workers:start
rake aborted!
Can't assign requested address - connect(2)

Tasks: TOP => resque:work
(See full trace by running task with --trace)
*** Starting worker dev2.local:4323:critical,high,low
** [09:01:12 2012-06-15] 4323: Registered signals
** Invoke resque:scheduler:start (first_time)
** Execute resque:scheduler:start
rake aborted!
Can't assign requested address - connect(2)

Tasks: TOP => resque:scheduler
(See full trace by running task with --trace)
2012-06-15 21:01:20 Schedule empty! Set Resque.schedule
** Invoke resque:web:start (first_time)
** Execute resque:web:start
/Users/jordan/.rvm/rubies/ruby-1.9.3-p194/lib/ruby/1.9.1/open-uri.rb:346:in `open_http': 500 Internal Server Error (OpenURI::HTTPError)

I tried:

Im totally halted because Resque is integral part of my app, please anyone who knows solution let me know.

Upvotes: 4

Views: 1169

Answers (1)

Rubytastic
Rubytastic

Reputation: 15491

Well...

It seems that, it looks like it's an incompatibility between resque 1.8.2 and newer versions on red is. Like @bknoles suggested.

Using

gem 'resque', "~> 1.20.0"
gem 'resque-scheduler', :require => 'resque_scheduler'

In gemfile fixes the problem

Upvotes: 1

Related Questions