Upgrading RabbitMQ - Mission Control 3.2.0.0 | Mission Control Web API 2.10

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.12.1 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.

NOTE: RabbitMQ 3.12.1 requires all previously existing feature flags to be enabled before the upgrade. The upgrade will fail if you miss this step.

Refer the RabbitMQ Clustering Guide to see how .erlang cookie paths are constructed.

Copy the Mission Control 3.2.0.0 installation package to all RabbitMQ servers.

Tip: It is recommended to use a 3-node cluster for high availability. For details, see Configuring high availability for RabbitMQ in the Genetec Mission Control™ Deployment Guide .

What you should know

Before you upgrade your RabbitMQ, validate your existing RabbitMQ configuration.

Procedure

Enable feature flags by any of the below methods:
- RabbitMQ web portal
  1. Open the RabbitMQ web portal (https://localhost:15671)
  2. In the Admin tab click on Feature Flags.
  3. Enable all feature flags and close the RabbitMQ web portal.
- RabbitMQ Command Prompt
  1. Open the RabbitMQ Command Prompt(sbin dir) and run this command:
    Code
    rabbitmqctl.bat enable_feature_flag all
If you are upgrading from RabbitMQ 3.9.x or an earlier version , run the RabbitMQ 3.11.5 standalone installer from the GTAP Product Download page and enable all its feature flags by repeating Step 1. If you are upgrading from RabbitMQ version 3.11.15 continue with the below steps.
Enable all feature flags for Rabbit
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.2.0.0 installation wizard to upgrade RabbitMQ.
Restart the RabbitMQ service.