Upgrading a RabbitMQ failover cluster to version 3.7.10 - Genetec Mission Control™ 2.12.1.0

If RabbitMQ is deployed in a failover configuration with a master node and a secondary node, you must use an adapted procedure to upgrade RabbitMQ to version 3.7.10. This version of RabbitMQ was introduced in Genetec Mission Control™ 2.11.

1. On the secondary node, do the following:
   1. Stop the RabbitMQ service.
   2. Back up the .erlang.cookie file from C:\Windows to a temporary storage location.
      IMPORTANT: A new .erlang.cookie file is generated during the upgrade process and must be replaced with the backup.
2. On the master node, do the following:
   1. Stop the RabbitMQ service.
   2. Back up the .erlang.cookie file from C:\Windows to a temporary storage location.
   3. Use the advanced setup in the Genetec Mission Control™ 2.12.1.0 installation wizard to only upgrade RabbitMQ.
   4. Restore your backup of the .erlang.cookie file to the following locations:
      • %HOMEDRIVE%%HOMEPATH%

        Usually C:\Users\<username>

      • C:\Windows\System32\config\systemprofile
   5. Restart the RabbitMQ service.
3. On the secondary node, do the following:
   1. Uninstall the current version of Erlang/OTP.
   2. Install Erlang/OTP 21.2.
      NOTE: The Erlang/OTP 21.2 installer is bundled with our software. To install it, do the following:

      1. Open the Genetec Mission Control™ 2.12.1.0 installation package.
      2. Navigate to the MC Packages folder.
      3. Run the Erlang/OTP installer for your version of Windows.
         • otp_win32_21.2 (32-bit)
         • otp_win64_21.2 (64-bit)
   3. Restore your backup of the .erlang.cookie file to the following locations:
      • %HOMEDRIVE%%HOMEPATH%

        Usually C:\Users\<username>

      • C:\Windows\System32\config\systemprofile
   4. Use the advanced setup in the Genetec Mission Control™ 2.12.1.0 installation wizard to only upgrade RabbitMQ.
   5. Restart the RabbitMQ service.