Welcome to the Cumulus Support forum.

Latest Cumulus MX release 3.28.5 (build 3282) - 23 February 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

Monthly Log file has stopped updating

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

bort483
Posts: 31
Joined: Tue 19 Sep 2017 9:16 am
Weather Station: Davis Vantage Pro2
Operating System: Ubuntu

Monthly Log file has stopped updating

Post by bort483 »

Hi. Just wondering if someone could help me out here.

So since the 10th of November, my monthly data logs have stopped uploading to Cumulus (however everything else like real-time, dayfile, uploading to my website etc works fine Essentially, this is just leaving me with a blank gap in my weather history from the 10th (which outputs in my NOAA data). I can't remember anything changed on this day so I have no idea how or why this happened. I would be extremely grateful if anyone could help me with this and maybe provide some info on how I might go about getting it working again. The box it runs on is scheduled to reboot at 4am everyday so obviously a simple reboot hasn't been enough to fix it. Thanks.
User avatar
HansR
Posts: 5784
Joined: Sat 20 Oct 2012 6:53 am
Weather Station: GW1100 (WS80/WH40)
Operating System: Raspberry OS/Bullseye
Location: Wagenborgen (NL)
Contact:

Re: Monthly Log file has stopped updating

Post by HansR »

Could you switch debug and data logging on and post your MXdiags please?
Hans

https://meteo-wagenborgen.nl
CMX build 3278 ● Ecowitt GW1100/WS80/WH40 ● RPi 3B+ ● Raspberry OS 6.1.21 ● Mono 6.12.0.200
https://meteo-wagenborgen.nl/CMX4/NET8/ (beta)
CMX build 4003+ ● RPi 4B ● RPi OS 6.1.0-rpi7-rpi-v8 aarch64 ● dotnet 8.0.1
bort483
Posts: 31
Joined: Tue 19 Sep 2017 9:16 am
Weather Station: Davis Vantage Pro2
Operating System: Ubuntu

Re: Monthly Log file has stopped updating

Post by bort483 »

I hope this helps:
20231128-215001.txt
edit: What should 'PING escape time' be set to? When I turned on debugging for this, I had to enter a value of 1 or more...I entered 1 and now my realtime data to my saratoga template keeps fluctuating between Current and Not Current because it isn't updating frequently enough. :shrug:
You do not have the required permissions to view the files attached to this post.
User avatar
HansR
Posts: 5784
Joined: Sat 20 Oct 2012 6:53 am
Weather Station: GW1100 (WS80/WH40)
Operating System: Raspberry OS/Bullseye
Location: Wagenborgen (NL)
Contact:

Re: Monthly Log file has stopped updating

Post by HansR »

You have multiple errors:
  1. Network errors
  2. Errors in the log record
  3. Difference between station logger interval and CMX logging interval
  4. etc?...
I would advise to start removing the error in the logfile and set the logger interval equal to the CMX interval. Then check your network connection with the logger. It is a Davis machine so it is best if Mark continues from here as the multiple errors in the Davis environment is too much for me :groan:

Code: Select all

2023-11-28 21:50:59.817 Reading history data from log files
2023-11-28 21:50:59.818 Loading last N hour data from data logs: 11/28/2023 9:45:00 PM
2023-11-28 21:50:59.832 LoadRecent: Attempting to load 7 days of entries to recent data list
2023-11-28 21:51:00.701 Error parsing log file record: Input string was not in a correct format.
2023-11-28 21:51:00.701 Log record:                                                                                                                                12/11/23,05:40,16.4,81,13.2,0,2,157,0.0,0.0,1020.4,527.2,22.4,68,0,16.4,16.4,0.0,0,0.00,0.00,17.4,56,0.0,159,0.0,0.0,17.1,19.3
2023-11-28 21:51:00.702 LoadRecent: Error at line 3127 of data/Nov23log.txt : Input string was not in a correct format.
2023-11-28 21:51:00.702 Please edit the file to correct the error
2023-11-28 21:51:01.971 LoadRecent: Loaded 0 of 0 new entries to recent database
2023-11-28 21:51:01.983 LoadWindData: Attempting to reload the wind speeds array
2023-11-28 21:51:02.021 LoadWindData: Loaded 633 entries to WindRecent data list
2023-11-28 21:51:02.029 LoadLast3Hour: Attempting to load 3 hour data list
2023-11-28 21:51:02.071 LoadLast3Hour: Loaded 156 entries to last 3 hour data list
2023-11-28 21:51:02.089 InitialiseWind: gust=0.0, speed=0.0
2023-11-28 21:51:02.089 Reading archive data from logger
2023-11-28 21:51:02.110 CheckLoggerInterval: Reading logger interval
2023-11-28 21:51:02.110 WakeVP: Not required
2023-11-28 21:51:02.110 WaitForACK: Starting
2023-11-28 21:51:02.611 WaitForACK: ACK received
2023-11-28 21:51:02.611 CheckLoggerInterval: Received - 1E-F3-FF
2023-11-28 21:51:02.611 CheckLoggerInterval: Station logger interval is 30 minutes
2023-11-28 21:51:02.611 CheckLoggerInterval: ** WARNING: Your station logger interval 30 mins does not match your Cumulus MX logging interval 5 mins
2023-11-28 21:51:02.612 Wind settings: Calc avg speed=True, Use speed for avg=False, Gust time=10, Avg time=10
2023-11-28 21:51:03.013 888 web tags initialised

Also you have network errors (which at first instance seem to correct):

Code: Select all

2023-11-28 21:50:08.916 Station type = Davis
2023-11-28 21:50:08.916 LOOP2 enabled
2023-11-28 21:50:08.916 IP address = 192.168.0.11 Port = 22222
2023-11-28 21:50:08.916 periodic disconnect = 2
2023-11-28 21:50:08.920 InitTCP: Connecting to the station
2023-11-28 21:50:08.921 OpenTcpPort: TCP Logger Connect attempt 1
2023-11-28 21:50:08.935 OpenTcpPort: Error - Network is unreachable
2023-11-28 21:50:08.938 OpenTcpPort: TCP Logger Connect attempt 2
2023-11-28 21:50:08.939 OpenTcpPort: Error - Network is unreachable
2023-11-28 21:50:08.939 OpenTcpPort: TCP Logger Connect attempt 3
2023-11-28 21:50:08.940 OpenTcpPort: Error - Network is unreachable
2023-11-28 21:50:08.940 OpenTcpPort: TCP Logger Connect attempt 4
2023-11-28 21:50:08.941 OpenTcpPort: Error - Network is unreachable
2023-11-28 21:50:08.941 OpenTcpPort: TCP Logger Connect attempt 5
2023-11-28 21:50:08.942 OpenTcpPort: Error - Network is unreachable
2023-11-28 21:50:08.942 OpenTcpPort: TCP Logger connect failed
2023-11-28 21:50:08.942 InitTCP: Failed to connect to the station, waiting 30 seconds before trying again
2023-11-28 21:50:52.615 InitTCP: Connecting to the station
2023-11-28 21:50:52.615 OpenTcpPort: TCP Logger Connect attempt 1
2023-11-28 21:50:53.787 OpenTcpPort: TCP Logger reconnected
2023-11-28 21:50:53.787 InitTCP: Flushing input stream
2023-11-28 21:50:55.827 InitTCP: Sending TEST (1) command
2023-11-28 21:50:58.245 InitTCP: TEST (1) received - '0A-0D-54-45-53-54-0A-0D'
2023-11-28 21:50:58.246 InitTCP: TEST (1) successful
2023-11-28 21:50:58.247 InitTCP: Connection confirmed
2023-11-28 21:50:58.247 Connected OK

[...]

2023-11-28 21:51:19.474 Realtime[2]: Start cycle
2023-11-28 21:51:19.475 Realtime[2]: Creating realtime.txt
2023-11-28 21:51:19.506 Realtime[2]: Creating realtime file - realtimegauges.txt
2023-11-28 21:51:20.302 Realtime[2]: Real time files starting
2023-11-28 21:51:21.244 LOOP: Data - 5: 4C-4F-4F-00-00-00-00-82-74-17-03-4C-CC-02-00-00-9F-00-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-53-FF-FF-FF-FF-FF-FF-FF-00-00-FF-FF-7F-51-00-17-BE-51-00-D6-01-DA-0B-00-00-00-00-00-00-FF-FF-FF-FF-FF-FF-FF-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-4C-03-06-2D-C2-01-20-07-0A-0D-B7-27
2023-11-28 21:51:21.245 LOOP: 5 - Data packet is good
2023-11-28 21:51:21.245 DoWind: latest=0.0, speed=0.0 - Current: gust=0.0, speed=0.0
2023-11-28 21:51:21.245 DoWind: New: gust=0.0, speed=0.0, latest:0.0
2023-11-28 21:51:23.221 LOOP: Data - 6: 4C-4F-4F-00-00-00-00-82-74-17-03-4C-CC-02-00-00-9F-00-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-53-FF-FF-FF-FF-FF-FF-FF-00-00-FF-FF-7F-51-00-17-BE-51-00-D6-01-DA-0B-00-00-00-00-00-00-FF-FF-FF-FF-FF-FF-FF-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-4C-03-06-2D-C2-01-20-07-0A-0D-B7-27
2023-11-28 21:51:23.221 LOOP: 6 - Data packet is good
2023-11-28 21:51:23.222 DoWind: latest=0.0, speed=0.0 - Current: gust=0.0, speed=0.0
2023-11-28 21:51:23.222 DoWind: New: gust=0.0, speed=0.0, latest:0.0
2023-11-28 21:51:23.475 Realtime[3]: Start cycle
2023-11-28 21:51:23.475 Realtime[3]: Warning, a previous cycle is still processing local files. Skipping this interval.
2023-11-28 21:51:23.499 Realtime[3]: End cycle
Hans

https://meteo-wagenborgen.nl
CMX build 3278 ● Ecowitt GW1100/WS80/WH40 ● RPi 3B+ ● Raspberry OS 6.1.21 ● Mono 6.12.0.200
https://meteo-wagenborgen.nl/CMX4/NET8/ (beta)
CMX build 4003+ ● RPi 4B ● RPi OS 6.1.0-rpi7-rpi-v8 aarch64 ● dotnet 8.0.1
bort483
Posts: 31
Joined: Tue 19 Sep 2017 9:16 am
Weather Station: Davis Vantage Pro2
Operating System: Ubuntu

Re: Monthly Log file has stopped updating

Post by bort483 »

It's weird since like I said, the logging issue only began to show up a couple of weeks ago. Before that, everything was working flawlessly. I use WifiLogger inside of a Vue console, and I do remember around that time the device just stopped working for some odd reason and I had to manually take the batteries out of the console and put them back in, unplug/replug, to get it to work again. I'm thinking it *may* be related but I can't be sure.

Also I'm not sure how accurate those logs are, since I've only started to see the other issues since a) I updated Cumulus tonight and b) I enabled data logging and set 'PING escape time (mins)' to '1' shortly after. Now my realtime data isn't uploading for 1 minute or more.
bort483
Posts: 31
Joined: Tue 19 Sep 2017 9:16 am
Weather Station: Davis Vantage Pro2
Operating System: Ubuntu

