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.8.3 or later, as applicable.
Before you begin
To see how .erlang cookie paths are constructed, see the RabbitMQ Clustering Guide
Copy the Genetec Mission Control™ 22.214.171.124 installation package to all RabbitMQ servers.
What you should know
To upgrade RabbitMQ on standalone machines, perform the following steps on each node:
- Stop the RabbitMQ service.
Back up the .erlang.cookie file to a temporary storage
Usual file path for the .erlang.cookie can be either of the following:
- If using your own certificates in C:\Program Files (x86)\Genetec\RabbitMQ, you must create a back up for them as well.
Use the advanced setup in the Genetec Mission
126.96.36.199 installation wizard to only upgrade RabbitMQ.
Your RabbitMQ has been upgraded.
If you have a RabbitMQ configuration for high availability with 3 or more nodes, on each node:
Right-click the Notepad application, select Run as
administrator, and then open the RabbitMQ.conf file in
By default, the RabbitMQ configuration file, RabbitMQ.conf, is found in C:\ProgramData\Genetec\RabbitMQ\config.Tip: Using Notepad++ with Makefile set as language improves the readability of the file.
Modify the following line from:
# cluster_partition_handling = pause_minority
By removing the
cluster_partition_handling = pause_minority
#symbol, the line is no longer flagged as a comment and becomes part of the code.
- Save the file.
- Restart the RabbitMQ service.