5,838
edits
MX on Linux: Difference between revisions
m
upgrading section rewritten
m (upgrading section rewritten) |
|||
| Line 172: | Line 172: | ||
==Upgrading a Cumulus package== | ==Upgrading a Cumulus package== | ||
If you are running an older release, before skipping in-between versions please check [[Updating_MX_to_new_version|here]]. Always check the release announcements in [https://cumulus.hosiene.co.uk/viewtopic.php?f=40&t=17887 Cumulus MX announcements] for any action needed in planned upgrade. In brief, all files from new release distribution replace the files from previous release, and the download/unzip is as covered above. | |||
If you run MX as a service, then: | |||
# Ensure you are not doing any changes to settings | |||
# Leave MX running as you copy files from the new release distribution over the existing files | |||
# Try to pick a time just after MX has done any standard interval store of readings or upload, so that it is least busy | |||
# Use <code>sudo systemctl restart cumulusmx</code> to stop and then restart MX picking up the new files | |||
# Result, downtime of MX kept to a minimum, so avoiding losing data | |||
If you run MX interactively, do the unzip into a temporary location before you stop MX, then copy all files from temporary location over your existing files, and finally restart MX. Depending on your weather station type, it might or might not offer historic data catch-up, so you might lose some data while MX is stopped, and therefore should keep the downtime to a minimum. | |||
The alternative is to install in a new folder (or rename the old one), and copy across files not in the release from old location to new location, but in that alternative you might forget some files. | |||
==Changing location of Cumulus== | ==Changing location of Cumulus== | ||