[rabbitmq-discuss] Clustering and rabbitmqctl hangs

[David Fooks]

Oops, right I needed the next set of commands:

RABBITMQ_NODE_PORT=5672 RABBITMQ_NODENAME=rabbit1 
RABBITMQ_SERVER_START_ARGS="-rabbitmq_mochiweb listeners 
[{mgmt,[{port,55672}]}]" rabbitmq-server -detached
RABBITMQ_NODE_PORT=5673 RABBITMQ_NODENAME=rabbit2 
RABBITMQ_SERVER_START_ARGS="-rabbitmq_mochiweb listeners 
[{mgmt,[{port,55673}]}]" rabbitmq-server -detached
RABBITMQ_NODE_PORT=5674 RABBITMQ_NODENAME=rabbit3 
RABBITMQ_SERVER_START_ARGS="-rabbitmq_mochiweb listeners 
[{mgmt,[{port,55674}]}]" rabbitmq-server -detached

To set up the monitoring as well!

On Friday, 4 May 2012 14:19:57 UTC+1, David Fooks wrote:
>
> Hi,
>
> I'm seeing the following behaviour when trying to test "A cluster on a 
> single machine" http://www.rabbitmq.com/clustering.html#single-machine
>
> I'm running the following script with sudo:
>
> RABBITMQ_NODE_PORT=5672 RABBITMQ_NODENAME=rabbit1 rabbitmq-server -detached
> RABBITMQ_NODE_PORT=5673 RABBITMQ_NODENAME=rabbit2 rabbitmq-server -detached
> RABBITMQ_NODE_PORT=5674 RABBITMQ_NODENAME=rabbit3 rabbitmq-server -detached
>
> Which outputs:
>
> Activating RabbitMQ plugins ...
> 6 plugins activated:
> * amqp_client-2.8.1
> * mochiweb-1.3-rmq2.8.1-git
> * rabbitmq_management-2.8.1
> * rabbitmq_management_agent-2.8.1
> * rabbitmq_mochiweb-2.8.1
> * webmachine-1.7.0-rmq2.8.1-hg
>
> Activating RabbitMQ plugins ...
> 6 plugins activated:
> * amqp_client-2.8.1
> * mochiweb-1.3-rmq2.8.1-git
> * rabbitmq_management-2.8.1
> * rabbitmq_management_agent-2.8.1
> * rabbitmq_mochiweb-2.8.1
> * webmachine-1.7.0-rmq2.8.1-hg
>
> Activating RabbitMQ plugins ...
> 6 plugins activated:
> * amqp_client-2.8.1
> * mochiweb-1.3-rmq2.8.1-git
> * rabbitmq_management-2.8.1
> * rabbitmq_management_agent-2.8.1
> * rabbitmq_mochiweb-2.8.1
> * webmachine-1.7.0-rmq2.8.1-hg
>
> Ok, looks good. So now I want to check that that all works and I run:
>
> $> sudo rabbitmqctl -n rabbit1 at dfooks-ubuntu64 status
> Status of node 'rabbit1 at dfooks-ubuntu64' ...
> [{pid,9141},
>  {running_applications,
>      [{rabbitmq_management,"RabbitMQ Management Console","2.8.1"},
>       {rabbitmq_management_agent,"RabbitMQ Management Agent","2.8.1"},
>       {amqp_client,"RabbitMQ AMQP Client","2.8.1"},
>       {rabbit,"RabbitMQ","2.8.1"},
>       {os_mon,"CPO  CXC 138 46","2.2.5"},
>       {sasl,"SASL  CXC 138 11","2.1.9.3"},
>       {rabbitmq_mochiweb,"RabbitMQ Mochiweb Embedding","2.8.1"},
>       {webmachine,"webmachine","1.7.0-rmq2.8.1-hg"},
>       {mochiweb,"MochiMedia Web Server","1.3-rmq2.8.1-git"},
>       {inets,"INETS  CXC 138 49","5.5.2"},
>       {mnesia,"MNESIA  CXC 138 12","4.4.17"},
>       {stdlib,"ERTS  CXC 138 10","1.17.3"},
>       {kernel,"ERTS  CXC 138 10","2.14.3"}]},
>  {os,{unix,linux}},
>  {erlang_version,
>      "Erlang R14B02 (erts-5.8.3) [source] [64-bit] [smp:3:3] [rq:3] 
> [async-threads:30] [kernel-poll:true]\n"},
>  {memory,
>      [{total,30671136},
>       {processes,11642648},
>       {processes_used,11633784},
>       {system,19028488},
>       {atom,1339001},
>       {atom_used,1316698},
>       {binary,156016},
>       {code,14610757},
>       {ets,1061320}]},
>  {vm_memory_high_watermark,0.39999999961788246},
>  {vm_memory_limit,418719334},
>  {file_descriptors,
>     
>  [{total_limit,924},{total_used,3},{sockets_limit,829},{sockets_used,1}]},
>  {processes,[{limit,1048576},{used,170}]},
>  {run_queue,0},
>  {uptime,703}]
> ...done.
>
>  Again, good its running. However, if I now try and run
>
> $> sudo rabbitmqctl -n rabbit2 at dfooks-ubuntu64 status
> Status of node 'rabbit2 at dfooks-ubuntu64' ...
>
> Then the command just hangs and I have to ctrl-c. This happens with all of 
> the rabbitmqctrl commands I've tried so far (app_stop, app_start, stop). 
> Anybody got some suggestions?
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20120504/878c5ca5/attachment.htm>