Re: Monthly Log file has stopped updating

Post by bort483 »

Woohoo, so I went into my Cumulus /data/ folder, removed the culprit line from the Nov23log.txt file (it was full of NULL values), and now my monthly logs are all fixed. Thanks for pointing me in the right direction on that. Now to try and clean up some of those other errors you've pointed out...

edit:

So first up, I've set my Cumulus settings for archive interval to match with my station - 30 minutes, as per the first part of the log file you posted.

I need help with the rest of my data now though which I didn't have an issue with before tonight. :( I suspect it has something to do with the second part of the logs you posted - Cumulus seems to be having trouble connecting to the station itself to pull data from it consistently. Any ideas?

I'm not 100% sure what my disconnect interval should be set to, I've been trial & erroring it but it hasn't seem to have made any difference.
User avatar
PaulMy
Posts: 3744
Joined: Sun 28 Sep 2008 11:54 pm
Weather Station: Davis VP2+ Cumulus1 / CummulusMX
Operating System: Windows8 / Windows10
Location: Komoka, ON Canada
Contact:

Re: Monthly Log file has stopped updating

Post by PaulMy »

Hi,
I'm not 100% sure what my disconnect interval should be set to, I've been trial & erroring it but it hasn't seem to have made any difference.
I use 20 seconds but then I have the WiFiLogger (like the WeatherlinkIP) this is uploading to 8 of the available third-party services at the 5-minute interval.

