[rabbitmq-discuss] rabbitmqctl help

Joel Grandin Joel.Grandin at mathworks.com
Thu Jan 20 18:17:09 GMT 2011

The cookie was the problem. Thanks to all for your help. Any opinions on good resources to read etc for a team not familiar to erlang.

-----Original Message-----
From: rabbitmq-discuss-bounces at lists.rabbitmq.com [mailto:rabbitmq-discuss-bounces at lists.rabbitmq.com] On Behalf Of Matthew Sackman
Sent: Thursday, January 20, 2011 11:52 AM
To: rabbitmq-discuss at lists.rabbitmq.com
Subject: Re: [rabbitmq-discuss] rabbitmqctl help

On Thu, Jan 20, 2011 at 04:45:01PM +0000, Joel Grandin wrote:
> This is the results from "status"
> rabbitmqctl -n rabbit at my-server-name
> Status of node 'rabbit at my-server-name' ...
> Error: unable to connect to node 'rabbit at my-server-name': nodedown
> diagnostics:
> - nodes and their ports on my-server-name: [{rabbit,64066}]
> - current node: 'rabbitmqctl at my-localhost'
> - current node home dir: H:\
> - current node cookie hash: HKx1IftG6awfKfr7YEqB1Q==
> If I run "telnet my-server-name 4369", it connects.

Ok, so our best guess now is that you've got different cookies on both
machines. The erlang cookies must be the same - it's an authentication
token of sorts.

explains where the cookie is stored under windows. You need to make sure
the cookie files on both my-server-name and my-localhost are the same.

rabbitmq-discuss mailing list
rabbitmq-discuss at lists.rabbitmq.com

More information about the rabbitmq-discuss mailing list