Setup Rabbitmq cluster on single instance with different port

[dipika patil]

Hi 

I am new to RabbitMQ.I have installed RabbitMQ from installation guide

https://www.rabbitmq.com/install-debian.html. and RabbiMQ server with deb file.

and also setup cluster on single machine with different port with below steps

sudo RABBITMQ_NODE_PORT=5672 RABBITMQ_NODENAME=rabbit rabbitmq-server -detached  // this step I have not executed because my RabbitMQ service is running on this port.

sudo RABBITMQ_NODE_PORT=5673 RABBITMQ_NODENAME=rabbit1 rabbitmq-server -detached

sudo RABBITMQ_NODE_PORT=5674 RABBITMQ_NODENAME=rabbit2 rabbitmq-server -detached

sudo RABBITMQ_NODE_PORT=5673 RABBITMQ_SERVER_START_ARGS="-rabbitmq_management listener [{port,15673}]" RABBITMQ_NODENAME=rabbit1 rabbitmq-server -detached

sudo RABBITMQ_NODE_PORT=5674 RABBITMQ_SERVER_START_ARGS="-rabbitmq_management listener [{port,15674}]" RABBITMQ_NODENAME=rabbit2 rabbitmq-server -detached

sudo rabbitmqctl -n rabbit1 stop_app

sudo rabbitmqctl -n rabbit2 stop_app

sudo rabbitmqctl -n rabbit1 join_cluster rabbit@`hostname -s

sudo rabbitmqctl -n rabbit2 join_cluster rabbit@`hostname -s`

sudo rabbitmqctl -n rabbit1 start_app

sudo rabbitmqctl -n rabbit2 start_app

This steps I follow and my cluster is ready in UI I can see 3 services running with rabbit,rabbit1,rabbit2.

but when I reboot my instance my rabbitMQ server will start with sudo service rabbitmq-server start but for cluster will not start 

sudo RABBITMQ_NODE_PORT=5673 RABBITMQ_SERVER_START_ARGS="-rabbitmq_management listener [{port,15673}]" RABBITMQ_NODENAME=rabbit1 rabbitmq-server -detached

sudo RABBITMQ_NODE_PORT=5674 RABBITMQ_SERVER_START_ARGS="-rabbitmq_management listener [{port,15674}]" RABBITMQ_NODENAME=rabbit2 rabbitmq-server -detached

this command I have to fire again  why this is happing or rabbitMQ behavior is like that only?

Please help me on this

Thank in advance.

 

[Luke Bakken]

Hello,

RabbitMQ is working as intended. Configuring a cluster to run on the same machine isn't recommended so the only way to do it is via manually starting the service like you see.

You can add the commands to start additional nodes on the same machine to the system startup process but, again, running a cluster for anything but development purposes isn't recommended.

Thanks,

Luke