Installing on Mac
This package requires OpenSSL 1.0.x installed. We strongly recommend doing this via Homebrew to avoid possible issues with dynamic library paths.
Installation with Homebrew
Possibly the easiest way to use this package is via Homebrew. It will automatically install the OpenSSL formula mentioned above:
brew install rabbitmq
Run RabbitMQ Server
Unlike some other installation methods, namely the Debian and RPM packages, RabbitMQ generic UNIX binary build does not require sudo. It can be uncompressed into any location and started and managed using the tools under sbin. Default data directory location will be under ./var, that is, in the installation directory.
Start the Server
To start the server, run the sbin/rabbitmq-server script. This displays a short banner message, concluding with the message "completed with [n] plugins.", indicating that the RabbitMQ broker has been started successfully.
To start the server in "detached" mode, use rabbitmq-server -detached. This will run the node process in the background.
Configure the Server
It is possible to customise the RabbitMQ environment by setting environment variables in $RABBITMQ_HOME/etc/rabbitmq/rabbitmq-env.conf. Server components may be configured, too, in the RabbitMQ configuration file located at $RABBITMQ_HOME/etc/rabbitmq/rabbitmq.config. Neither of these files exist after installation.
The Generic Unix tarball is designed as far as possible to run without requiring configuration changes or special permissions. The directories and files used by default are all held under the installation directory rabbitmq_server-3.7.7 which is in the $RABBITMQ_HOME variable in the scripts.
Should you wish to install RabbitMQ Server such that it uses the conventional system directories for configuration, database, log files, plugins etc, it is possible to do this.
Find the line:
in the sbin/rabbitmq-defaults script and change this line to:
but do not modify any other line in this script.
Note: After this modification the default directory locations may require different permissions. In particular RABBITMQ_MNESIA_BASE and RABBITMQ_LOG_BASE may need to be created (the server will attempt to create them at startup), and the RABBITMQ_ENABLED_PLUGINS_FILE will need to be writable (for rabbitmq-plugins). The configuration files will be looked for in /etc/rabbitmq/.
Default user access
The broker creates a user guest with password guest. Unconfigured clients will in general use these credentials. By default, these credentials can only be used when connecting to the broker as localhost so you will need to take action before connecting from any other machine.
See the documentation on access control for information on how to create more users, delete the guest user, or allow remote access to the guest user.
Managing the Broker
To stop the server or check its status, etc., you can invoke sbin/rabbitmqctl (as the user running rabbitmq-server). All rabbitmqctl commands will report the node absence if no broker is running.
to start server:
Invoke rabbitmqctl stop to stop the server.
Invoke rabbitmqctl status to check whether it is running.