Welcome to the Cumulus Support forum.

Latest Cumulus MX V4 release 4.4.2 (build 4085) - 12 March 2025

Latest Cumulus MX V3 release 3.28.6 (build 3283) - 21 March 2024

Legacy Cumulus 1 release 1.9.4 (build 1099) - 28 November 2014
(a patch is available for 1.9.4 build 1099 that extends the date range of drop-down menus to 2030)

Download the Software (Cumulus MX / Cumulus 1 and other related items) from the Wiki

If you are posting a new Topic about an error or if you need help PLEASE read this first viewtopic.php?p=164080#p164080

MX not talking to console

Please DO NOT use this to publish your entire wish. This Forum is for specific suggestions to enhance the usability of Cumulus MX for all users, NOT your personal requirements. Please check this forum and the rejected forum to make sure you are NOT posting a DUPLICATE suggestion. It will be heavily monitored by Admin and Mark Crossley to determine the feasibility and the difficulty of the suggestion. Those Topics that are deemed inadmissible will moved to the rejected Forum. The remaining Topics will be the Accepted list of future developments, and when our voluntary development group adds it to a build, the build number will be added to the Topic title.
Post Reply
UncleBuck
Posts: 43
Joined: Sat 29 Dec 2012 10:27 pm
Weather Station: Davis VP2+
Operating System: MAC Mini - OSX El Capitan
Location: Victoria, Australia

MX not talking to console

Post by UncleBuck »

I have been doing quite a bit of work getting data out of MySQL and today MX decided it could not get the data from the console.

Restarting MX fixed that problem (what caused it I don't know) BUT, during the time MX could not get the data from the console, it kept sending the same data to MySQL every minute and kept sending an updated (but incorrect) realtime file to the server.

I stopped MX again, restored the files from a backup just prior to when the error started and started MX again. This fixed all the dayfile etc, but I noticed that MySQL was still showing the erroneous data. I thought MX "updated" the entries in MySQL but it appears this is not the case.

What I had to do was stop MX, restore the files, remove the erroneous entries from MySQL and then finally restart MX.

So now a request for a future update to MX:
When MX cannot get the data from the console, MySQL not be updated.

I hope all of the above makes sense.
Regards,
User avatar
steve
Cumulus Author
Posts: 26672
Joined: Mon 02 Jun 2008 6:49 pm
Weather Station: None
Operating System: None
Location: Vienne, France
Contact:

Re: MX not talking to console

Post by steve »

UncleBuck wrote:I thought MX "updated" the entries in MySQL but it appears this is not the case.
It does "INSERT IGNORE". I could change it to "INSERT ... ON DUPLICATE KEY UPDATE" if it's generally thought that's a good idea, and no-one can think of any problems with doing it.
So now a request for a future update to MX:
When MX cannot get the data from the console, MySQL not be updated.
This would be covered by the existing request(s) to stop updating things in general if there is no new data, if/when I ever get around to doing it.
Steve
Post Reply