Contents
Cirrus Link Resources
Chariot MQTT Server v1 (previous version)
Cirrus Link Modules for Ignition
Contact Us (Sales/Support)
Forum
Warning |
---|
During this upgrade process your MQTT broker will be offline. If you are performing license deactivation/reactivation online, then typical update time is less than 10 minutes. If you are performing license deactivation/activation offline, you will need to send the deactivation/activation requests to support@cirrus-link.com in order to receive the Activation Code required to complete the upgrade. Cirrus Link support hours are 8am - 5pm PST. To minimize downtime during your upgrade, we recommend letting Cirrus Link know ahead of time so we ensure support availability during your upgrade period. |
Note |
---|
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. |
Following the Licensing Procedure, deactivate your existing license on the
v2.1.0Chariot MQTT Server.
Tip |
---|
If deactivating offline, make sure to send the generated Deactivation Request text to support@cirrus-link.com |
Stop the v2.1.0 Chariot service. From a command prompt, run the Chariot service stop script in the v2.1.0 installed directory
Code Block |
---|
# Use this command for Chariot versions prior to 2.4.1 sudo /etc/init.d/chariot stop # Use this command for Chariot v2.4.2 and later sudo systemctl stop chariot |
Install the new version of Chariot 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:
|
If configuring SSL, copy ssl.jks keystore from Step 3 to <NEW_chariot_install_folder>/security
Warning |
---|
If you fail to do the copy BEFORE you start Chariot for the first time, the certs will not get picked up dynamically. |
Start the new version of Start the v2.2.* Chariot service. From a command prompt, run the Chariot service start script in the v2.2*.* directory.
Code Block |
---|
# Use this command for Chariot versions prior to 2.4.1 sudo /etc/init.d/chariot start # Use this command for Chariot v2.4.2 and later sudo systemctl start chariot |
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.* new Chariot MQTT Server to complete the upgrade.
Tip |
---|
If activating offline, make sure to send the generated Activation Request to support@cirrus-link.com. They will return the Activation Code required to complete the upgrade. |
Following the Licensing Procedure, deactivate your existing license on the
v2.1.0Chariot MQTT Server.
Tip |
---|
If deactivating offline, make sure to send the generated Deactivation Request text to support@cirrus-link.com |
Backup 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 Export Backup.
Stop the v2.1.0 Chariot service. From a command prompt, run the Chariot service stop script in the v2.1.0 installed directory.
Code Block |
---|
serviceStop.bat |
Install v2.2.* the new version of Chariot 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:
|
If configuring SSL, copy ssl.jks keystore from Step 3 to <NEW_chariot_install_folder>\security
Warning |
---|
If you fail to do the copy BEFORE you start Chariot for the first time, the certs will not get picked up dynamically. |
Start the new version of Start the v2.2.* 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.
Following the Licensing Procedure, activate your existing license on the
v2.2.*new Chariot MQTT Server to complete the upgrade.
Tip |
---|
If activating offline, make sure to send the generated Activation Request to support@cirrus-link.com. They will return the Activation Code required to complete the upgrade. |