...
- Recommended procedure: you can publish a new configuration for the system from the cloud interface, use our simple templates and distribute the configuration to the different sites. This process is automated and is the recommended path in order to keep track of changes, updates and possible issues.
- Change the configuration file XML. After doing this, you will need to restart both the mosquitto broker and the Site Controller, with the following commands sequence:
...
| Code Block |
|---|
#$SiteControllerPath$/run_SiteController.sh stop |
...
#$SiteControllerPath$/run_SiteController.sh mosquitto_stop |
...
#$SiteControllerPath$/run_SiteController.sh mosquitto_start |
...
#$SiteControllerPath$/run_SiteController.sh start |
...
- Alternatively, you can publish the new configuration through MQTT in the topic /config/complete_update using any mosquitto client available (like MQTTfx).
...
If the process of updating the configuration is successful. If not, the log will tell you which part of the configuration has failed, and revert to the last known valid configuration. Below there is the log that we expect after a proper configuration change. In case there is some error, there will be information regarding where the problem has ocurred.
| Code Block |
|---|
2015-02-26 12:10:40,090:1994:[ConfigProvider.py:374]:INFO:We have changes - so we publish the new config as last valid config/complete... |
...
2015-02-26 12:10:43,991:1994:[ConfigProvider.py:395]:INFO:Save config to disk: True |
...
2015-02-26 12:10:43,993:1994:[ConfigProvider.py:410]:DEBUG:backup_xml_toprettyxml: True |
...
2015-02-26 12:10:48,215:1994:[ConfigProvider.py:425]:DEBUG:Number of backup config files: 0 |
...
2015-02-26 12:10:48,220:1994:[ConfigProvider.py:392]:INFO:Processing time: 30.35 |
...
Next Steps
| Info |
|---|