Reputation: 791
I've just installed rabbitmq on 2 new VMs and tried to create a simple two node cluster. I've copied the erlang cookie file from one machine to both locations on that machine (C:\Users{username} and C:\Windows\System32\config\systemprofile) and those locations on the other machine as well.
When I try to join one to the other to create a cluster using the rabbitmqctl join_cluster command, I get the following output:
Clustering node rabbit@{machinename1} with rabbit@{machinename2}
Error: unable to perform an operation on node 'rabbit@{machinename2}. 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 http://rabbitmq.com/documentation.html to learn more
* Consult server logs on node rabbit@{machinename2}
DIAGNOSTICS
===========
attempted to contact: ['{machinename2}']
rabbit@{machinename2}:
* connected to epmd (port 4369) on {machinename2}
* epmd reports node 'rabbit' uses port 25672 for inter-node and CLI tool traffic
* TCP connection succeeded but Erlang distribution failed
* Hostname mismatch: node "rabbit@{machinename2}" believes its host is different. Please ensure that hostnames resolve the same way locally and on "rabbit@{machinename2}"
Current node details:
* node name: 'rabbitmqcli60@{machinename1}'
* effective user's home directory: {homedirectory}
* Erlang cookie hash: {hash}
Everyone on the internet seems to be saying that this is caused by having cookie mismatches, but I've verified that they're the same. What am I missing here?
Running Erlang OTP 20.2 and rabbitMQ 3.7.3
Upvotes: 0
Views: 1436
Reputation: 11
I have noticed that join_cluster
is case sensitive when it comes to the machine name.
Upvotes: 1