I am following "A cluster on a single machine" explained in https://www.rabbitmq.com/clustering.html but it is not working as it is. I am using ubuntu 14.04 64 bit.
root@sunny-workstation:~# RABBITMQ_NODE_PORT=5673 RABBITMQ_SERVER_START_ARGS="-
rabbitmq_management listener [{port,15673}]" RABBITMQ_NODENAME=hare rabbitmq-server &
[1] 17990
root@sunny-workstation:~#
RabbitMQ 3.2.4. Copyright (C) 2007-2013 GoPivotal, Inc.
## ## Licensed under the MPL. See http://www.rabbitmq.com/
## ##
########## Logs: /var/log/rabbitmq/hare.log
###### ## /var/log/rabbitmq/hare-sasl.log
##########
Starting broker...
BOOT FAILED
===========
Error description:
{could_not_start,rabbitmq_stomp,
{{shutdown,
{failed_to_start_child,'rabbit_stomp_listener_sup_:::61613',
{shutdown,
{failed_to_start_child,tcp_listener,
{cannot_listen,{0,0,0,0,0,0,0,0},61613,eaddrinuse}}}}},
{rabbit_stomp,start,[normal,[]]}}}
Above error indicates that 61613 address already in use. Stomp is listening on 61613 port. I am exploring how to change/define stomp listener port while creating a new node. Please help if somebody already know solution.
I never tried it, but have you tried to set
RABBITMQ_CONFIG_FILE
and set the configurations into different files?I run into the same problem, but the proposed solution only partly solved my problem. After having solved the stomp issue, the next one was mqtt :-( But figuring that one out wasn't too hard :-) First server started without parameters:
Second server started with modified parameters:
It seems the more plugins are added to RabbitMQ the more issues you will run into when starting it on a single machine. So with the next release you might have to add some more args
Thanks Matthlas from RabbitMQ. It works like a dream with following commands.