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
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
sql
Moderator: mcrossley
- dazza1223
- Posts: 910
- Joined: Sun 25 Jan 2015 8:41 pm
- Weather Station: Davis Vantage Pro 2 plus
- Operating System: Raspberry pi 4 (4gb)
- Location: Worthing
- Contact:
sql
hi ive just setup SQL to use with top10.php
i get this in MXdiags
017-01-27 02:08:01.550 Error encountered during MySQL operation.
2017-01-27 02:08:01.550 Connection must be opened.
2017-01-27 02:08:03.550 Error encountered during MySQL operation.
2017-01-27 02:08:03.550 Connection must be opened.
2017-01-27 02:08:05.557 Error encountered during MySQL operation.
2017-01-27 02:08:05.558 Connection must be opened.
2017-01-27 02:08:07.568 Error encountered during MySQL operation.
2017-01-27 02:08:07.568 Connection must be opened.
2017-01-27 02:08:09.567 Error encountered during MySQL operation.
2017-01-27 02:08:09.568 Connection must be opened.
2017-01-27 02:08:11.577 Error encountered during MySQL operation.
2017-01-27 02:08:11.578 Connection must be opened.
2017-01-27 02:08:13.595 Error encountered during MySQL operation.
2017-01-27 02:08:13.595 Connection must be opened.
2017-01-27 02:08:15.578 Error encountered during MySQL operation.
2017-01-27 02:08:15.578 Connection must be opened.
2017-01-27 02:08:17.578 Error encountered during MySQL operation.
2017-01-27 02:08:17.579 Connection must be opened.
2017-01-27 02:08:19.579 Error encountered during MySQL operation.
2017-01-27 02:08:19.579 Connection must be opened.
2017-01-27 02:08:21.578 Error encountered during MySQL operation.
2017-01-27 02:08:21.579 Connection must be opened.
2017-01-27 02:08:23.578 Error encountered during MySQL operation.
2017-01-27 02:08:23.579 Connection must be opened.
2017-01-27 02:08:25.588 Error encountered during MySQL operation.
2017-01-27 02:08:25.588 Connection must be opened.
2017-01-27 02:08:27.597 Error encountered during MySQL operation.
2017-01-27 02:08:27.598 Connection must be opened.
2017-01-27 02:08:29.599 Error encountered during MySQL operation.
2017-01-27 02:08:29.600 Connection must be opened.
2017-01-27 02:08:31.598 Error encountered during MySQL operation.
2017-01-27 02:08:31.598 Connection must be opened.
2017-01-27 02:08:33.621 Error encountered during MySQL operation.
2017-01-27 02:08:33.622 Connection must be opened.
2017-01-27 02:08:35.598 Error encountered during MySQL operation.
2017-01-27 02:08:35.598 Connection must be opened.
2017-01-27 02:08:37.598 Error encountered during MySQL operation.
2017-01-27 02:08:37.598 Connection must be opened.
2017-01-27 02:08:39.601 Error encountered during MySQL operation.
2017-01-27 02:08:39.602 Connection must be opened.
2017-01-27 02:08:41.598 Error encountered during MySQL operation.
2017-01-27 02:08:41.598 Connection must be opened.
2017-01-27 02:08:43.738 Error encountered during MySQL operation.
2017-01-27 02:08:43.738 Connection must be opened.
2017-01-27 02:08:45.608 Error encountered during MySQL operation.
2017-01-27 02:08:45.608 Connection must be opened.
2017-01-27 02:08:47.608 Error encountered during MySQL operation.
2017-01-27 02:08:47.609 Connection must be opened.
2017-01-27 02:08:49.608 Error encountered during MySQL operation.
2017-01-27 02:08:49.608 Connection must be opened.
2017-01-27 02:08:51.608 Error encountered during MySQL operation.
2017-01-27 02:08:51.608 Connection must be opened.
2017-01-27 02:08:53.629 Error encountered during MySQL operation.
2017-01-27 02:08:53.629 Connection must be opened.
2017-01-27 02:08:55.609 Error encountered during MySQL operation.
2017-01-27 02:08:55.609 Connection must be opened.
2017-01-27 02:08:57.618 Error encountered during MySQL operation.
2017-01-27 02:08:57.618 Connection must be opened.
2017-01-27 02:08:59.617 Error encountered during MySQL operation.
is there somthink im missing
i get this in MXdiags
017-01-27 02:08:01.550 Error encountered during MySQL operation.
2017-01-27 02:08:01.550 Connection must be opened.
2017-01-27 02:08:03.550 Error encountered during MySQL operation.
2017-01-27 02:08:03.550 Connection must be opened.
2017-01-27 02:08:05.557 Error encountered during MySQL operation.
2017-01-27 02:08:05.558 Connection must be opened.
2017-01-27 02:08:07.568 Error encountered during MySQL operation.
2017-01-27 02:08:07.568 Connection must be opened.
2017-01-27 02:08:09.567 Error encountered during MySQL operation.
2017-01-27 02:08:09.568 Connection must be opened.
2017-01-27 02:08:11.577 Error encountered during MySQL operation.
2017-01-27 02:08:11.578 Connection must be opened.
2017-01-27 02:08:13.595 Error encountered during MySQL operation.
2017-01-27 02:08:13.595 Connection must be opened.
2017-01-27 02:08:15.578 Error encountered during MySQL operation.
2017-01-27 02:08:15.578 Connection must be opened.
2017-01-27 02:08:17.578 Error encountered during MySQL operation.
2017-01-27 02:08:17.579 Connection must be opened.
2017-01-27 02:08:19.579 Error encountered during MySQL operation.
2017-01-27 02:08:19.579 Connection must be opened.
2017-01-27 02:08:21.578 Error encountered during MySQL operation.
2017-01-27 02:08:21.579 Connection must be opened.
2017-01-27 02:08:23.578 Error encountered during MySQL operation.
2017-01-27 02:08:23.579 Connection must be opened.
2017-01-27 02:08:25.588 Error encountered during MySQL operation.
2017-01-27 02:08:25.588 Connection must be opened.
2017-01-27 02:08:27.597 Error encountered during MySQL operation.
2017-01-27 02:08:27.598 Connection must be opened.
2017-01-27 02:08:29.599 Error encountered during MySQL operation.
2017-01-27 02:08:29.600 Connection must be opened.
2017-01-27 02:08:31.598 Error encountered during MySQL operation.
2017-01-27 02:08:31.598 Connection must be opened.
2017-01-27 02:08:33.621 Error encountered during MySQL operation.
2017-01-27 02:08:33.622 Connection must be opened.
2017-01-27 02:08:35.598 Error encountered during MySQL operation.
2017-01-27 02:08:35.598 Connection must be opened.
2017-01-27 02:08:37.598 Error encountered during MySQL operation.
2017-01-27 02:08:37.598 Connection must be opened.
2017-01-27 02:08:39.601 Error encountered during MySQL operation.
2017-01-27 02:08:39.602 Connection must be opened.
2017-01-27 02:08:41.598 Error encountered during MySQL operation.
2017-01-27 02:08:41.598 Connection must be opened.
2017-01-27 02:08:43.738 Error encountered during MySQL operation.
2017-01-27 02:08:43.738 Connection must be opened.
2017-01-27 02:08:45.608 Error encountered during MySQL operation.
2017-01-27 02:08:45.608 Connection must be opened.
2017-01-27 02:08:47.608 Error encountered during MySQL operation.
2017-01-27 02:08:47.609 Connection must be opened.
2017-01-27 02:08:49.608 Error encountered during MySQL operation.
2017-01-27 02:08:49.608 Connection must be opened.
2017-01-27 02:08:51.608 Error encountered during MySQL operation.
2017-01-27 02:08:51.608 Connection must be opened.
2017-01-27 02:08:53.629 Error encountered during MySQL operation.
2017-01-27 02:08:53.629 Connection must be opened.
2017-01-27 02:08:55.609 Error encountered during MySQL operation.
2017-01-27 02:08:55.609 Connection must be opened.
2017-01-27 02:08:57.618 Error encountered during MySQL operation.
2017-01-27 02:08:57.618 Connection must be opened.
2017-01-27 02:08:59.617 Error encountered during MySQL operation.
is there somthink im missing
- steve
- Cumulus Author
- Posts: 26672
- Joined: Mon 02 Jun 2008 6:49 pm
- Weather Station: None
- Operating System: None
- Location: Vienne, France
- Contact:
Re: sql
Looks like Cumulus was unable to connect to your SQL server - are there no error messages about this near the start of the diags file? Have you configured your SQL server details correctly in Cumulus? Does your SQL server allow remote connections? Some don't, and with those that do, sometimes you have to explicitly allow the remote connection. Your hosting provider should have this information.
Steve
- dazza1223
- Posts: 910
- Joined: Sun 25 Jan 2015 8:41 pm
- Weather Station: Davis Vantage Pro 2 plus
- Operating System: Raspberry pi 4 (4gb)
- Location: Worthing
- Contact:
Re: sql
i will send you the file mate and i use sql on my raspberry pi 3 and the webserver the same pi
and i look in mysql and i can see the database be uploaded
and the setting in the Cumulus i uese host name 127.0.0.1
and port is 3306
but it must be ok as i se the database?
and i look in mysql and i can see the database be uploaded
and the setting in the Cumulus i uese host name 127.0.0.1
and port is 3306
but it must be ok as i se the database?
Code: Select all
You do not have the required permissions to view the files attached to this post.
- steve
- Cumulus Author
- Posts: 26672
- Joined: Mon 02 Jun 2008 6:49 pm
- Weather Station: None
- Operating System: None
- Location: Vienne, France
- Contact:
Re: sql
Looks like the updates into the 'Monthly' table are OK and the errors are from another update. Some kind of configuration error somewhere, perhaps. Perhaps you haven't created the other tables?
Steve
- steve
- Cumulus Author
- Posts: 26672
- Joined: Mon 02 Jun 2008 6:49 pm
- Weather Station: None
- Operating System: None
- Location: Vienne, France
- Contact:
Re: sql
From the frequency of the error messages, it must be the connection for the realtime update which is failing. Unfortunately, I can't tell you why. Perhaps your SQL server logs can give you more information.
Steve
- steve
- Cumulus Author
- Posts: 26672
- Joined: Mon 02 Jun 2008 6:49 pm
- Weather Station: None
- Operating System: None
- Location: Vienne, France
- Contact:
Re: sql
The bug was that processing of the realtimegauges.txt file caused problems with the processing of other files.
You seem to be uploading lots of files at a the realtime interval. And using a very short realtime interval = 1 or 2 seconds? I'm not sure why you're doing that for files that don't change that frequently, but I suspect that the uploads are taking longer than the time you are allowing and hence one set of uploads is clashing with the next one (although in theory Cumulus shouldn't start the next upload if the previous one hasn't finished).
You seem to be uploading lots of files at a the realtime interval. And using a very short realtime interval = 1 or 2 seconds? I'm not sure why you're doing that for files that don't change that frequently, but I suspect that the uploads are taking longer than the time you are allowing and hence one set of uploads is clashing with the next one (although in theory Cumulus shouldn't start the next upload if the previous one hasn't finished).
Steve
- dazza1223
- Posts: 910
- Joined: Sun 25 Jan 2015 8:41 pm
- Weather Station: Davis Vantage Pro 2 plus
- Operating System: Raspberry pi 4 (4gb)
- Location: Worthing
- Contact:
Re: sql
so i got Extra web files to /home/pi/usb/davis/web/realtimegaugesT.txt /home/pi/usb/website/realtimegauges.txt so i dont do it like that ?
and so do i uptick real time then mate?
and the realtime interval = 1 or 2 what shud it be?
and so do i uptick real time then mate?
and the realtime interval = 1 or 2 what shud it be?
- steve
- Cumulus Author
- Posts: 26672
- Joined: Mon 02 Jun 2008 6:49 pm
- Weather Station: None
- Operating System: None
- Location: Vienne, France
- Contact:
Re: sql
If you just want to copy the realtimegauges.txt file locally, you will need to use Extra Files as you are doing (and select realtime for that one), and not tick the new option to do it automatically. You should untick the realtime setting for most if not all of your other files, it's pointless processing all-time records, for example, at 2-second intervals.
Steve
- steve
- Cumulus Author
- Posts: 26672
- Joined: Mon 02 Jun 2008 6:49 pm
- Weather Station: None
- Operating System: None
- Location: Vienne, France
- Contact:
Re: sql
Once you've stopped trying to do so much at the realtime interval, 2 seconds might be a reasonoable setting (given that you have a Davis which updates wind speeds at 2 to 3 second intervals). if you still have problems you'll need to try increasing the interval.
Steve