Here is some early posts by Steve on this.
viewtopic.php?p=29391#p29391
viewtopic.php?p=58208#p58208

Your 30-minute logging is fine but you do loose a lot of data points that you could log. What is the minimum your Weatherlink.com site allows? The usual free plan is 15 minutes and paid subscription can be set at 5-minutes. As Hans mentioned, to avoid issues make sure your WL logging and Cumulus is the same. You can have CumulusMX set your Davis logger interval.

Enjoy,
Paul
Davis Vantage Pro2+
C1 www.komokaweather.com/komokaweather-ca
MX www .komokaweather.com/cumulusmxwll/index.htm
MX www.komokaweather.com/cumulusmx/index.php
MX www.komokaweather.com/cumulusmx/index.html

Image
bort483
Posts: 31
Joined: Tue 19 Sep 2017 9:16 am
Weather Station: Davis Vantage Pro2
Operating System: Ubuntu

Re: Monthly Log file has stopped updating

Post by bort483 »

PaulMy wrote: Tue 28 Nov 2023 2:51 pm Hi,
I'm not 100% sure what my disconnect interval should be set to, I've been trial & erroring it but it hasn't seem to have made any difference.
I use 20 seconds but then I have the WiFiLogger (like the WeatherlinkIP) this is uploading to 8 of the available third-party services at the 5-minute interval.

