[chef-dev] Re: [chef] Re: Re: Intermittent chef-expander problem

[Alex Kiernan < >]

[moved to chef-dev]

On Wed, Aug 31, 2011 at 11:12 AM, Alex Kiernan 
<
 >
 wrote:
>>>> 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!
>>
>
> Tried this just on a client (once I'd hacked the gemspecs so it didn't
> continue to pick up 1.5.2) and I still got some corrupt JSON through,
> but I'm guessing the JSON that a client starts with comes from the
> server, so any corruption there would propagate through?
>
> To test that theory I've just hacked up the server similarly...
>

And it's just died in the same way. Though this time I just restarted
rabbitmq and chef-expander is (as expected) happy.

Anyone any ideas? It definitely looks like it's native code corruption
:( My thinking at the moment is to patch chef-expander to discard (and
log) invalid messages since there's little point in it getting into a
die/fork/die loop.

-- 
Alex Kiernan