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

[Daniel DeLeo < >]

On Friday, August 26, 2011 at 3:37 AM, Alex Kiernan wrote:
> On Fri, Aug 26, 2011 at 11:16 AM, Alex Kiernan 
> <
 
>  
> (mailto:
 )>
>  wrote:
> > We've an intermittent chef-expander problem... every few days it'll
> > get invalid JSON from rabbitmq, the pattern's always the same, 8
> > octets of corruption, the last 4 of which are always NUL. If we
> > restart rabbitmq & chef-expander the problem goes away for a few days,
> > then comes back... a (heavily snipped) example is:

Why restart chef-expander? Does the problem persist until you restart it?

> > 
> > [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",
> > 
> > Any ideas?
> > 
> > This is Chef 0.10.0 on RHEL 5.5
> 
> Sorry should have added RabbitMQ is 2.5.1, Erlang is R14B.
> 
> -- 
> Alex Kiernan
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?

-- 
Dan DeLeo