Here is some early posts by Steve on this.
viewtopic.php?p=29391#p29391
viewtopic.php?p=58208#p58208

Your 30-minute logging is fine but you do loose a lot of data points that you could log. What is the minimum your Weatherlink.com site allows? The usual free plan is 15 minutes and paid subscription can be set at 5-minutes. As Hans mentioned, to avoid issues make sure your WL logging and Cumulus is the same. You can have CumulusMX set your Davis logger interval.

Enjoy,
Paul
Thank you Paul.

Is there a way to see my disconnect interval in my Wifilogger settings?

Also, the option in Cumulus to set the Davis Logger interval to match Cumulus MX interval comes with this disclaimer:

" WARNING: This will clear all data from your logger if it is invoked. If the Davis logger interval does not match the Cumulus interval, set it to match."

And in Wifilogger: "Setting new archive interval will automatically erase whole memory. Do it?" So I'm stuck with 30 minutes?
"
This is so frustrating, and I do believe it has to have something to do with this:

2023-11-28 21:50:08.920 InitTCP: Connecting to the station
2023-11-28 21:50:08.921 OpenTcpPort: TCP Logger Connect attempt 1
2023-11-28 21:50:08.935 OpenTcpPort: Error - Network is unreachable
2023-11-28 21:50:08.938 OpenTcpPort: TCP Logger Connect attempt 2
2023-11-28 21:50:08.939 OpenTcpPort: Error - Network is unreachable

