|Packaged as .deb for Debian-based Linux||rabbitmq-server_3.4.0-1_all.deb||(Signature)|
rabbitmq-server is included in Debian since 6.0 (squeeze) and in Ubuntu since 9.04. However, the versions included are often quite old. You will probably get better results installing the .deb from our website. Check the Debian package and Ubuntu package details for which version of the server is available for which versions of the distribution.
You can either download it with the link above and install with dpkg, or use our APT repository (see below).
All dependencies should be met automatically.
The server is started as a daemon by default when the RabbitMQ server package is installed.
As an administrator, start and stop the server as usual for Debian using invoke-rc.d rabbitmq-server stop/start/etc.
Note: The server is set up to run as system user rabbitmq. If you change the location of the Mnesia database or the logs, you must ensure the files are owned by this user (and also update the environment variables).
To use our APT repository:
deb http://www.rabbitmq.com/debian/ testing main(Please note that the word testing in this line refers to the state of our release of RabbitMQ, not any particular Debian distribution. You can use it with Debian stable, testing or unstable, as well as with Ubuntu. We describe the release as "testing" to emphasise that we release somewhat frequently.)
wget http://www.rabbitmq.com/rabbitmq-signing-key-public.asc sudo apt-key add rabbitmq-signing-key-public.asc
sudo apt-get install rabbitmq-server
To adjust system limits (in particular the number of open file handles), edit the file /etc/default/rabbitmq-server to invoke ulimit when the service is started, for example:
ulimit -n 1024
will set the maximum number of file open handles for the service process to 1024 (the default).
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 fromn 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.
To stop the server or check its status, etc., you can invoke rabbitmqctl (as an administrator). It should be available on the path. All rabbitmqctl commands will report the node absence if no broker is running.
More info on rabbitmqctl.
Output from the server is sent to a RABBITMQ_NODENAME.log file in the RABBITMQ_LOG_BASE directory. Additional log data is written to RABBITMQ_NODENAME-sasl.log.
The broker always appends to the log files, so a complete log history is retained.
You can use the logrotate program to do all necessary rotation and compression, and you can change it. By default, this script runs weekly on files located in default /var/log/rabbitmq directory. See /etc/logrotate.d/rabbitmq-server to configure logrotate.