5,838
edits
MX on Linux: Difference between revisions
From Cumulus Wiki
Jump to navigationJump to search
m
→Report and data files to copy across from any previous Cumulus location
| (2 intermediate revisions by the same user not shown) | |||
| Line 345: | Line 345: | ||
All the (optional) files in the [[Reports folder]] can be copied across from a previous installation. If your previous installation was not on Linux, see [[#Line terminators in .txt files]] | All the (optional) files in the [[Reports folder]] can be copied across from a previous installation. If your previous installation was not on Linux, see [[#Line terminators in .txt files]] | ||
<br> | |||
If your previous Cumulus installation was of the legacy software, version 1.9.4, or earlier, then you need to do a lot of reading: | Whilst you should copy ALL the files in the [[data folder]], from any old installation into the new installation, there are several extra considerations: | ||
* [[Amending dayfile]] tells you about how MX is far more fussy about the content in [[dayfile.txt]] | * '''Your new MX installation will ignore any entries prior to the MX Start Date''' in [[Monthly log files]], such as [[Standard log files]], and [[Extra Sensor Files]]: | ||
* [[:Category:Ini Files|.ini files]] explains how time-stamps are formatted differently in the extreme tracking files | ** See [[Cumulus.ini#Data_Logging|'''StartDate=xxxxx''']] parameter, edit using ''Station Settings → Common Options → Advanced Options → Records Began date'' | ||
* [[Migrating from Cumulus 1 to MX]] gives some advice about differences in settings, but be aware that the way MX handles settings varies by release, and information on the linked page may be out of date | * Be aware your new installation has to use the same "locale" as the old installation, or MX will struggle as the locale affects how new lines are stored, and how MX expects old lines to have been stored. | ||
* Microsoft Windows uses different line terminators, see [[#Line terminators in .txt files]], although MX should cope, any third party routines reading your data files will probably not accept a line terminator change. | |||
* If your previous Cumulus installation was of the legacy software, version 1.9.4, or earlier, then you need to do a lot of reading: | |||
** [[Amending dayfile]] tells you about how MX is far more fussy about the content in [[dayfile.txt]] | |||
** [[:Category:Ini Files|.ini files]] explains how time-stamps are formatted differently in the extreme tracking files | |||
** [[Migrating from Cumulus 1 to MX]] gives some advice about differences in settings, but be aware that the way MX handles settings varies by release, and information on the linked page may be out of date | |||
==Configuration Files to copy across from any previous Cumulus installation== | ==Configuration Files to copy across from any previous Cumulus installation== | ||
| Line 442: | Line 447: | ||
# as a service and | # as a service and | ||
# interactively with terminal window left open. | # interactively with terminal window left open. | ||
As a side-note, some weather station types require MX to be run with '''root''' rights, this is why ''sudo'' is included in each example command, but if you have technical knowledge and know your weather station can be run with default user, you can omit the ''sudo'' provided your user has ownership of all folders and files used by MX. | |||
== Optional parameters to add to the instruction to run the MX engine == | == Optional parameters to add to the instruction to run the MX engine == | ||
| Line 505: | Line 512: | ||
=== -debug parameter for adding debugging === | === -debug parameter for adding debugging === | ||
This is only available for [https://cumulus.hosiene.co.uk/viewtopic.php?p=138839#p138839 release 3.4.4 - Build 3068] onwards. This switches on debug and data logging from the start-up of Cumulus MX by adding a parameter: | |||
:<code>sudo mono CumulusMX.exe -debug</code> | |||
MX has a default level of logging that stores in the [[MXdiags_folder]] folder a log file that shows some of the interaction with the weather station and some of the output actions done as MX runs. A new log is started each time MX is restarted. | MX has a default level of logging that stores in the [[MXdiags_folder]] folder a log file that shows some of the interaction with the weather station and some of the output actions done as MX runs. A new log is started each time MX is restarted. | ||
If there is a problem, then there is a great benefit in actually increasing the level of detail in these logs; and that is done either within the settings (on recent MX releases this is on '''Program Settings''' page of admin interface - please see [[ | If there is a problem, then there is a great benefit in actually increasing the level of detail in these logs; and that is done either within the settings (on recent MX releases this is on '''Program Settings''' page of admin interface - please see [[:Category:Diagnostics]] page for details) or the above command. | ||
=== Parameters only applicable to Version 3.0.0 Beta builds of MX === | === Parameters only applicable to Version 3.0.0 Beta builds of MX === | ||
| Line 519: | Line 528: | ||
Beta builds in MX version 3.0.0 had an optional parameter <code>sudo mono EXISTING PATH/CumulusMX/CumulusMX.exe -wsport nnnn</code> that determined which port (represented by a 4 digit number ''nnnn'') was used for '''Web Sockets'''. | Beta builds in MX version 3.0.0 had an optional parameter <code>sudo mono EXISTING PATH/CumulusMX/CumulusMX.exe -wsport nnnn</code> that determined which port (represented by a 4 digit number ''nnnn'') was used for '''Web Sockets'''. | ||
Note use of this parameter is now deprecated, as it has been incorporated into '''-port''' parameter described earlier. The reason is that [https://cumulus.hosiene.co.uk/viewtopic.php?f=40&t=17887&p=138815&hilit=sockets#p138815 Web Sockets in all builds since 3045] use the same port for web sockets as for the HTTP port of the [[MX_Administrative_Interface#The_API_interface|Admin Interface]]. | |||
==== -logging parameter for debugging of data flow between station and MX==== | ==== -logging parameter for debugging of data flow between station and MX==== | ||
Beta builds in MX version 3.0.0 had an optional parameter <code>sudo mono CumulusMX.exe -Logging=1</code> (for the station to MX transfers to have increased debugging logging). | |||
Note use of this parameter is now deprecated, as it has been incorporated into '''-debug''', see above. | |||
==Running as a service== | ==Running as a service== | ||
