- From: Alex Kiernan <
>
- To:
- Subject: [chef] Re: Re: Re: Intermittent chef-expander problem
- Date: Sat, 27 Aug 2011 09:53:32 +0100
>
>> > [Thu, 25 Aug 2011 18:24:48 +0100] ERROR: cannot index object because it
>
>> > is inval
>
>> > id JSON:
>
>> > {"action":"add","payload":{"enqueued_at":1314293088,"id":"92a1d57c-4579
>
>> > -446c-8fda-c3331f8477d9","type":"node","database":"chef","item":{
>
>> > ...............
>
>> > "dmi":^@<80><9E>
@
@{"address":"0xEA2E0","firmware_revision":"0.0",
>
>> >
Now you've given me the clue, I'm guessing this is a 64 bit little
endian pointer that's gotten stamped in there...
>
>> > Any ideas?
>
>> >
>
>> > This is Chef 0.10.0 on RHEL 5.5
>
>>
>
>> Sorry should have added RabbitMQ is 2.5.1, Erlang is R14B.
>
>>
>
>
> I've seen something like this in a different context that leads me to
>
> believe it's a bug in the JSON gem or possibly Ruby. It seems to only
>
> occur on Red Hat systems. What version of ruby are you using? Is your
>
> system 64 bit? Is ruby 64 bit?
>
I'm guessing this:
https://github.com/flori/json/issues/46
might be the problem. Time to get that omnibus build working!
--
Alex Kiernan
Archive powered by MHonArc 2.6.16.