Contents
Cirrus Link Resources
Chariot MQTT Server v1 (previous version)
Cirrus Link Modules for Ignition
Contact Us (Sales/Support)
Forum
The following upgrade instructions for each of the supported platforms Linux and Windows requires the user has superuser/admin privileges and can execute any scripts at the command line in the directories where these servers are installed.
Warning |
---|
During this upgrade process your MQTT broker will be offline. Typical update time is less than 10 minutes. |
Stop the v2.1.0 Chariot service. From a command prompt, run the Chariot service stop script in the v2.1.0 directory
Code Block |
---|
sudo /etc/init.d/chariot stop |
Install v2.2.* following the Chariot MQTT Server Installation instructions in a new Chariot directory.
Warning |
---|
Do not overwrite the old version of Chariot when extracting the Chariot ZIP package, but instead create a new Chariot directory and extract the new Chariot package into that new directory. For example:
|
Start the v2.2.* Chariot service. From a command prompt, run the Chariot service start script in the v2.2.* directory.
Code Block |
---|
sudo /etc/init.d/chariot start |
Restore your Chariot configuration using the Backup/Restore feature. To do this navigate to System in the left menu bar of the Chariot MQTT UI, select Backup/Restore and Restore from Backup. When prompted, navigate to the backup.tgz file created earlier and import.
Confirm that any configuration items have been imported correctly.
If configured for SSL, reload any SSL certificates.
Following the Licensing Procedure, activate your existing license on the v2.2.* Chariot MQTT Server to complete the upgrade.
Backup your
NOTE: If you're trying to upgrade from 2.0.0 to 2.2.0+ you will first need to upgrade from 2.0.0 to 2.1.0 and then from 2.1.0 to 2.2.0+.
...
Chariot configuration using the Backup/Restore feature
...
. To do this navigate to System in the left menu bar of the Chariot MQTT UI, select Backup/Restore
...
and Export Backup.
...
Deactivate your Chariot license on the old Chariot instance, before you decommission it. You will need to reactivate the license on the new Chariot instance.
...
Stop the v2.1.0 Chariot service. From a command prompt, run the Chariot service stop script in the v2.1.0 directory.
Code Block |
---|
serviceStop.bat |
Install v2.2.* following the Chariot MQTT Server Installation instructions in a new Chariot directory.
Warning |
---|
Do not overwrite the old version of Chariot when extracting the Chariot ZIP package, but instead create a new |
...
Chariot directory and extract the new Chariot package into that new directory. For example |
...
: |
|
...
|
...
|
Start the v2.2.
...
# Linux Example
Old version of Chariot is installed in /opt/chariot
New version of Chariot should be installed in /opt/chariot.v2.2.0
* Chariot service. From a command prompt, run the Chariot service start script in the v2.2.* directory.
Code Block |
---|
serviceStart.bat |
Restore your Chariot configuration using the Backup/Restore feature. To do this navigate to System in the left menu bar of the Chariot MQTT UI, select Backup/Restore and Restore from Backup. When prompted, navigate to the backup.zip file created earlier and import.
...
Restore your old Chariot configuration from the backup taken in Step 1.
...
Re-upload and reactivate your existing Chariot license.
...
Re-upload your SSL certificates.
...