Back to Home

Start the Server

sudo /etc/init.d/rabbitmq-server start
Starting rabbitmq-server: FAILED - check /var/log/rabbitmq/startup_{log, _err}

Note: the suse service may have issues

Admin Cmds

the standard commands:

rabbitmqctl       rabbitmq-plugins  rabbitmq-server   

Star the server

 /usr/sbin/rabbitmqctl start_app

rabbitmq-plugin mgt

rabbitmq@linux-5mi7:~> /usr/sbin/rabbitmq-plugins list
[e] amqp_client                       3.2.2
[ ] cowboy                            0.5.0-rmq3.2.2-git4b93c2d
[ ] eldap                             3.2.2-gite309de4
[e] mochiweb                          2.7.0-rmq3.2.2-git680dba8
[ ] rabbitmq_amqp1_0                  3.2.2
[ ] rabbitmq_auth_backend_ldap        3.2.2
[ ] rabbitmq_auth_mechanism_ssl       3.2.2
[ ] rabbitmq_consistent_hash_exchange 3.2.2
[E] rabbitmq_federation               3.2.2
[E] rabbitmq_federation_management    3.2.2
[ ] rabbitmq_jsonrpc                  3.2.2
[ ] rabbitmq_jsonrpc_channel          3.2.2
[ ] rabbitmq_jsonrpc_channel_examples 3.2.2
[E] rabbitmq_management               3.2.2
[e] rabbitmq_management_agent         3.2.2
[ ] rabbitmq_management_visualiser    3.2.2
[ ] rabbitmq_mqtt                     3.2.2
[ ] rabbitmq_shovel                   3.2.2
[ ] rabbitmq_shovel_management        3.2.2
[ ] rabbitmq_stomp                    3.2.2
[ ] rabbitmq_tracing                  3.2.2
[e] rabbitmq_web_dispatch             3.2.2
[ ] rabbitmq_web_stomp                3.2.2
[ ] rabbitmq_web_stomp_examples       3.2.2
[ ] rfc4627_jsonrpc                   3.2.2-git5e67120
[ ] sockjs                            0.3.4-rmq3.2.2-git3132eb9
[e] webmachine                        1.10.3-rmq3.2.2-gite9359c7

Where *E* is enabled

RabbitMq Managment Console

Installing the console:

Starting the console:

http://localhost:55672 & login via default user and password which is guest:guest & you will be able to see it all.

Securing the console:

Command line mgt

Clustering and High Availability

Rabbit supports various types of Clustering and HA.

Clustering This will be resilient to the loss of individual nodes in terms of the overall availability of service, however in rabbit queues and their messages can be lost on simple clustering. This is because a queue and its contents reside on exactly one node, thus the loss of a node will render its queues unavailable.

Rabbit also supports an active/passive pair with clustering meaning the passive node will take over with no loss of messages

Mirroring allows active/active high availability for queues. This works by allowing queues to be mirrored on other nodes within a RabbitMQ cluster.

Mirroring is setup using the policy command:

Policies can be used to configure the

  • federation plugin
rabbitmq-plugins enable rabbitmq_federation
rabbitmq-plugins enable rabbitmq_federation_management
rabbitmqctl set_policy federate-me "^amq\." '{"federation-upstream-set":"all"}' --priority 1 --apply-to exchanges

This can also be done via the web mgt console:

Navigate to Admin > Policies > Add / update a policy.
Enter "federate-me" next to Name, "^amq\." next to Pattern, and select "Exchanges" next to Apply to.
Enter "federation-upstream-set" = "all" in the first line next to Policy.
Click Add policy.
  • mirrored queues.

Policy where queues whose names begin with “ha.” are mirrored to all nodes in the cluster:

rabbitmqctl set_policy ha-all "^ha\." '{"ha-mode":"all"}'

or from the web console:

Navigate to Admin > Federation Upstreams > Add a new upstream. 
Enter "my-upstream" next to Name, "amqp://server-name" next to URI, and 36000000 next to Expiry. 
Click Add upstream.
  • alternate exchanges
  • dead lettering
  • per-queue TTLs
  • maximum queue length.
rabbitmq.txt · Last modified: 2014/03/23 05:12 by root
RSS - 200 © CrosswireDigitialMedia Ltd