Rabbit MQ Error : unable to perform an operation on node 'rabbit@USERNAME'

Question

Error: unable to perform an operation on node 'rabbit@YASHODIP-PC'. Please see diagnostics information and suggestions below.

Most common reasons for this are:

• Target node is unreachable (eg due to hostname resolution, TCP connection or firewall issues)
• CLI tool fails to authenticate with the server (eg due to CLI tool's Erlang cookie not matching that of the server)
• Target node is not running

In addition to the diagnostics info below:

• See the CLI, clustering and.networking guides on https://rabbitmq.com/documentation.html to learn more
• Consult server logs on node rabbit@YASHODIP-PC
• If target node is configured to use long node names, don't forget to use --longnames with CLI tools

DIAGNOSTICS

attempted to contact: ['rabbit@YASHODIP-PC']

rabbit@YASHODIP-PC: * connected to epmd (port 4369) on YASHODIP-PC * epmd reports: node 'rabbit' not running at all no other nodes on YASHODIP-PC * suggestion: start the node

Current node details: * node name: 'rabbitmqcli-17388-rabbit@YASHODIP-PC' * effective user's home directory: C:\Users\yasho * Erlang cookie hash: 96Pe9121Rb1vncp1IqXA6Q==

---

I am not able to view the status of the rabbitMQ service installed on my local machine. Please suggest resolution.

Answer 1

This error can occur due to

1. Clustering between nodes are not proper
2. The erlang cookie is irrelevant

If you are not working on Clustering then second can be your problem, Please study RabbitMQ, erlang: how to "make sure the erlang cookies are the same"

Answer 2

This type of errors could happen if you have too long hostname. It's the reason why it explains:

If target node is configured to use long node names, don't forget to use --longnames with CLI tools

Solution

edit the rabbit's config file (for RHEL type it's /etc/rabbitmq/rabbitmq.conf ). In the networking section:

#IPv4
listeners.tcp.local = 127.0.0.1:5672
#...

## write your ip and not your hostname
listeners.tcp.ohter_ip = 164.81.0.0:5672 

Answer 3

Old topic, but I stumbled across it looking for reasons. So I will write what I have. In the file /etc/rabbitmq/rabbitmq-env.conf

export RABBITMQ_NODENAME=rabbit@domain.com

replaced by

export RABBITMQ_NODENAME=rabbit@localhost