Cumulus Support

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,

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.