Running RabbitMQ 2.6 and 2.7 on Mac OS/X

AMQP is an open protocol for Asynchronous message queueing.  The number one implementation for AMQP is RabbitMQ.
 
I normally run RabbitMQ on my Mac in a Linux/Ubuntu VM  but I recently got a new Macbook Air that's limited to 4GB.  I wanted to run RabbitMQ native on the Macbook Air instead of the Linux virtual machine to save space and give me better performance when running tcServer, RabbitMQ and STS on this slightly smaller machine. 

Installation
RabbitMQ is written in Erlang.  The Mac doesn't come with Erlang so you have to install it. You can use Macports or Homebrew per the Rabbit installation instructions.  I'm lazy so I used Rudix  Erlang-Solutions which provides Erlang in neat Mac installation packages that put the files in /usr/local /usr/bin. (The rudix version of Erlang went away over the weekend of 11/12/2011). 
  1. Download the img/package mentioned above and install it like any other .img file.
  2. Download RabbitMQ and unpack it into some working directory.
  3. cd into the RabbitMQ sbin directory.
  4. Start the server with sudo ./rabbitmq-server
  5. Use the sudo sbin/rabbitmqctl status command to see the status of the broker.
You now have a running RabbitMQ broker with only administrative exchanges and no queues configured.  You should now stop that server if you want to install the optional Web Management console or any other plugin.

Web Management Console
The web management console makes troubleshooting and experimentation easier. The steps for configuring plugins differ based on the version. 

Users access the web management console using URL http://localhost:55672/mgmt/. The default username and password are guest/guest. The console uses JavaScript so make sure you have JavaScript enabled for that web site.

Rabbit 2.6 
The plugins must be manually downloaded and installed in Rabbit 2.6
  1. Download the RabbitMQ management console components from the plugins page.  Download the plugins and copy them into RabbitMQ the plugins directory. Each of the plugins has a .ez file extension. The console plug-in requires 6 components at the time of this blog posting.
  2. Restart the RabbitMQ server. You should see the plugins load in the console output.
  3. Connect to the management console with a web browser and log in.
Rabbit 2.7 
The plugins are installed but not enabled for RabbitMQ 2.7.  You manually enable plugins with the new sbin/rabbitmq-plugins command.  First bring down your RabbitMQ server you started above.
  1. Create the location where the config file will be generated sudo mkdir /etc/rabbitmq
  2. cd into <rabbitmq_home>/sbin
  3. run sudo ./rabbitmq-plugins enable rabbitmq_management to create the config file and add this plugin. Note that no plug-in version numbers are specified. You should see that it adds all of the necessary dependencies.  A core dump probably means you forgot to use "sudo"
  4. Start the RabbitMQ server as you did in the previous steps.
  5. Connect to the management console with a web browser and log in.

Conclusion
You should now have a running server with the optional web console configured and loaded.  Use the previous section as a guide if you want to add additional plug-ins.  See the Rabbit tutorials for examples on how you can use the RabbitMQ server configured above.



Comments

Post a Comment

Popular posts from this blog

Installing the RNDIS driver on Windows 11 to use USB Raspberry Pi as network attached

Image
I do a lot of my development and configuration via ssh into my Raspberry Pi Zero over the RNDIS connection. Some models of the Raspberry PIs can be configured with  gadget drivers  that let the Raspberry pi emulate different devices when plugged into computers via USB. My favorite gadget  is the network profile that makes a Raspberry Pi look like an RNDIS-attached network device.  All types of network services travel over an RNDIS device without knowing it is a USB hardware connection. A Raspberry Pi shows up as a Remote NDIS (RNDIS) device when you plug the Pi into a PC or Mac via a USB cable. The gadget  in the Windows Device Manager picture shows this RNDIS Gadget connectivity between a Windows machine and a Raspberry Pi. The Problem Windows 11 and Windows 10 no longer auto-installs the RNDIS driver that makes magic happen. Windows recognizes that the Raspberry Pi is some type of generic USB COM device. Manually running W indows Update  or  Upd...
Read more

Understanding your WSL2 RAM and swap - Changing the default 50%-25%

Image
The Windows Subsystem for Linux operates as a virtual machine that can dynamically grow the amount of RAM to a maximum set at startup time.  Microsoft sets a default maximum RAM available to 50% of the physical memory and a swap-space that is 1/4 of the maximum WSL RAM.  You can scale those numbers up or down to allocate more or less RAM to the Linux instance. The first drawing shows the default WSL memory and swap space sizing. The images below show a developer machine that is running a dev environment in WSL2 and Docker Desktop.  Docker Desktop has two of its own WSL modules that need to be accounted for.  You can see that the memory would actually be oversubscribed, 3 x 50% if every VM used its maximum memory.  The actual amount of memory used is significantly smaller allowing every piece to fit. Click to Enlarge The second drawing shows the memory allocation on my 64GB laptop. WSL Linux defaul...
Read more

Almost PaaS Document Parsing with Tika and AWS Elastic Beanstalk

Image
The Apache Tika project provides a  library capable of parsing and extracting data and meta data from over 1000 file types.  Tika is available as a single jar file that can be included inside applications or as a deployable jar file that runs Tika as a standalone service. This blog describes deploying the Tika jar as an auto-scale service in Amazon AWS Elastic Beanstalk.  I selected Elastic Beanstalk because it supports jar based deployments without any real Infrastructure configuration. Elastic Beanstalk auto-scale should take care of scaling up and down for for the number of requests you get. Tika parses documents and extracts their text completely in memory. Tika was deployed for this blog using EC2 t2.micro instances available in the AWS free tier. t2.micro VMs are 1GB which means that you are restricted in document complexity and size. You would size your instances appropriately for your largest documents.   Preconditions An AWS account. AWS ac...
Read more