All geek questions in one place

RabbitMQ Management Plugin with Local Cluster

Is there a reason why the rabbitmq management plugin will not work when I use "rabbitmq-multi" to expand a cluster of nodes on my desktop? Or, more precisely, that the control plugin will lead to the failure of this unwinding?

I get Error: {node_start_failed,normal} when rabbitmq-multi starts rabbit_1 @localhost The first node, the rabbit @localhost seems to start well, though.

If I take out the control plugins, all nodes start up (and then the cluster) in order. I think I'm using a fairly recent version of Erlang (5.8 / OTP R14A according to README in my erl5.8.2 folder). I use all the plugins that are listed as necessary on the plugins page , including mochiweb, webmachine, amqp_client, rabbitmq-mochiweb, rabbitmq-management-agent and rabbitmq-management. These plugins are just those plugins.

+4
source share
1 answer

The problem is that rabbitmq-multi only assigns serial ports for AMQP, not HTTP (or STOMP or AMQPS or anything else that a broker can open). Therefore, each node tries to listen on the same port for the management plugin, and only the first ones succeed. rabbitmq-multi will be leaving in the next release; this is one of the reasons.

I think you will want to start the nodes without using rabbitmq-multi, just with a few calls to the rabbitmq server, using environment variables to configure each node differently. I am using a script like:

Start- node.sh:

 #!/bin/sh RABBITMQ_NODE_PORT=$1 RABBITMQ_NODENAME=$2 \ RABBITMQ_MNESIA_DIR=/tmp/rabbitmq-$2-mnesia \ RABBITMQ_PLUGINS_EXPAND_DIR=/tmp/rabbitmq-$2-plugins-scratch \ RABBITMQ_LOG_BASE=/tmp \ RABBITMQ_SERVER_START_ARGS="-rabbit_mochiweb port 5$1" \ /path/to/rabbitmq-server -detached

and then call it like

 start-node.sh 5672 rabbit start-node.sh 5673 hare
+2
source

Source: https://habr.com/ru/post/1340909/

More articles:


All Articles