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

Upload now broken 3.24.2

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

AndyKF650
Posts: 818
Joined: Thu 20 Aug 2020 8:35 am
Weather Station: Davis VP2 Plus
Operating System: RPiv5B 64bit Linux 12 Bookworm
Location: Jersey Channel Islands
Contact:

Re: Upload now broken 3.24.2

Post by AndyKF650 »

Hi there

I tried this fix and once I had loaded it in the correct place it worked perfectly. I have attached my MXDiags file for information, the line at 448 was when the new file was in the wrong place and hence not working, then at 465 to 472 shows the graph file transfers as expected.
You do not have the required permissions to view the files attached to this post.
User avatar
HansR
Posts: 6926
Joined: Sat 20 Oct 2012 6:53 am
Weather Station: GW1100 (WS80/WH40)
Operating System: Raspberry OS/Bookworm
Location: Wagenborgen (NL)
Contact:

Re: Upload now broken 3.24.2

Post by HansR »

I have no error in the debug logs from yesterday evening until now (there were two restarts included.

I did notice however, that the log from Andy (see previous post) does have those errors e.g.:

Code: Select all

2023-03-15 18:16:12.696 Normal running
2023-03-15 18:16:14.852 SendLoopCommand: Starting - LOOP 50
2023-03-15 18:17:31.250 LoadDayFile: Attempting to load the day file
2023-03-15 18:17:32.400 LoadDayFile: Loaded 3702 entries to recent daily data list
2023-03-15 18:17:43.880 Upload Now: Specified argument was out of the range of valid values.
Parameter name: start
2023-03-15 18:17:48.214 Upload Now: Specified argument was out of the range of valid values.
Parameter name: start
2023-03-15 18:17:49.311 SendLoopCommand: Starting - LPS 2 1
2023-03-15 18:17:49.381 SendLoopCommand: Starting - LOOP 50
2023-03-15 18:17:51.318 Upload Now: Specified argument was out of the range of valid values.
Parameter name: start
2023-03-15 18:19:27.310 SendLoopCommand: Starting - LPS 2 1
2023-03-15 18:19:27.380 SendLoopCommand: Starting - LOOP 50
2023-03-15 18:19:50.906 Ecowitt Gateway uptime = 353982 secs - 4.02:19:42
2023-03-15 18:20:00.284 DoLogFile: Writing log entry for 15/03/2023 18:20:00
2023-03-15 18:20:00.289 DoLogFile: log entry for 15/03/2023 18:20:00 written
2023-03-15 18:20:00.310 Writing today.ini, LastUpdateTime = 15/03/2023 18:20:00 raindaystart = 158.8 rain counter = 158.8
And searching the code for a start argument leads me to believe it has something to do with int.parse or string.parse statements somewhere (as that is where the start argument is present).

I switch debug off now and expect that will generate those errors again, apparently it has some timing component in it.
It does not seem to have immediate consequences but on the other hand it does not look trustworthy.
Hans

https://meteo-wagenborgen.nl
CMX build 4070+ ● RPi 4B ● Linux 6.6.62+rpt-rpi-v8 aarch64 (bookworm) ● dotnet 8.0.1
BlueSky: https://bsky.app/profile/wagenborgenwx.bsky.social
Post Reply