etc
User avatar
PaulMy
Posts: 3744
Joined: Sun 28 Sep 2008 11:54 pm
Weather Station: Davis VP2+ Cumulus1 / CummulusMX
Operating System: Windows8 / Windows10
Location: Komoka, ON Canada
Contact:

Re: Monthly Log file has stopped updating

Post by PaulMy »

Hi,
Is there a way to see my disconnect interval in my Wifilogger settings?
The Disconnect is a Cumulus setting/function and not in WiFiLogger, but my version of WiFiLogger2 v2.42 has a bright orange bar popup at the bottom of the Real Time Data screen saying [PC Software Is Connected] and then goes away so that shows during the connection period.
Also, the option in Cumulus to set the Davis Logger interval to match Cumulus MX interval comes with this disclaimer:
" WARNING: This will clear all data from your logger if it is invoked. If the Davis logger interval does not match the Cumulus interval, set it to match."
And in Wifilogger: "Setting new archive interval will automatically erase whole memory. Do it?" So I'm stuck with 30 minutes?
It is true when the logger is reset it losses the previous data in its memory but as long as you are current with your saved data when you do that it doesn't matter as from then it would keep on logging at the new interval. Those messages are just to make you aware. I presume the same occurs if you change your logger interval directly with Weatherlink.
viewtopic.php?p=98977&sid=2f4571411c0d2 ... 52b#p98977

Also remember shorter period of logging means less days of logging in the logger.

Enjoy,
Paul
Davis Vantage Pro2+
C1 www.komokaweather.com/komokaweather-ca
MX www .komokaweather.com/cumulusmxwll/index.htm
MX www.komokaweather.com/cumulusmx/index.php
MX www.komokaweather.com/cumulusmx/index.html

Image
freddie
Posts: 2406
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: Monthly Log file has stopped updating

Post by freddie »

bort483 wrote: Tue 28 Nov 2023 3:20 pm This is so frustrating, and I do believe it has to have something to do with this:

2023-11-28 21:50:08.920 InitTCP: Connecting to the station
2023-11-28 21:50:08.921 OpenTcpPort: TCP Logger Connect attempt 1
2023-11-28 21:50:08.935 OpenTcpPort: Error - Network is unreachable
2023-11-28 21:50:08.938 OpenTcpPort: TCP Logger Connect attempt 2
2023-11-28 21:50:08.939 OpenTcpPort: Error - Network is unreachable
What this is telling you is that the computer running MX lost connection to your network. Do you connect with WiFi? If you do then perhaps the signal is of marginal strength. If you don't then there is an issue with your network itself.
Freddie
Image
bort483
Posts: 31
Joined: Tue 19 Sep 2017 9:16 am
Weather Station: Davis Vantage Pro2
Operating System: Ubuntu

Re: Monthly Log file has stopped updating

Post by bort483 »

freddie wrote: Tue 28 Nov 2023 5:44 pm
bort483 wrote: Tue 28 Nov 2023 3:20 pm This is so frustrating, and I do believe it has to have something to do with this:

2023-11-28 21:50:08.920 InitTCP: Connecting to the station
2023-11-28 21:50:08.921 OpenTcpPort: TCP Logger Connect attempt 1
2023-11-28 21:50:08.935 OpenTcpPort: Error - Network is unreachable
2023-11-28 21:50:08.938 OpenTcpPort: TCP Logger Connect attempt 2
2023-11-28 21:50:08.939 OpenTcpPort: Error - Network is unreachable
What this is telling you is that the computer running MX lost connection to your network. Do you connect with WiFi? If you do then perhaps the signal is of marginal strength. If you don't then there is an issue with your network itself.
On second look I don't think that's related to my issue as those lines only show up at the very beginning of the log (just as the box is booting up). My issue is ongoing, realtime takes 1min+ to update and FTP is slower than I have it set to as well. Updated log file:
20231129-040114.txt
Box + station console sit right next to the router.
sarat.png
You do not have the required permissions to view the files attached to this post.
AndyKF650
Posts: 684
Joined: Thu 20 Aug 2020 8:35 am
Weather Station: Davis VP2 Plus
Operating System: RPiv4 64bit Linux 12 Bookworm
Location: Jersey Channel Islands
Contact:

