[rabbitmq-discuss] RMQ-3.0.0 multi rabbit nodes not able to start .

[Tim Watson]

Hi

On 12/04/2012 10:50 AM, ponmuthu wrote:
> Its working fine . but is ther any way to get all nodes in same
> mgnt plugin ?

Let's just make sure we're answering your question properly. It sounds 
like you are running a cluster on a single machine. In this scenario, 
the management plugin can either

1. run on all nodes on a different port
2. run on one node only

Using *either* of these approaches, you should still be able to see all 
three nodes in the management ui, *as long as they are clustered 
together* !!!

If you are doing (1) then as I showed you, the 
RABBITMQ_SERVER_START_ARGS needs to use '-rabbitmq_management listener 
[{port, ?}]' where the port is different for each node. That should work 
just fine and all three nodes will have a listener running on a 
different port.

If you just want to run management on one of your nodes and not the 
other two then you can do this by pointing to a different 
RABBITMQ_ENABLED_PLUGINS_FILE for the node on which you want to run 
management and enabling the plugin on *only* that node by running 
`RABBITMQ_ENABLED_PLUGINS_FILE=/path/to/the/file rabbitmq-plugins enable 
rabbitmq_management` and restarting just that rabbit. This will enable 
management on *one node only* but as long as the other nodes are 
*clustered* then they will all appear in the UI.

Does that make sense? Sorry if I misunderstood your question at first. :-)

> -----Original Message-----
> From: Tim Watson [mailto:tim at rabbitmq.com]
> Sent: Tuesday, December 04, 2012 4:06 PM
> To: Discussions about RabbitMQ
> Cc: PONMUTHU M
> Subject: Re: [rabbitmq-discuss] RMQ-3.0.0 multi rabbit nodes not
> able to start .
>
> On 12/04/2012 10:40 AM, PONMUTHU M wrote:
>> but after changing port 15673 which is free in my box , also
> not able
>> to start its picking 15672
>>
>> i want to know . from where its picking ?
> Use
>
> RABBITMQ_SERVER_START_ARGS="-rabbitmq_management listener
> [{port,15673}]"
>
> instead
>
>
>> RABBITMQ_NODENAME=$1 \
>> RABBITMQ_NODE_PORT=$2 \
>> RABBITMQ_MNESIA_DIR=/tmp/rabbitmq-$1-mnesia \
>> RABBITMQ_PLUGINS_EXPAND_DIR=/tmp/rabbitmq-$1-plugins-scratch \
>> RABBITMQ_LOG_BASE=/tmp \
>> RABBITMQ_SERVER_START_ARGS="-rabbitmq_mochiweb listeners
>> [{mgmt,[{port,15673}]}]" \ ${RMQ_ROOT_PATH}rabbitmq-server&   #
>> -detached
>>
>>
>> BOOT FAILED
>> ===========
>>
>> Error description:
>>      {could_not_start,rabbitmq_management,
>>
>> {could_not_start_listener,[{port,15672}],eaddrinuse}}
>>
>> Log files (may contain more information):
>>      /tmp/pon1.log
>>      /tmp/pon1-sasl.log
>>
>> {"init terminating in
>>
> do_boot",{rabbit,failure_during_boot,{could_not_start,rabbitmq_m
> anagem
>> ent,{could_not_start_listener,[{port,15672}],eaddrinuse}}}}
>>
>> Crash dump was written to: erl_crash.dump init terminating in
> do_boot
>> ()
>>
>>
>>
>>
>> --
>> View this message in context:
>>
> http://rabbitmq.1065348.n5.nabble.com/RMQ-3-0-0-multi-rabbit-nod
> es-not
>> -able-to-start-tp23817p23820.html Sent from the RabbitMQ
> mailing list
>> archive at Nabble.com.
>> _______________________________________________
>> rabbitmq-discuss mailing list
>> rabbitmq-discuss at lists.rabbitmq.com
>>
> https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-dis
> cuss
>
>