If RabbitMQ is deployed on a standalone machine or in a high availability configuration
with multiple nodes, you must use an adapted procedure to upgrade RabbitMQ to version 3.11.5 or
later, as applicable.
Before you begin
This procedure is specific to the deployment of RabbitMQ by the Genetec Mission Control™
installer. For external deployment of RabbitMQ with third-party solutions, refer to the
third-party documentation as deployment process may differ.
Refer the Upgrading
RabbitMQ article to understand the deployment process.
Refer the RabbitMQ Clustering Guide to see how .erlang
cookie paths are constructed.
Copy the Mission Control 3.1.3.0
installation package to all RabbitMQ servers.
What you should know
Before you upgrade your RabbitMQ,
validate
your existing RabbitMQ configuration.
Procedure
-
Stop the RabbitMQ service.
-
Back up the .erlang.cookie file to a temporary storage
location.
Usual file path for the .erlang.cookie is
C:\Windows\ServiceProfiles\LocalService.
-
Paste the .erlang.cookie file from the temporary storage location
to the following folders:
- C:\
- C:\Users\<username>\
- C:\Windows\System32\config\systemprofile
NOTE: If an .erlang.cookie file exists in the destination folder,
overwrite it with the copied file.
-
If using your own certificates in C:\Program Files
(x86)\Genetec\RabbitMQ, you must create a backup for them as well.
-
Use the advanced setup in the Mission Control 3.1.3.0
installation wizard to upgrade RabbitMQ.
-
Restart the RabbitMQ
service.