[rabbitmq-discuss] newbie problem--'Error: unable to connect to node 'rabbit at rabbitmq-small02-dev': nodedown'

John Stoner johnstoner2 at gmail.com
Fri Mar 16 21:26:52 GMT 2012


still getting

March 16, 2012 @ 08:54:01PM: ~
[jstoner at rabbitmq-small02-dev]> sudo rabbitmqctl cluster
rabbit at rabbitmq-small01-dev
Clustering node 'rabbit at rabbitmq-small02-dev' with
['rabbit at rabbitmq-small01-dev'] ...
Error: {no_running_cluster_nodes,['rabbit at rabbitmq-small01-dev'],
                                 ['rabbit at rabbitmq-small01-dev']}

I changed the rabbitmq.config to

                        [{inet_dist_listen_min, [some number]},
                         {inet_dist_listen_max, [another number]}]

on both servers, and restarted.

I think we have the right ports open now.

The erlang cookie matches.

seeing traffic on 4369, but not the other ports.

What else could be wrong?

On Fri, Mar 16, 2012 at 1:37 PM, Michael Cumings <
mcumings at narrativescience.com> wrote:

> So what is the considerations on having 5 over 10 or 1?  Is there a
> reasonable criteria that can be used to determine what an appropriate
> number of ports that should be allocated?
> On Fri, Mar 16, 2012 at 12:56 PM, Emile Joubert <emile at rabbitmq.com>wrote:
>> Hi John,
>> I assume that you established the reason for the clustering problems
>> encountered earlier was due to firewall configuration.
>> On 16/03/12 17:25, John Stoner wrote:
>> > We're looking to open fewer ports, not more./ /Is there a minimum we
>> > could do? Would one work, or would it break something else?
>> One port is possible (then inet_dist_listen_min = inet_dist_listen_max),
>> but a small number like 5 is more common. Avoid the ephemeral port range
>> when you make your selection.
>> > Also, we have these ports open to all TCP.  In the spirit of securing
>> > our systems, I guess we could open 4369 only to the IPs of the other
>> > machines in the cluster. Is that a good idea? Can you think of more
>> > firewall restrictions to add?
>> As discussed previously and above, you need to open at least one port in
>> addition to the one used by the port mapper daemon. You are free to add
>> further firewall restrictions, as long as all clusternodes are
>> accessible from all other clusternodes on the relevant ports, as
>> discussed here:
>> http://www.rabbitmq.com/clustering.html#firewall
>> -Emile
> _______________________________________________
> rabbitmq-discuss mailing list
> rabbitmq-discuss at lists.rabbitmq.com
> https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss

'In knowledge is power; in  wisdom, humility.'
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20120316/b054e5be/attachment.htm>

More information about the rabbitmq-discuss mailing list