Welcome to the Cumulus Support forum.

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

Cumulus MX V4 beta test release 4.0.0 (build 4017) - 17 March 2024

Legacy Cumulus 1 release v1.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

MySQL Timeouts Continue

From build 3044 the development baton passed to Mark Crossley. Mark has been responsible for all the Builds since. He has made the code available on GitHub. It is Mark's hope that others will join in this development, but at the very least he welcomes your ideas for future developments (see Cumulus MX Development suggestions).

Moderator: mcrossley

stefanbagnato
Posts: 159
Joined: Sun 08 May 2016 9:11 pm
Weather Station: Vantage Pro 2
Operating System: Windows Server 2019
Location: Raleigh, NC

Re: MySQL Timeouts Continue

Post by stefanbagnato »

freddie wrote: Fri 19 Aug 2022 7:45 am
stefanbagnato wrote: Fri 19 Aug 2022 1:53 amBTW, I am curious as to your 2s realtime? Why did you go with 2s? I went with 15s since that's the update time of the VP2 wind data. I assume you have something that updates more frequently?
The VP2 sensors actually send updates every 2.5 seconds. That's why I use 2s realtime interval. See https://www.davisinstruments.com/pages/ ... e-interval
You are right! Man, I am not on my smarts game haha, between this and the 'monthly' table comment yesterday. And I should know this as I've had a Davis station (several) since I was a teen. Sighhhhhhh

Well, I like you're thinking. Mark may need to chime in on this as well, but thoughts on switching from 15 to 2? Besides of course the increase in logs and i/o between CXM and MySQL, any potential compatibility issues with the switch (not like it's changing from F to C or inHg to mb, etc)? I've had it set to 15s since inception.
freddie
Posts: 2433
Joined: Wed 08 Jun 2011 11:19 am
Weather Station: Davis Vantage Pro 2 + Ecowitt
Operating System: GNU/Linux Ubuntu 22.04 LXC
Location: Alcaston, Shropshire, UK
Contact:

Re: MySQL Timeouts Continue

Post by freddie »

stefanbagnato wrote: Fri 19 Aug 2022 12:39 pmWell, I like you're thinking. Mark may need to chime in on this as well, but thoughts on switching from 15 to 2? Besides of course the increase in logs and i/o between CXM and MySQL, any potential compatibility issues with the switch (not like it's changing from F to C or inHg to mb, etc)? I've had it set to 15s since inception.
Give it a try for a couple of days and see how it goes. It's not affecting any permanent records as it is just realtime data. MX does its own thing internally with realtime data - this setting is purely about how often "exports" of realtime data are made by MX, regardless of whether it is to file (realtime.txt, for example) or to a DB.
Freddie
Image
Post Reply