Upgrading RabbitMQ - Mission Control | Mission Control Web API 2.6

Genetec Mission Control™ Release Notes

Applies to
Mission Control | Mission Control Web API 2.6
Last updated
Content type
Release notes
Genetec Mission Control™
Release notes

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

To see how .erlang cookie paths are constructed, see the RabbitMQ Clustering Guide

Copy the Mission Control 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.


  1. Stop the RabbitMQ service.
  2. Backup the .erlang.cookie file to a temporary storage location.
    Usual file path for the .erlang.cookie is C:\Windows\ServiceProfiles\LocalService.
  3. 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.
  4. If using your own certificates in C:\Program Files (x86)\Genetec\RabbitMQ, you must create a backup for them as well.
  5. Use the advanced setup in the Mission Control installation wizard to only upgrade RabbitMQ.
  6. Restart the RabbitMQ service.