Page 1 of 2
Updating to a new MX release
Posted: Mon 18 May 2020 10:13 am
by billy
I'm in need of a bit of education about a couple of things that come out of my browsing the wiki (for entirely different purposes to the questions below!). The "Cumulus MX" topic states:
Annotation 2020-05-18 174217.jpg
(1) I stumbled across the first sentence and wondered what is "the console log" being referred to here?
(2) And then I noticed the second sentence. My MXdiags file doesn't seem to mention a new version being available. Have I missed something in there?
Of course neither issue creates a problem in terms of keeping informed about new versions.
Re: Updating to a new MX release
Posted: Mon 18 May 2020 10:34 am
by water01
The console log refers to the output terminal window that MX shows when it is run with the sudo command.
Re: Updating to a new MX release
Posted: Mon 18 May 2020 1:05 pm
by billy
thank you - I use the start/stop/restart script so the mystery is solved
Re: Updating to a new MX release
Posted: Mon 18 May 2020 1:44 pm
by jank
billy wrote: ↑Mon 18 May 2020 1:05 pm
thank you - I use the start/stop/restart script so the mystery is solved
Hello billy
there is a bug in the start/stop/restart script which is not showing the version information correctly
Bug is fixed ...new version already in the pipeline.....please be patient
-....and:
(1) I stumbled across the first sentence and wondered what is "the console log" being referred to here?
(2) And then I noticed the second sentence. My MXdiags file doesn't seem to mention a new version being available. Have I missed something in there?
I never saw an "update available" information in the console output....(mono CumulusMX.exe) of course, I am also using the start stop script......
But in the "update available" information is present in the MXDiags log
Re: Updating to a new MX release
Posted: Mon 18 May 2020 2:03 pm
by billy
thanks. (and still no luck searching mxdiags for update availability - but this is getting pedantic in the extreme)
Re: Updating to a new MX release
Posted: Tue 19 May 2020 8:31 am
by jank
billy wrote: ↑Mon 18 May 2020 2:03 pm
thanks. (and still no luck searching mxdiags for update availability - but this is getting pedantic in the extreme)
Are you sure, you are running an old version of CumulusMX ?
Anyway....here it is:
2020-05-14 14:19:26.389 Expecting listsep=, decimal=.
2020-05-14 14:19:27.987 You are not running the latest version of CumulusMX, build 3076 is available.
2020-05-14 14:19:42.161 Midnight rain found in the following entry:
And yes, I didn't realized the past updates because of the Bug in my Start Stop Script .....I realized it, when I had the need to have a deeper look into the debug logfile.
However, I am not sure, if this is only being logged if you run CumulusMX in the debug mode....btw: this is also new in the next version of my Script....running CumulusMX in Debug mode..........it was a suggestion from Mark....
Jan
Re: Updating to a new MX release
Posted: Tue 19 May 2020 11:42 am
by billy
Today I updated to 3078 (from 3075). I had restarted MX several times during the period 3075 was the version installed (from at least 28/04/2020 until today) and none of the mxdiags files have a line with "you are not running .... ". (I've searched in several different ways). In the restart today (before the upgrade) there is no line in the equivalent place to the one you have posted. Mine shows:
2020-05-19 12:24:59.947 Expecting listsep=, decimal=.
2020-05-19 12:25:00.837 Midnight rain found in the following entry:
Debug logging has been on throughout that period, but not data logging.
Re: Updating to a new MX release
Posted: Tue 19 May 2020 12:03 pm
by mcrossley
Of course, the computer you are running CMX on has to have internet access to perform the check?
Re: Updating to a new MX release
Posted: Tue 19 May 2020 1:08 pm
by billy
My knee jerk reaction to that question is yes, but my ignorance is now really going to be revealed. mx runs on a rpi that I manage headless. It happily uploads files to my website (externally hosted) so it is connected to the internet. I've also set it up to send emails. But I've never tried to use it to browse the web.
Re: Updating to a new MX release
Posted: Tue 19 May 2020 1:12 pm
by freddie
billy wrote: ↑Tue 19 May 2020 1:08 pmBut I've never tried to use it to browse the web.
Sounds like you do have internet access. Try running this in a terminal window:
Code: Select all
wget https://github.com/cumulusmx/CumulusMX/releases/download/b3078/CumulusMXDist3078.zip
If that succeeds then you definitely have everything working okay.
Re: Updating to a new MX release
Posted: Tue 19 May 2020 1:16 pm
by jank
...since the Start Stop Script -> ./cumulusmx.sh -s is showing values, I assume that this raspberry is able to reach the internet.
Can you try to start CumulusMX in debug Mode and look again into the MXdiags file ?
sudo mono CumulusMX.exe -debug
Look into the latest logfile in the MXdiags folderand search again for the sting - use grep command
grep -i "You are not running" MXdiags/*.txt
Jan
Re: Updating to a new MX release
Posted: Tue 19 May 2020 1:41 pm
by mcrossley
The update message is a normal log message, it does not require debug logging to be enabled. But the debug log may show something else of course.

Re: Updating to a new MX release
Posted: Tue 19 May 2020 1:48 pm
by billy
Freddie - yep that downloads the distribution
Jank: Debug logging has been on all the time - on three occasions in the past 6 months the connection to my station has been lost (in the previous few years no problem) and I have been waiting patiently to get more information when/if it does it again. Nonetheless, I did what you said. Of course there is no message of that sort now because I'm up to date as of this afternoon! Does one expect a line in the file indicating the version is up to date if that is the situation?
Re: Updating to a new MX release
Posted: Tue 19 May 2020 1:52 pm
by mcrossley
No, it only logs a message if you are out of date.
Re: Updating to a new MX release
Posted: Tue 26 May 2020 1:50 pm
by billy
Just to close this off, I now get the message that I'm not running the latest version of MX. As indicated in another post, I have been running with an old version of mono (4.something) and this seemed to prevent CumulusUtils from installing because it didn't have a valid SSL certificate for a fetch. An upgrade to mono V6.8 solved that problem - and I presume the new version of MX message in the console was having a similar issue.