|Installer for Windows systems (from rabbitmq.com)||rabbitmq-server-3.5.3.exe||(Signature)|
|Installer for Windows systems (from github.com)||rabbitmq-server-3.5.3.exe||(Signature)|
If you have an existing installation and are planning to upgrade the Erlang VM from a 32bit to a 64bit version then you must uninstall the broker before upgrading the VM. The installer will not be able to stop or remove a service that was installed with an Erlang VM of a different architecture.
Firstly, download and run the Erlang Windows Binary File. It takes around 5 minutes.
Then just run the installer, rabbitmq-server-3.5.3.exe. It takes around 2 minutes, and will set RabbitMQ up and running as a service, with a default configuration.
The RabbitMQ service starts automatically. You can stop/reinstall/start the RabbitMQ service from the Start Menu.
You can find links to RabbitMQ directories in the Start Menu.
There is also a link to a command prompt window that will start in the sbin dir, in the Start Menu. This is the most convenient way to run the various command line tools.
Firewalls and other security tools may prevent RabbitMQ from binding to a port. When that happens, RabbitMQ will fail to start. Make sure the following ports can be opened:
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 broker or check its status, use rabbitmqctl.bat in sbin (as an administrator).
Use rabbitmqctl stop.
Use rabbitmqctl status. All rabbitmqctl commands will report the node absence if no broker is running (i.e. nodedown).
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 rotate logs using rabbitmqctl rotate_logs.
In the event that the Erlang VM crashes whilst RabbitMQ is running as a service, rather than writing the crash dump to the current directory (which doesn't make sense for a service) it is written to an erl_crash.dump file in the base directory of the RabbitMQ server (set by the RABBITMQ_BASE environment variable, defaulting to %APPDATA%\%RABBITMQ_SERVICENAME% - typically %APPDATA%\RabbitMQ otherwise).
We aim to make RabbitMQ a first-class citizen on Windows. However, sometimes there are circumstances beyond our control. Please consult the Windows-specific Issues page.
If you have questions or need help, feel free to ask on RabbitMQ mailing list.