[chef] Re: Can't connect to RabbitMQ after upgrade/downgrade debacle

[Autif Khan < >]

On Wed, Feb 27, 2013 at 1:40 PM, Luke Jolly 
<
 >
 wrote:
> I accidentally did a gem update on a working chef server box.  This broke
> chef.  After rolling back all the gems I believe where updated (chef and
> chef-server 0.10.4), I can now run chef, but it is erring.  It is failing to
> talk to rabbitmq correctly.  Rabbitmq is complaining about bad_headers.
> Here's the errors I'm getting:
> chef server.log
> rabbit.log
>
> Here's all my gem versions, and other package versions:
> CentOS release 5.4 (Final)
> rabbitmq-server.x86_64         1.7.2-1.el5
> couchdb.x86_64                      0.11.2-2.el5
> yum ruby versions
>
> I did notice that there are some older versions of gems installed through
> yum, but I believe the new ones are indeed running.  I'm at my whit's end on
> this one and would love any help or suggestions.

Woah! Woah! Woah!

Fascinating.

Presumably this was while running chef via gems and not via the
omnibus installer. Is that assumption correct?