Re: Monthly Log file has stopped updating

Post by AndyKF650 »

Just a observation, why is your system time set at 29 June 2021
2023-11-29 04:01:15.299 Mono version : 6.8.0.105 (Debian 6.8.0.105+dfsg-3.2 Tue Jun 29 21:11:52 UTC 2021)
2023-11-29 04:01:15.649 Platform : Unix
2023-11-29 04:01:15.659 OS Description : Unix 5.10.123.64
2023-11-29 04:01:15.661 Current culture: English (United States) [en-US]
I would have thought that it ought to be much closer to 28 November 2023 or 29 November if you are in Australia.
bort483
Posts: 31
Joined: Tue 19 Sep 2017 9:16 am
Weather Station: Davis Vantage Pro2
Operating System: Ubuntu

Re: Monthly Log file has stopped updating

Post by bort483 »

AndyKF650 wrote: Tue 28 Nov 2023 6:25 pm Just a observation, why is your system time set at 29 June 2021
2023-11-29 04:01:15.299 Mono version : 6.8.0.105 (Debian 6.8.0.105+dfsg-3.2 Tue Jun 29 21:11:52 UTC 2021)
2023-11-29 04:01:15.649 Platform : Unix
2023-11-29 04:01:15.659 OS Description : Unix 5.10.123.64
2023-11-29 04:01:15.661 Current culture: English (United States) [en-US]
I would have thought that it ought to be much closer to 28 November 2023 or 29 November if you are in Australia.
Didn't even notice until you pointed it out. :lol: All I use this box for is for running Cumulus and a couple of other things, which I occasionally remotely connect to.
User avatar
HansR
Posts: 5784
Joined: Sat 20 Oct 2012 6:53 am
Weather Station: GW1100 (WS80/WH40)
Operating System: Raspberry OS/Bullseye
Location: Wagenborgen (NL)
Contact:

Re: Monthly Log file has stopped updating

Post by HansR »

AndyKF650 wrote: Tue 28 Nov 2023 6:25 pm Just a observation, why is your system time set at 29 June 2021
2023-11-29 04:01:15.299 Mono version : 6.8.0.105 (Debian 6.8.0.105+dfsg-3.2 Tue Jun 29 21:11:52 UTC 2021)
2023-11-29 04:01:15.649 Platform : Unix
2023-11-29 04:01:15.659 OS Description : Unix 5.10.123.64
2023-11-29 04:01:15.661 Current culture: English (United States) [en-US]
I would have thought that it ought to be much closer to 28 November 2023 or 29 November if you are in Australia.
That is not the system time (which is the timestamp at the start of a line) but it is Debian OS generation timestamp.
Having said that: @bort483: updating the system and mono would do no harm. Mono is at 6.12.0.200 and Linux is at 6.1.21-v7+
Hans

https://meteo-wagenborgen.nl
CMX build 3278 ● Ecowitt GW1100/WS80/WH40 ● RPi 3B+ ● Raspberry OS 6.1.21 ● Mono 6.12.0.200
https://meteo-wagenborgen.nl/CMX4/NET8/ (beta)
CMX build 4003+ ● RPi 4B ● RPi OS 6.1.0-rpi7-rpi-v8 aarch64 ● dotnet 8.0.1
User avatar
PaulMy
Posts: 3744
Joined: Sun 28 Sep 2008 11:54 pm
Weather Station: Davis VP2+ Cumulus1 / CummulusMX
Operating System: Windows8 / Windows10
Location: Komoka, ON Canada
Contact:

Re: Monthly Log file has stopped updating

Post by PaulMy »

Hi,
Your status page shows that realtime is not always current https://maryborough-wx.xyz/wxstatus.php
Your realtime seems to be set at 5 seconds but is not updating for usually more than 1 or 2 minutes or more

