Error: unable to connect to node 'rabbit@xhy-205-4': nodedown

[qq8...@126.com]

Dear:

      Our RabbitMQ already runed aout 122d. But yeasterday we found that it began fall into flow control. We saw that too much connections closed interruptly. Also when we runned 'rabbitmqctl status', it seemed that nodedown.

[root@xhy-205-4 bin]# rabbitmqctl status

Status of node 'rabbit@xhy-205-4' ...

Error: unable to connect to node 'rabbit@xhy-205-4': nodedown

DIAGNOSTICS

===========

attempted to contact: ['rabbit@xhy-205-4']

rabbit@xhy-205-4:

  * connected to epmd (port 4369) on xhy-205-4

  * epmd reports node 'rabbit' running on port 25672

  * TCP connection succeeded but Erlang distribution failed

  * suggestion: hostname mismatch?

  * suggestion: is the cookie set correctly?

  * suggestion: is the Erlang distribution using TLS?

current node details:

- node name: 'rabbitmq-cli-86614@xhy-205-4'

- home dir: /var/lib/rabbitmq

- cookie hash: DQWGDqwTbax4Q1opiXpyXg==

But when we use WebConsole, it works. 

It matchs 'http://www.rabbitmq.com/blog/2014/04/14/finding-bottlenecks-with-rabbitmq-3-3/' first condition. Anything wrong?

[Michael Klishin]

rabbitmqctl status did not tell you that the node is down.

It says

> TCP connection succeeded but Erlang distribution failed

In other words, rabbitmqctl successfully connected to the node but failed to authenticate

with it.

See "How Nodes (and CLI Tools) Authenticate to Each Other"

http://www.rabbitmq.com/clustering.html.

From there you can collect more information about node state using rabbitmqctl.