librelist archives

« back to archive

NoMethodError viewing Failed queue

NoMethodError viewing Failed queue

From:
Mason Jones
Date:
2010-04-29 @ 21:43
Anyone else encountered this error page when trying to view the Failed queue?

NoMethodError at /failed
undefined method `join' for nil:NilClass
file: failed.erb location: __tilt_194e781e80fdf820f2a19b84adfdf9e2 line: 39
BACKTRACE
/usr/bin/resque-web in load
19. load Gem.bin_path('resque', 'resque-web', version)
/usr/bin/resque-web in nil
19. load Gem.bin_path('resque', 'resque-web', version)

I haven't run into this before; however, this is a fairly new server
instance and this might be the first time I've had to view /failed on
it. It's running resque 1.8.0, redis gem 1.0.6, redis-namespace 0.4.2,
and redis 1.2.6.

Thanks for any ideas...

Re: [resque] NoMethodError viewing Failed queue

From:
Chris Wanstrath
Date:
2010-04-30 @ 01:22
On Thu, Apr 29, 2010 at 2:43 PM, Mason Jones <masonoise@gmail.com> wrote:
> Anyone else encountered this error page when trying to view the Failed queue?

This should be fixed in 1.8.1 which was just released. Sorry about that.

Re: [resque] NoMethodError viewing Failed queue

From:
Tim Haines
Date:
2010-04-29 @ 22:02
Hey Mason,

I've had a few intermittent problems viewing the failed job list.  I haven't
taken the time to dig in to the problem yet.  I've been clearing them with
Resque::Failed.clear  (or maybe it's Resque::Failures.clear).  There's
definitely some kind of problem there though.

My app usually uses a very long param list - I'm wondering if that's
related.

Tim.

On Fri, Apr 30, 2010 at 9:43 AM, Mason Jones <masonoise@gmail.com> wrote:

> Anyone else encountered this error page when trying to view the Failed
> queue?
>
> NoMethodError at /failed
> undefined method `join' for nil:NilClass
> file: failed.erb location: __tilt_194e781e80fdf820f2a19b84adfdf9e2 line: 39
> BACKTRACE
> /usr/bin/resque-web in load
> 19. load Gem.bin_path('resque', 'resque-web', version)
> /usr/bin/resque-web in nil
> 19. load Gem.bin_path('resque', 'resque-web', version)
>
> I haven't run into this before; however, this is a fairly new server
> instance and this might be the first time I've had to view /failed on
> it. It's running resque 1.8.0, redis gem 1.0.6, redis-namespace 0.4.2,
> and redis 1.2.6.
>
> Thanks for any ideas...
>

Re: [resque] NoMethodError viewing Failed queue

From:
Mason Jones
Date:
2010-04-29 @ 22:31
On Thu, Apr 29, 2010 at 3:02 PM, Tim Haines <tmhaines@gmail.com> wrote:
> Hey Mason,
> I've had a few intermittent problems viewing the failed job list.  I haven't
> taken the time to dig in to the problem yet.  I've been clearing them with
> Resque::Failed.clear  (or maybe it's Resque::Failures.clear).  There's
> definitely some kind of problem there though.

Hm. I don't want to just clear the list since I want to check out the
exception/whatever that's behind the failures. But I suppose I can
probably go into redis directly and check that and then clear them
out.

> My app usually uses a very long param list - I'm wondering if that's
> related.

My list is very short, just a single integer ID being passed into the
workers, so that wouldn't be the problem in my case I'm sure.


> On Fri, Apr 30, 2010 at 9:43 AM, Mason Jones <masonoise@gmail.com> wrote:
>>
>> Anyone else encountered this error page when trying to view the Failed
>> queue?
>>
>> NoMethodError at /failed
>> undefined method `join' for nil:NilClass
>> file: failed.erb location: __tilt_194e781e80fdf820f2a19b84adfdf9e2 line:
>> 39
>> BACKTRACE
>> /usr/bin/resque-web in load
>> 19. load Gem.bin_path('resque', 'resque-web', version)
>> /usr/bin/resque-web in nil
>> 19. load Gem.bin_path('resque', 'resque-web', version)
>>
>> I haven't run into this before; however, this is a fairly new server
>> instance and this might be the first time I've had to view /failed on
>> it. It's running resque 1.8.0, redis gem 1.0.6, redis-namespace 0.4.2,
>> and redis 1.2.6.
>>
>> Thanks for any ideas...
>
>

Re: [resque] NoMethodError viewing Failed queue

From:
Mason Jones
Date:
2010-04-29 @ 23:02
Well, looking into redis doesn't give me a whole lot more info, but I
did notice that the two failed jobs seem to coincide with two workers
going away, and in the resque:failed list I just found two entries
like this:


{"queue":"load_queue","payload":{"args":[88064],"class":"LoadEntry"},"exception":"Resque::DirtyExit","failed_at":"2010/04/29

21:23:47","worker":"domU-12-31-39-0F-B9-D2:22990:load_entry","error":"Resque::DirtyExit","backtrace":null}

So it appears that DirtyExit causes the worker to terminate? Any
thoughts about how to determine the cause of the exit?

This is separate from the exception trying to view /failed, I guess...

Thanks!

On Thu, Apr 29, 2010 at 3:31 PM, Mason Jones <masonoise@gmail.com> wrote:
> On Thu, Apr 29, 2010 at 3:02 PM, Tim Haines <tmhaines@gmail.com> wrote:
>> Hey Mason,
>> I've had a few intermittent problems viewing the failed job list.  I haven't
>> taken the time to dig in to the problem yet.  I've been clearing them with
>> Resque::Failed.clear  (or maybe it's Resque::Failures.clear).  There's
>> definitely some kind of problem there though.
>
> Hm. I don't want to just clear the list since I want to check out the
> exception/whatever that's behind the failures. But I suppose I can
> probably go into redis directly and check that and then clear them
> out.
>
>> My app usually uses a very long param list - I'm wondering if that's
>> related.
>
> My list is very short, just a single integer ID being passed into the
> workers, so that wouldn't be the problem in my case I'm sure.
>
>
>> On Fri, Apr 30, 2010 at 9:43 AM, Mason Jones <masonoise@gmail.com> wrote:
>>>
>>> Anyone else encountered this error page when trying to view the Failed
>>> queue?
>>>
>>> NoMethodError at /failed
>>> undefined method `join' for nil:NilClass
>>> file: failed.erb location: __tilt_194e781e80fdf820f2a19b84adfdf9e2 line:
>>> 39
>>> BACKTRACE
>>> /usr/bin/resque-web in load
>>> 19. load Gem.bin_path('resque', 'resque-web', version)
>>> /usr/bin/resque-web in nil
>>> 19. load Gem.bin_path('resque', 'resque-web', version)
>>>
>>> I haven't run into this before; however, this is a fairly new server
>>> instance and this might be the first time I've had to view /failed on
>>> it. It's running resque 1.8.0, redis gem 1.0.6, redis-namespace 0.4.2,
>>> and redis 1.2.6.
>>>
>>> Thanks for any ideas...
>>
>>
>