Code: Select all

29/11/23 05:12:49 21.8 85 19.1 0 0 194 0.0 10.4 1009.6 SSW 0 km/h C hPa mm 15.4 +0.3 95.0 605.4 7.0 25.8 74 21.8 +0.1 25.1 11:41 21.4 23:40 3 15:18 11 15:11 1012.8 09:00 1008.3 02:49 3.27.1 3263 3 21.8 28.5 0.0 0.00 0 194 0.0 2 1 0 SSW 1077 ft 25.0 0.0 6 0 24.3
and next update

Code: Select all

29/11/23 05:14:44 21.8 85 19.2 0 0 194 0.0 10.4 1009.5 SSW 0 km/h C hPa mm 15.4 +0.3 95.0 605.4 7.0 25.9 74 21.8 +0.1 25.1 11:41 21.4 23:40 3 15:18 11 15:11 1012.8 09:00 1008.3 02:49 3.27.1 3263 2 21.8 28.6 0.0 0.00 0 194 0.0 2 1 0 SSW 1078 ft 25.1 0.0 8 0 24.4
your diag logs show

Code: Select all

2023-11-29 04:02:24.361 Realtime[0]: Not all data is ready, aborting process

2023-11-29 04:02:29.353 Realtime[1]: Not all data is ready, aborting process
2023-11-29 04:02:34.355 Realtime[2]: Start cycle
2023-11-29 04:02:34.356 Realtime[2]: Creating realtime.txt

2023-11-29 04:02:39.355 Realtime[3]: Start cycle
2023-11-29 04:02:39.355 Realtime[3]: Warning, a previous cycle is still processing local files. Skipping this interval.
2023-11-29 04:02:39.380 Realtime[3]: End cycle

2023-11-29 04:02:34.404 Realtime[2]: Creating realtime file - realtimegauges.txt
2023-11-29 04:03:24.356 Realtime[12]: Start cycle
2023-11-29 04:03:24.356 Realtime[12]: Warning, a previous cycle is still processing local files. Skipping this interval.
2023-11-29 04:03:24.357 Realtime[12]: End cycle
2023-11-29 04:03:25.891 FTP[2]: Error uploading /domains/maryborough-wx.xyz/public_html/realtimegauges.txt : Error while uploading the file to the server. See InnerException for more info.
2023-11-29 04:03:25.892 FTP[2]: Inner Exception: Code: 550 Message: /domains/maryborough-wx.xyz/public_html/realtimegauges.txttmp: Temporary hidden file /domains/maryborough-wx.xyz/public_html/.in.realtimegauges.txttmp. already exists
2023-11-29 04:03:25.892 Realtime[2]: Real time files complete
https://maryborough-wx.xyz/realtime.txt
https://maryborough-wx.xyz/realtimegauges.txt
I am just pointing out, but don't know what to suggest to fix it.
So since the 10th of November, my monthly data logs have stopped uploading to Cumulus (however everything else like real-time, dayfile, uploading to my website etc works fine Essentially, this is just leaving me with a blank gap in my weather history from the 10th (which outputs in my NOAA data). I can't remember anything changed on this day so I have no idea how or why this happened. I would be extremely grateful if anyone could help me with this and maybe provide some info on how I might go about getting it working again. The box it runs on is scheduled to reboot at 4am everyday so obviously a simple reboot hasn't been enough to fix it. Thanks.
Strange that your status page shows NOAA update is current and that your NOAA page is only up to November 10 https://maryborough-wx.xyz/Reports/NOAAMO1123.txt

Did you by chance change to PHP Upload and forgot to change the NOAA Upload folder path?

Enjoy,
Paul
Davis Vantage Pro2+
C1 www.komokaweather.com/komokaweather-ca
MX www .komokaweather.com/cumulusmxwll/index.htm
MX www.komokaweather.com/cumulusmx/index.php
MX www.komokaweather.com/cumulusmx/index.html

Image
Post Reply