1

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 (e.g. due to hostname resolution, TCP connection or firewall issues)
  • CLI tool fails to authenticate with the server (e.g. 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.

Yashodip Bhavsar
  • 21
  • 1
  • 1
  • 5

4 Answers4

0

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.other_ip = 164.81.0.0:5672 
chris Frisina
  • 19,086
  • 22
  • 87
  • 167
0

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
0

With linux, in this case /etc/hostname has changed.

Change to old hostname before install rabbitmq

Or systemctl restart rabbitmq-server and re-create user and vhost

0

with windows go to start menu and search 'Service' and find 'RabbitMQ' and click on start.