Cumulus Support

I noticed some erroneous "Total hours of sunshine" and "High solar rad" on my Interface graphs from the end of June and early July - I don't have any solar sensors so rarely look at this graph. I used the Interface dayfile editor to remove the readings. On each save I noticed a MySql error occuring - I didn't make a note of the precise error text, but wasn't too fussed as I can always manually delete the entries in the database table. I did this about 11:10 UTC today and moved onto doing other stuff (company tax return!). I didn't think anything was amiss (as I was still seeing data on the MX dashboard) until I got an email notification from WeatherCloud saying that my device had been offline since 11:10 UTC. Looking in the MXdiags file I could see repeated SQL errors since 11:10 UTC - referring to the CustomSqlSecs realtime statements, but containing queries from the regular realtime updates (i.e. NOT the custom ones that I have defined). No errors from WeatherCloud - just no WeatherCloud update log statements after 11:10 UTC. Similar for WOW, APRS, Windy, PWS, etc. Even generation of twitter.txt stopped (I wrote my own tweeting utility but fortunately included in it a check to see if twitter.txt has updated before actually tweeting).

I restarted MX once I noticed the errors in the MXdiags file, and all has returned to normal.

I can only think that the MySQL errors I saw during my use of the Interface dayfile editor triggered all sorts of problems for timed threads! Attached below is the MXdiags file.

Thanks, I'll get the day file editor SQL statement format fixed tonight, then take a look at why it was affecting the other uploads...

Thanks Mark.