[rabbitmq-discuss] Initial cluster set-up questoin

Wed Dec 14 10:31:55 GMT 2011

> I createdthe  /etc/rabbitmq/rabbitmq-env.conf with this content:
> 
> [{rabbit, [{cluster_nodes, ['rabbit at iuu-app007', 'rabbit at iuu-app008']}]}].
> 
> /etc/rabbitmq/rabbitmq-env.conf: line 1: [{rabbit,: command not found
> Cluster status of node 'rabbit at iuu-app008' ...
> [{nodes,[{disc,['rabbit at iuu-app008','rabbit at iuu-app007']}]},
>  {running_nodes,['rabbit at iuu-app007','rabbit at iuu-app008']}]
> ...done.
> 
> The syntax of the file looks fine to us, and also according to the
> documentation. :~(
> 
> 1) Is the syntax correct?

Yes, but it's in the wrong file.  That should go in
  /etc/rabbitmq/rabbitmq.config

> 2) Should the rabbitmq-env.conf be placed on both nodes?

You should set that parameter in rabbitmq.config on both nodes.

Cheers,
Alex

On Wed, Dec 14, 2011 at 11:12:45AM +0100, Simon Loewenthal/NL/Tele2 wrote:
> On 14/12/11 09:47, Simon Loewenthal/NL/Tele2 wrote:
> > 	
> >
> > Hi,
> >
> > 	I have installed Rabbit & Erlang and followed these instruction
> > http://www.rabbitmq.com/clustering.html to set-up a two node cluster.
> > Both nodes are be started, but when node 2 attempts to join node 1 it
> > fails.
> >
> > There are no firewalls between each other. Both are on the same vlan and
> > a /22 subnet.
> >
> > O/S: RHEL 6.2  Fully patched from RHN.
> >
> > Node 1:
> >
> > # rabbitmq-server --detached
> > Activating RabbitMQ plugins ...
> > 6 plugins activated:
> > * amqp_client-2.7.0
> > * mochiweb-1.3-rmq2.7.0-git
> > * rabbitmq_management-2.7.0
> > * rabbitmq_management_agent-2.7.0
> > * rabbitmq_mochiweb-2.7.0
> > * webmachine-1.7.0-rmq2.7.0-hg
> >
> > ** Found 0 name clashes in code paths
> >
> > +---+   +---+
> > |   |   |   |
> > |   |   |   |
> > |   |   |   |
> > |   +---+   +-------+
> > |                   |
> > | RabbitMQ  +---+   |
> > |           |   |   |
> > |   v2.7.0  +---+   |
> > |                   |
> > +-------------------+
> > AMQP 0-9-1 / 0-9 / 0-8
> > Copyright (C) 2007-2011 VMware, Inc.
> > Licensed under the MPL.  See http://www.rabbitmq.com/
> >
> > node           : rabbit at iuu-app007
> > app descriptor :
> > /usr/lib/rabbitmq/lib/rabbitmq_server-2.7.0/sbin/../ebin/rabbit.app
> > home dir       : /var/lib/rabbitmq
> > config file(s) : (none)
> > cookie hash    : Fm+somLGFoQYy1H+2FUteQ==
> > log            : /var/log/rabbitmq/rabbit at iuu-app007.log
> > sasl log       : /var/log/rabbitmq/rabbit at iuu-app007-sasl.log
> > database dir   : /var/lib/rabbitmq/mnesia/rabbit at iuu-app007
> > erlang version : 5.8.5
> >
> > -- rabbit boot start
> > starting file handle cache server
> > ...done
> > starting worker pool
> > ...done
> > starting database
> > ...done
> > starting codec correctness check
> > ...done
> > -- external infrastructure ready
> > starting statistics event manager
> > ...done
> > starting logging server
> > ...done
> > starting plugin registry
> > ...done
> > starting auth mechanism amqplain
> > ...done
> > starting auth mechanism cr-demo
> > ...done
> > starting auth mechanism plain
> > ...done
> > starting exchange type direct
> > ...done
> > starting exchange type fanout
> > ...done
> > starting exchange type headers
> > ...done
> > starting exchange type topic
> > ...done
> > -- kernel ready
> > starting node monitor
> > ...done
> > starting cluster delegate
> > ...done
> > starting guid generator
> > ...done
> > starting alarm handler
> > ...done
> > starting memory monitor
> > ...done
> > -- core initialized
> > starting empty DB check
> > ...done
> > starting management agent
> > ...done
> > starting exchange, queue and binding recovery
> > ...done
> > starting mirror queue slave sup
> > ...done
> > starting adding mirrors to queues
> > ...done
> > -- message delivery logic ready
> > starting error log relay
> > ...done
> > starting networking
> > ...done
> > starting notify cluster nodes
> > ...done
> > starting direct_client
> > ...done
> >
> > broker running
> >
> >
> >
> > # rabbitmqctl cluster_status
> > Cluster status of node 'rabbit at iuu-app007' ...
> > [{nodes,[{disc,['rabbit at iuu-app007']}]},{running_nodes,['rabbit at iuu-app007']}]
> > ...done.
> >
> >
> > Node 2:
> > # rabbitmq-server --detached
> > Activating RabbitMQ plugins ...
> > 6 plugins activated:
> > * amqp_client-2.7.0
> > * mochiweb-1.3-rmq2.7.0-git
> > * rabbitmq_management-2.7.0
> > * rabbitmq_management_agent-2.7.0
> > * rabbitmq_mochiweb-2.7.0
> > * webmachine-1.7.0-rmq2.7.0-hg
> >
> > ** Found 0 name clashes in code paths
> > [SNIP]
> > node           : rabbit at iuu-app008
> > app descriptor :
> > /usr/lib/rabbitmq/lib/rabbitmq_server-2.7.0/sbin/../ebin/rabbit.app
> > home dir       : /var/lib/rabbitmq
> > config file(s) : (none)
> > cookie hash    : VOYILJRa2vmMlRly95DYQw==
> > log            : /var/log/rabbitmq/rabbit at iuu-app008.log
> > sasl log       : /var/log/rabbitmq/rabbit at iuu-app008-sasl.log
> > database dir   : /var/lib/rabbitmq/mnesia/rabbit at iuu-app008
> > erlang version : 5.8.5
> > [SNIP]
> > broker running
> > Erlang has closed
> >
> > # rabbitmqctl stop_app
> > Stopping node 'rabbit at iuu-app008' ...
> > ...done.
> > [root at iuu-app008 ~]# rabbitmqctl reset
> > Resetting node 'rabbit at iuu-app008' ...
> > ...done.
> >
> > # rabbitmqctl cluster rabbit at iuu-app007
> > Clustering node 'rabbit at iuu-app008' with ['rabbit at iuu-app007'] ...
> > Error:
> > {no_running_cluster_nodes,['rabbit at iuu-app007'],['rabbit at iuu-app007']}
> >
> > I have tried the command above with the FQDN and had the same error
> > returned.
> >
> >
> > Any ideas where I could look?
> >
> > Simon.
> >
> Hi,
> 
>     Problem solved by copying the Erlang cookie from Node 1 onto Node 2.
> Successfully joined two nodes in a disc cluster.
> 
> 
> I createdthe  /etc/rabbitmq/rabbitmq-env.conf with this content:
> 
> [{rabbit, [{cluster_nodes, ['rabbit at iuu-app007', 'rabbit at iuu-app008']}]}].
> 
> #  rabbitmqctl cluster_status
> /etc/rabbitmq/rabbitmq-env.conf: line 1: [{rabbit,: command not found
> Cluster status of node 'rabbit at iuu-app008' ...
> [{nodes,[{disc,['rabbit at iuu-app008','rabbit at iuu-app007']}]},
>  {running_nodes,['rabbit at iuu-app007','rabbit at iuu-app008']}]
> ...done.
> 
> The syntax of the file looks fine to us, and also according to the
> documentation. :~(
> 
> 1) Is the syntax correct?
> 2) Should the rabbitmq-env.conf be placed on both nodes?
> 
> Regards, S.
> 
> -- 
> Simon Loewenthal/Tele2
> GSM: +31 6 2000 5427
> 
> ******** IMPORTANT NOTICE ********
> This e-mail (including any attachments) may contain information 
> that is confidential or otherwise protected from disclosure and
> it is intended only for the addressees. If you are not the intended
> recipient, please kindly refrain from copying or distribution.
> Other use of information contained in this e-mail (and its attachments)
> is frowned upon. If you have received this e-mail in error, kindly
> notify us immediately by telephone or e-mail and, if possible, kindly
> delete the message (including any attachments) from your system. Of
> course, this is not legal advice, nor is it a contract. If it were a
> contract, it would have an exchange of value and affirmative agreement
> by both parties. If it were legal advice, it should be written by a
> lawyer and would have a bill attached.
> 
> It ought to be obvious my views in this Email might not represent my
> employer's views, & vice-verse. Please note that e-mail messages may
> contain computer viruses or other defects. I presume that you understand
> the concept of a computer virus, and took reasonable precautions.
> 
> _______________________________________________
> rabbitmq-discuss mailing list
> rabbitmq-discuss at lists.rabbitmq.com
> https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss