librelist archives

« back to archive

Re: Resque-web problem

Re: Resque-web problem

From:
Bratish Goswami
Date:
2010-03-09 @ 16:39
The first mail was dropped in between a confirmation process (as stated by
librelist).
Please look below for my query.
Any help will be highly appreciated.

Thanks
Bratish

On Tue, Mar 9, 2010 at 9:59 PM, Bratish Goswami <bratish@truesparrow.com>wrote:

> Hi there,
>
> Facing one problem running resque-web with *resque-web -p 8282
> rails_root/config/initializers/resque.rb*
> The url *http://localhost:7501/ *is redirecting to *
> http://localhost:7501/overview* and showing the following error:
>
> "NoMethodError at /overview
> undefined method `start_with?' for "/overview":String"
>  # /usr/bin/resque-web in nil
> load Gem.bin_path('resque', 'resque-web', version)
>
> Any ideas, what could be the problem?
>
> Thanks in advance.
>
> -Bratish
>

Re: [resque] Re: Resque-web problem

From:
Philippe Lafoucrière
Date:
2010-03-09 @ 16:40
On Tue, Mar 9, 2010 at 5:39 PM, Bratish Goswami <bratish@truesparrow.com> wrote:
> The first mail was dropped in between a confirmation process (as stated by
> librelist).
> Please look below for my query.
> Any help will be highly appreciated.

Any chance you are running ruby 1.8.6 ?

Re: [resque] Re: Resque-web problem

From:
Bratish Goswami
Date:
2010-03-09 @ 16:47
You got it right Philippe, ruby -v says *ruby 1.8.6 (2008-08-11 patchlevel
287) [i386-linux]*
*
*
Is there a problem with it?*
*

Thanks for your reply.

-Bratish

2010/3/9 Philippe Lafoucrière <philippe.lafoucriere@gmail.com>

> On Tue, Mar 9, 2010 at 5:39 PM, Bratish Goswami <bratish@truesparrow.com>
> wrote:
> > The first mail was dropped in between a confirmation process (as stated
> by
> > librelist).
> > Please look below for my query.
> > Any help will be highly appreciated.
>
> Any chance you are running ruby 1.8.6 ?
>

Re: [resque] Re: Resque-web problem

From:
Philippe Lafoucrière
Date:
2010-03-09 @ 16:50
On Tue, Mar 9, 2010 at 5:47 PM, Bratish Goswami <bratish@truesparrow.com> wrote:
> You got it right Philippe, ruby -v says ruby 1.8.6 (2008-08-11 patchlevel
> 287) [i386-linux]
>
> Is there a problem with it?

My bad :(
I introduced this bug a few commits ago, I didn't know start_with? was
introduced in 1.8.7
It has been fixed (but not released yet) :

http://github.com/defunkt/resque/commit/fc26509c206f8f3980b89a0d790c734f59710480

Re: [resque] Re: Resque-web problem

From:
Bratish Goswami
Date:
2010-03-09 @ 17:07
Thanks so much :-)
This correction fixed the problem.

Now in the mean time, another thing is giving problem. *The forked workers
are always starting in development mode* (i confirmed it by log prints,
these are going to development.log).
I'm clueless from where it's taking 'development', as the main worker is
starting with 'production' environment.

Again thanks in advance.

-Bratish

2010/3/9 Philippe Lafoucrière <philippe.lafoucriere@gmail.com>

> On Tue, Mar 9, 2010 at 5:47 PM, Bratish Goswami <bratish@truesparrow.com>
> wrote:
> > You got it right Philippe, ruby -v says ruby 1.8.6 (2008-08-11 patchlevel
> > 287) [i386-linux]
> >
> > Is there a problem with it?
>
> My bad :(
> I introduced this bug a few commits ago, I didn't know start_with? was
> introduced in 1.8.7
> It has been fixed (but not released yet) :
>
>
> http://github.com/defunkt/resque/commit/fc26509c206f8f3980b89a0d790c734f59710480
>

Re: [resque] Re: Resque-web problem

From:
Philippe Lafoucrière
Date:
2010-03-09 @ 17:12
On Tue, Mar 9, 2010 at 6:07 PM, Bratish Goswami <bratish@truesparrow.com> wrote:
> Thanks so much :-)
> This correction fixed the problem.
> Now in the mean time, another thing is giving problem. The forked workers
> are always starting in development mode (i confirmed it by log prints, these
> are going to development.log).
> I'm clueless from where it's taking 'development', as the main worker is
> starting with 'production' environment.

you didn't create a resque.rb file in lib/tasks to load to env :

task "resque:setup" => :environment

;)

Re: [resque] Re: Resque-web problem

From:
Bratish Goswami
Date:
2010-03-09 @ 17:32
Thanks Philippe but I didn't get the whole thing.
Let me be elaborate. My setup is something like the following:

In *lib/tasks/fab_resque.rake*

namespace :resque do
   desc "Copy item to place"
   task( :work => :environment ) do
     p Resque.redis
   end

  task "resque:setup" => :environment do
     ENV['RAILS_ENV'] = 'production'
   end
end
------------------------------------

In *config/initializers/resque.rb*

require 'resque'

rails_root = ENV['RAILS_ROOT'] || File.dirname(__FILE__) + '/../..'
rails_env = ENV['RAILS_ENV'] || 'development'

resque_config = YAML.load_file(rails_root + '/config/resque.yml')
Resque.redis = resque_config["#{rails_env}_redis"]
Resque.redis.namespace = "fab:#{rails_env}"
------------------------------------

In *config/resque.yml*

development_redis: localhost:9000
test_redis: localhost:9000
staging_redis: localhost:9000
production_redis: localhost:9000
------------------------------------

Is there anything missing. Today is the first time I'm burning my fingers
with Resque.
It's highly possible that I'm missing something.

As always, appreciate your help.

-Bratish



2010/3/9 Philippe Lafoucrière <philippe.lafoucriere@gmail.com>

> On Tue, Mar 9, 2010 at 6:07 PM, Bratish Goswami <bratish@truesparrow.com>
> wrote:
> > Thanks so much :-)
> > This correction fixed the problem.
> > Now in the mean time, another thing is giving problem. The forked workers
> > are always starting in development mode (i confirmed it by log prints,
> these
> > are going to development.log).
> > I'm clueless from where it's taking 'development', as the main worker is
> > starting with 'production' environment.
>
> you didn't create a resque.rb file in lib/tasks to load to env :
>
> task "resque:setup" => :environment
>
> ;)
>

Re: [resque] Re: Resque-web problem

From:
Andrew Nordman
Date:
2010-03-09 @ 17:44
Based on that fab_resque.rake, your rake task would be resque:resque:setup.
 drop the "resque:" from the task name and your problem should be resolved,
or as Philippe said, you can decrease the size just by doing task
"resque:setup => :environment" as rake will pick the environment up from the
=> :environment reference.

- Andrew

On Tue, Mar 9, 2010 at 11:32 AM, Bratish Goswami <bratish@truesparrow.com>wrote:

> Thanks Philippe but I didn't get the whole thing.
> Let me be elaborate. My setup is something like the following:
>
> In *lib/tasks/fab_resque.rake*
>
> namespace :resque do
>    desc "Copy item to place"
>    task( :work => :environment ) do
>      p Resque.redis
>    end
>
>   task "resque:setup" => :environment do
>      ENV['RAILS_ENV'] = 'production'
>    end
> end
> ------------------------------------
>
> In *config/initializers/resque.rb*
>
> require 'resque'
>
> rails_root = ENV['RAILS_ROOT'] || File.dirname(__FILE__) + '/../..'
> rails_env = ENV['RAILS_ENV'] || 'development'
>
> resque_config = YAML.load_file(rails_root + '/config/resque.yml')
> Resque.redis = resque_config["#{rails_env}_redis"]
> Resque.redis.namespace = "fab:#{rails_env}"
> ------------------------------------
>
> In *config/resque.yml*
>
> development_redis: localhost:9000
> test_redis: localhost:9000
> staging_redis: localhost:9000
> production_redis: localhost:9000
> ------------------------------------
>
> Is there anything missing. Today is the first time I'm burning my fingers
> with Resque.
> It's highly possible that I'm missing something.
>
> As always, appreciate your help.
>
> -Bratish
>
>
>
> 2010/3/9 Philippe Lafoucrière <philippe.lafoucriere@gmail.com>
>
>> On Tue, Mar 9, 2010 at 6:07 PM, Bratish Goswami <bratish@truesparrow.com>
>> wrote:
>>
>> > Thanks so much :-)
>> > This correction fixed the problem.
>> > Now in the mean time, another thing is giving problem. The forked
>> workers
>> > are always starting in development mode (i confirmed it by log prints,
>> these
>> > are going to development.log).
>> > I'm clueless from where it's taking 'development', as the main worker is
>> > starting with 'production' environment.
>>
>> you didn't create a resque.rb file in lib/tasks to load to env :
>>
>> task "resque:setup" => :environment
>>
>> ;)
>>
>
>

Re: [resque] Re: Resque-web problem

From:
Bratish Goswami
Date:
2010-03-09 @ 18:11
Thank you both, but still no luck for me.
Now the *lib/tasks/fab_resque.rake *looks like

require 'resque/tasks'
task "resque:setup" => :environment
------------------------------------------------------------
Is *require 'resque_scheduler/tasks'* mandatory?
As I feel there's no need for *resque_scheduler* in this project presently.

Thanks
Bratish

On Tue, Mar 9, 2010 at 11:14 PM, Andrew Nordman <cadwallion@gmail.com>wrote:

> Based on that fab_resque.rake, your rake task would be resque:resque:setup.
>  drop the "resque:" from the task name and your problem should be resolved,
> or as Philippe said, you can decrease the size just by doing task
> "resque:setup => :environment" as rake will pick the environment up from the
> => :environment reference.
>
> - Andrew
>
>
> On Tue, Mar 9, 2010 at 11:32 AM, Bratish Goswami <bratish@truesparrow.com>wrote:
>
>> Thanks Philippe but I didn't get the whole thing.
>> Let me be elaborate. My setup is something like the following:
>>
>> In *lib/tasks/fab_resque.rake*
>>
>> namespace :resque do
>>    desc "Copy item to place"
>>    task( :work => :environment ) do
>>      p Resque.redis
>>    end
>>
>>   task "resque:setup" => :environment do
>>      ENV['RAILS_ENV'] = 'production'
>>    end
>> end
>> ------------------------------------
>>
>> In *config/initializers/resque.rb*
>>
>> require 'resque'
>>
>> rails_root = ENV['RAILS_ROOT'] || File.dirname(__FILE__) + '/../..'
>> rails_env = ENV['RAILS_ENV'] || 'development'
>>
>> resque_config = YAML.load_file(rails_root + '/config/resque.yml')
>> Resque.redis = resque_config["#{rails_env}_redis"]
>> Resque.redis.namespace = "fab:#{rails_env}"
>> ------------------------------------
>>
>> In *config/resque.yml*
>>
>> development_redis: localhost:9000
>> test_redis: localhost:9000
>> staging_redis: localhost:9000
>> production_redis: localhost:9000
>> ------------------------------------
>>
>> Is there anything missing. Today is the first time I'm burning my fingers
>> with Resque.
>> It's highly possible that I'm missing something.
>>
>> As always, appreciate your help.
>>
>> -Bratish
>>
>>
>>
>> 2010/3/9 Philippe Lafoucrière <philippe.lafoucriere@gmail.com>
>>
>>> On Tue, Mar 9, 2010 at 6:07 PM, Bratish Goswami <bratish@truesparrow.com>
>>> wrote:
>>>
>>> > Thanks so much :-)
>>> > This correction fixed the problem.
>>> > Now in the mean time, another thing is giving problem. The forked
>>> workers
>>> > are always starting in development mode (i confirmed it by log prints,
>>> these
>>> > are going to development.log).
>>> > I'm clueless from where it's taking 'development', as the main worker
>>> is
>>> > starting with 'production' environment.
>>>
>>> you didn't create a resque.rb file in lib/tasks to load to env :
>>>
>>> task "resque:setup" => :environment
>>>
>>> ;)
>>>
>>
>>
>

Re: [resque] Re: Resque-web problem

From:
Philippe Lafoucrière
Date:
2010-03-09 @ 18:14
On Tue, Mar 9, 2010 at 7:11 PM, Bratish Goswami <bratish@truesparrow.com> wrote:
> Is require 'resque_scheduler/tasks' mandatory?
> As I feel there's no need for resque_scheduler in this project presently.

it's not, unless you're using the resque_scheduler plugin (at which
you should take a look btw ;) )

Re: [resque] Re: Resque-web problem

From:
Bratish Goswami
Date:
2010-03-09 @ 18:19
I have already looked into it Philippe, that's a very nice tool indeed.
But the present problem I cannot get rid of is, the worker is starting sane
with 'production' environment. But when it's forking a child process, the
new process is getting a 'development' environment.
Completely puzzled :-(

Thanks
Bratish

2010/3/9 Philippe Lafoucrière <philippe.lafoucriere@gmail.com>

> On Tue, Mar 9, 2010 at 7:11 PM, Bratish Goswami <bratish@truesparrow.com>
> wrote:
> > Is require 'resque_scheduler/tasks' mandatory?
> > As I feel there's no need for resque_scheduler in this project presently.
>
> it's not, unless you're using the resque_scheduler plugin (at which
> you should take a look btw ;) )
>

Re: [resque] Re: Resque-web problem

From:
Philippe Lafoucrière
Date:
2010-03-09 @ 18:21
On Tue, Mar 9, 2010 at 7:19 PM, Bratish Goswami <bratish@truesparrow.com> wrote:
> I have already looked into it Philippe, that's a very nice tool indeed.
> But the present problem I cannot get rid of is, the worker is starting sane
> with 'production' environment. But when it's forking a child process, the
> new process is getting a 'development' environment.
> Completely puzzled :-(

could you send us the command line you are using please ?

Re: [resque] Re: Resque-web problem

From:
Bratish Goswami
Date:
2010-03-09 @ 18:25
Yeah, sure

VVERBOSE=1 QUEUE=* rake resque:work --trace

-Bratish

2010/3/9 Philippe Lafoucrière <philippe.lafoucriere@gmail.com>

> On Tue, Mar 9, 2010 at 7:19 PM, Bratish Goswami <bratish@truesparrow.com>
> wrote:
> > I have already looked into it Philippe, that's a very nice tool indeed.
> > But the present problem I cannot get rid of is, the worker is starting
> sane
> > with 'production' environment. But when it's forking a child process, the
> > new process is getting a 'development' environment.
> > Completely puzzled :-(
>
> could you send us the command line you are using please ?
>

Re: [resque] Re: Resque-web problem

From:
Philippe Lafoucrière
Date:
2010-03-09 @ 18:27
On Tue, Mar 9, 2010 at 7:25 PM, Bratish Goswami <bratish@truesparrow.com> wrote:
> VVERBOSE=1 QUEUE=* rake resque:work --trace

Have you tried to add the RAILS_ENV ?

RAILS_ENV=production QUEUE=* rake resque:work

it's necessary if the rails_env is not set in environment.rb (is it?)

Re: [resque] Re: Resque-web problem

From:
Bratish Goswami
Date:
2010-03-09 @ 18:45
RELIEF... finally this worked. Thanks a lot Philippe and Andrew :-)

But one thing, i checked it thoroughly that the rails-env is (and was) set
to production. This was the first thing I looked for, after discovering the
issue.
Is there any possible bug hidden?

But not gonna think of it anymore now, it's well past midnight here.

Once again, thank you guys for your help.

-Bratish

2010/3/9 Philippe Lafoucrière <philippe.lafoucriere@gmail.com>

> On Tue, Mar 9, 2010 at 7:25 PM, Bratish Goswami <bratish@truesparrow.com>
> wrote:
> > VVERBOSE=1 QUEUE=* rake resque:work --trace
>
> Have you tried to add the RAILS_ENV ?
>
> RAILS_ENV=production QUEUE=* rake resque:work
>
> it's necessary if the rails_env is not set in environment.rb (is it?)
>

Re: [resque] Re: Resque-web problem

From:
Philippe Lafoucrière
Date:
2010-03-09 @ 18:57
On Tue, Mar 9, 2010 at 7:45 PM, Bratish Goswami <bratish@truesparrow.com> wrote:
> RELIEF... finally this worked. Thanks a lot Philippe and Andrew :-)
>
> But one thing, i checked it thoroughly that the rails-env is (and was) set
> to production. This was the first thing I looked for, after discovering the
> issue.
> Is there any possible bug hidden?
> But not gonna think of it anymore now, it's well past midnight here.
> Once again, thank you guys for your help.

you're welcome. I'll try to find some time to investigate this. More
important, it's working :)
Good night

Re: [resque] Re: Resque-web problem

From:
Bratish Goswami
Date:
2010-03-10 @ 11:02
Hey guys,

Updated to 1.6.0, but still I got to write it like *RAILS_ENV=production
QUEUE=* rake resque:work  *to get it work properly.

Please tell me one more thing, how/where to mention the* timeout for redis
connection*?


Thanks
Bratish


2010/3/10 Philippe Lafoucrière <philippe.lafoucriere@gmail.com>

> On Tue, Mar 9, 2010 at 7:45 PM, Bratish Goswami <bratish@truesparrow.com>
> wrote:
> > RELIEF... finally this worked. Thanks a lot Philippe and Andrew :-)
> >
> > But one thing, i checked it thoroughly that the rails-env is (and was)
> set
> > to production. This was the first thing I looked for, after discovering
> the
> > issue.
> > Is there any possible bug hidden?
> > But not gonna think of it anymore now, it's well past midnight here.
> > Once again, thank you guys for your help.
>
> you're welcome. I'll try to find some time to investigate this. More
> important, it's working :)
> Good night
>

Re: [resque] Re: Resque-web problem

From:
Bratish Goswami
Date:
2010-03-10 @ 13:45
for this timeout related question, i found these from
http://github.com/ezmobius/redis-rb/blob/master/lib/redis.rb

# We support connect() timeout only if system_timer is availabe
# or if we are running against Ruby >= 1.9
# Timeout reading from the socket instead will be supported anyway.

Is this portion related to the question I asked?


Bratish Goswami
Senior Software Engineer
True Sparrow Systems
Pune, India

On Wed, Mar 10, 2010 at 4:32 PM, Bratish Goswami <bratish@truesparrow.com>wrote:

> Hey guys,
>
> Updated to 1.6.0, but still I got to write it like *RAILS_ENV=production
> QUEUE=* rake resque:work  *to get it work properly.
>
> Please tell me one more thing, how/where to mention the* timeout for redis
> connection*?
>
>
> Thanks
> Bratish
>
>
> 2010/3/10 Philippe Lafoucrière <philippe.lafoucriere@gmail.com>
>
> On Tue, Mar 9, 2010 at 7:45 PM, Bratish Goswami <bratish@truesparrow.com>
>> wrote:
>> > RELIEF... finally this worked. Thanks a lot Philippe and Andrew :-)
>> >
>> > But one thing, i checked it thoroughly that the rails-env is (and was)
>> set
>> > to production. This was the first thing I looked for, after discovering
>> the
>> > issue.
>> > Is there any possible bug hidden?
>> > But not gonna think of it anymore now, it's well past midnight here.
>> > Once again, thank you guys for your help.
>>
>> you're welcome. I'll try to find some time to investigate this. More
>> important, it's working :)
>> Good night
>>
>
>

Re: [resque] Re: Resque-web problem

From:
Bratish Goswami
Date:
2010-03-10 @ 12:36
Yet another question...

How can we re-process the failed jobs? Can we retry failed jobs by manually
setting some flags?
Please suggest.

Thanks in advance...

-Bratish

On Wed, Mar 10, 2010 at 4:32 PM, Bratish Goswami <bratish@truesparrow.com>wrote:

> Hey guys,
>
> Updated to 1.6.0, but still I got to write it like *RAILS_ENV=production
> QUEUE=* rake resque:work  *to get it work properly.
>
> Please tell me one more thing, how/where to mention the* timeout for redis
> connection*?
>
>
> Thanks
> Bratish
>
>
> 2010/3/10 Philippe Lafoucrière <philippe.lafoucriere@gmail.com>
>
> On Tue, Mar 9, 2010 at 7:45 PM, Bratish Goswami <bratish@truesparrow.com>
>> wrote:
>> > RELIEF... finally this worked. Thanks a lot Philippe and Andrew :-)
>> >
>> > But one thing, i checked it thoroughly that the rails-env is (and was)
>> set
>> > to production. This was the first thing I looked for, after discovering
>> the
>> > issue.
>> > Is there any possible bug hidden?
>> > But not gonna think of it anymore now, it's well past midnight here.
>> > Once again, thank you guys for your help.
>>
>> you're welcome. I'll try to find some time to investigate this. More
>> important, it's working :)
>> Good night
>>
>
>

Re: [resque] Re: Resque-web problem

From:
Bratish Goswami
Date:
2010-03-10 @ 13:20
Okay, this snippet solved

ftasks = Resque::Failure.all(0, 1000000)
Resque::Failure.clear()
ftasks.each do |ftask|
  queue = ftask["queue"]
  payload = ftask["payload"]
  Resque::Job.new(queue, payload).recreate()
end


-Bratish

On Wed, Mar 10, 2010 at 6:06 PM, Bratish Goswami <bratish@truesparrow.com>wrote:

> Yet another question...
>
> How can we re-process the failed jobs? Can we retry failed jobs by manually
> setting some flags?
> Please suggest.
>
> Thanks in advance...
>
> -Bratish
>
> On Wed, Mar 10, 2010 at 4:32 PM, Bratish Goswami <bratish@truesparrow.com>wrote:
>
>> Hey guys,
>>
>> Updated to 1.6.0, but still I got to write it like *RAILS_ENV=production
>> QUEUE=* rake resque:work  *to get it work properly.
>>
>> Please tell me one more thing, how/where to mention the* timeout for
>> redis connection*?
>>
>>
>> Thanks
>> Bratish
>>
>>
>> 2010/3/10 Philippe Lafoucrière <philippe.lafoucriere@gmail.com>
>>
>> On Tue, Mar 9, 2010 at 7:45 PM, Bratish Goswami <bratish@truesparrow.com>
>>> wrote:
>>> > RELIEF... finally this worked. Thanks a lot Philippe and Andrew :-)
>>> >
>>> > But one thing, i checked it thoroughly that the rails-env is (and was)
>>> set
>>> > to production. This was the first thing I looked for, after discovering
>>> the
>>> > issue.
>>> > Is there any possible bug hidden?
>>> > But not gonna think of it anymore now, it's well past midnight here.
>>> > Once again, thank you guys for your help.
>>>
>>> you're welcome. I'll try to find some time to investigate this. More
>>> important, it's working :)
>>> Good night
>>>
>>
>>
>

Re: [resque] Re: Resque-web problem

From:
Chris Wanstrath
Date:
2010-03-10 @ 20:52
On Wed, Mar 10, 2010 at 4:36 AM, Bratish Goswami
<bratish@truesparrow.com> wrote:

> How can we re-process the failed jobs? Can we retry failed jobs by manually
> setting some flags?

I believe the resque-web interface has a "retry" button, too. But
that's manual and for individual jobs.

-- 
Chris Wanstrath
http://github.com/defunkt

Re: [resque] Re: Resque-web problem

From:
Chris Wanstrath
Date:
2010-03-10 @ 20:50
On Wed, Mar 10, 2010 at 3:02 AM, Bratish Goswami
<bratish@truesparrow.com> wrote:

> Updated to 1.6.0, but still I got to write it like RAILS_ENV=production
> QUEUE=* rake resque:work  to get it work properly.

How do you *want* to write it?

If you just want to do `rake jobs:work` or something you can add this
to a Rakefile or .rake file:

https://gist.github.com/2385aed45a7c3a4a3b82

> Please tell me one more thing, how/where to mention the timeout for redis
> connection?

The timeout thing is a pickle. We have no go way to let you set it directly.

Instead you have to create the Redis object by hand. Anyone have an
idea for this?

Maybe you should be able to pass `Resque.redis =` a hash.

Resque.redis = {
  :timeout => 0.2,
  :db => 2,
  :host => blah,
  :port => 1234
}

Chris

Re: [resque] Re: Resque-web problem

From:
Philippe Lafoucrière
Date:
2010-03-09 @ 17:39
On Tue, Mar 9, 2010 at 6:32 PM, Bratish Goswami <bratish@truesparrow.com> wrote:
> Thanks Philippe but I didn't get the whole thing.
> Let me be elaborate. My setup is something like the following:
> In lib/tasks/fab_resque.rake

More simple :
$ cat lib/tasks/resque.rake
require 'resque/tasks'
require 'resque_scheduler/tasks'
task "resque:setup" => :environment

that's it, no more :)

> ------------------------------------
>
> In config/initializers/resque.rb
>
> require 'resque'
>
> rails_root = ENV['RAILS_ROOT'] || File.dirname(__FILE__) + '/../..'
> rails_env = ENV['RAILS_ENV'] || 'development'
>
> resque_config = YAML.load_file(rails_root + '/config/resque.yml')
> Resque.redis = resque_config["#{rails_env}_redis"]
> Resque.redis.namespace = "fab:#{rails_env}"

sounds good ! (don't know why you are overriding the namespace, but
you might have a good reason)

> ------------------------------------
> In config/resque.yml
> development_redis: localhost:9000
> test_redis: localhost:9000
> staging_redis: localhost:9000
> production_redis: localhost:9000
> ------------------------------------

Good also

> Is there anything missing. Today is the first time I'm burning my fingers
> with Resque.
> It's highly possible that I'm missing something.
> As always, appreciate your help.

Everything sounds in place, you should be able to run (and enjoy)
resque without problem now.
Let me now if the workers are starting now

Re: [resque] Re: Resque-web problem

From:
Chris Wanstrath
Date:
2010-03-09 @ 18:57
On Tue, Mar 9, 2010 at 8:39 AM, Bratish Goswami <bratish@truesparrow.com> wrote:

> "NoMethodError at /overview
> undefined method `start_with?' for "/overview":String"
  # /usr/bin/resque-web in nil
> load Gem.bin_path('resque', 'resque-web', version)

I just pushed 1.6.0 which should fix this - sorry about that!

-- 
Chris Wanstrath
http://github.com/defunkt