Hi @jsantos,
Looking at the message that rabbitmqctl cluster_status
reports:
$ sudo rabbitmqctl cluster_status
sudo: unable to resolve host prodrabbitmq11: Connection timed out
$ sudo rabbitmqctl cluster_status
sudo: unable to resolve host prodrabbitmq12: Connection timed out
Can you try to resolve the ip for the above addresses? You can use the following command that you need to execute in each of the VMs:
ping -c1 prodrabbitmq11
ping -c1 prodrabbitmq12
Azure has an internal DNS server that you may want to use to make each of the machine hostnames resolvable. You can access to it through Resource group > Network interface > DNS servers:

Maybe after the change in the private ips of the nodes, this service is not behaving correctly. To workaround it, as you mentioned, you can use the /etc/hosts
file. However, it seems you added the complete identifier of the rabbitmq node <node>@<machine>
instead of the machine only:
$ cat /etc/hosts
...
10.4.13.19 rabbit@prodrabbitmq11
Can you change the /etc/hosts
file to make sure it contains the following entries?:
Note that you will need to substitute IP_OF_NODE_0
to the real value of the IP.
Node prodrabbitmq10:
IP_OF_NODE_0 prodrabbitmq10
10.4.13.19 prodrabbitmq11
10.4.13.21 prodrabbitmq12
IP_OF_NODE_0 provisioner-local
Node prodrabbitmq11:
IP_OF_NODE_0 prodrabbitmq10
10.4.13.19 prodrabbitmq11
10.4.13.21 prodrabbitmq12
IP_OF_NODE_0 provisioner-peer
10.4.13.19 provisioner-local
Node prodrabbitmq12:
IP_OF_NODE_0 prodrabbitmq10
10.4.13.19 prodrabbitmq11
10.4.13.21 prodrabbitmq12
IP_OF_NODE_0 provisioner-peer
10.4.13.21 provisioner-local
After those changes, try to resolve the names again with the ping
command and restart the rabbitmq services in all the VMs:
sudo service bitnami restart
Let us know if it works.
Regards,
AndrĂŠs Bono.