Chapter 3. Running and administering Rabbit
This chapter covers
- Server management—starting and stopping nodes
- Permission configuration
- Usage statistics
- Troubleshooting problems with RabbitMQ and Erlang
We’ve spent the majority of our time so far on the concepts of AMQP messaging and how to get a basic install of RabbitMQ running. Now we’re ready to more deeply explore what it takes to administer RabbitMQ on a day-to-day basis. Knowing how to get RabbitMQ started on your workstation is one thing, but how do you get it stopped cleanly? How do you limit the amount of RAM it can consume so it doesn’t starve other applications on the same server? These are the kinds of things you’ll run into when it comes time to move RabbitMQ out of development and into production. We’ll use this chapter to show you how to run a top-notch production RabbitMQ environment so you can avoid the big gotchas.
- Some background on how Erlang operates, including those mysterious Erlang cookies
- Controlling user access via RabbitMQ’s permissions system
- Using the command-line tools to view the status of your vhosts, queues, exchanges, and bindings
- What to do when you see scary Erlang error messages like "badrpc,nodedown"
- How to interpret RabbitMQ’s various log files
By the time we’re done, you’ll be a top-notch RabbitMQ admin and ready to tackle your production Rabbit environment. Let’s get started with the basics and dive into how to manage a RabbitMQ server.