[rabbitmq-discuss] Debugging clustering issues

[Matthias Radestock]

Andreas,

On 21/06/10 09:10, Andreas Jung wrote:
> ajung at blackmoon:~/sandboxes/occ> bin/rabbitmqctl stop_app
> Stopping node rabbit at blackmoon ...
> ...done.
> ajung at blackmoon:~/sandboxes/occ> bin/rabbitmqctl reset
> Resetting node rabbit at blackmoon ...
> ...done.
> ajung at blackmoon:~/sandboxes/occ> bin/rabbitmqctl cluster
> rabbit at 192.168.0.103 <mailto:rabbit at 192.168.0.103>
> Clustering node rabbit at blackmoon with ['rabbit at 192.168.0.103'] ...
> ...done.
> ajung at blackmoon:~/sandboxes/occ> bin/rabbitmqctl start_app
> Starting node rabbit at blackmoon ...
> ...done.
> ajung at blackmoon:~/sandboxes/occ> bin/rabbitmqctl status
> Status of node rabbit at blackmoon ...
> [{running_applications,[{rabbit,"RabbitMQ","1.8.0"},
>                          {mnesia,"MNESIA  CXC 138 12","4.4.10"},
>                          {os_mon,"CPO  CXC 138 46","2.2.2"},
>                          {sasl,"SASL  CXC 138 11","2.1.6"},
>                          {stdlib,"ERTS  CXC 138 10","1.16.2"},
>                          {kernel,"ERTS  CXC 138 10","2.13.2"}]},
>   {nodes,[rabbit at blackmoon]},
>   {running_nodes,[rabbit at blackmoon]}]
> ...done.
>
> So the node running on 192.168.0.103 is _not_ part of the cluster as
> 'status' shows.
> How can I track this down?

I suspect the problem is that the way you refer to the other node - by 
its IP address - is not the way the node refers to itself. E.g. if the 
other node thinks it's 'rabbit at whitemoon' then that is what you must put 
in the 'cluster' command.


Regards,

Matthias.