4063 - local wind gauges not working

[AndyO2]

upgraded to 4063 from prior version, on local web server DASHBOARD the 3 x wind gauges are all zero'd / blank, though the 'wind speeds' box is updating as expected (every second or so).
The 'now' page is working as expected, the 'GAUGES' page is completely broken (not updating).
Running Instromet station on Debian VM, using serial passthrough. Separate website updating fine. Will likely roll back.

[HansR]

Please post MXdiags with DEBUG on before you roll back

[AndyO2]

Please post MXdiags with DEBUG on before you roll back

ok I can see that the 202412log.txt format changes at the upgrade. MXDiags is complaining at start up about these lines (from 05/12/2024 at 08:40hrs) a bunch of zeros are dropped replaced with null entry e.g.
28,0,0,0,
becomes
28,,,

& log file after restart this morning:

2024-12-07 09:14:59.092 Start reading history data
2024-12-07 09:14:59.092 Loading last N hour data from data logs: 07/12/2024 09:10:00
2024-12-07 09:14:59.095 LoadRecent: Attempting to load 7 days of entries to recent data list
2024-12-07 09:14:59.423 Error parsing log file record: The input string '' was not in a correct format.
2024-12-07 09:14:59.424 LoadRecent: Error at line 1258 of data/202412log.txt : The input string '' was not in a correct format.
2024-12-07 09:14:59.424 Please edit the file to correct the error
2024-12-07 09:14:59.424 Error parsing log file record: The input string '' was not in a correct format.
2024-12-07 09:14:59.425 LoadRecent: Error at line 1259 of data/202412log.txt : The input string '' was not in a correct format.
2024-12-07 09:14:59.425 Please edit the file to correct the error
2024-12-07 09:14:59.425 Error parsing log file record: The input string '' was not in a correct format.
2024-12-07 09:14:59.425 LoadRecent: Error at line 1260 of data/202412log.txt : The input string '' was not in a correct format.
2024-12-07 09:14:59.425 Please edit the file to correct the error
2024-12-07 09:14:59.425 Error parsing log file record: The input string '' was not in a correct format.
2024-12-07 09:14:59.425 LoadRecent: Error at line 1261 of data/202412log.txt : The input string '' was not in a correct format.
2024-12-07 09:14:59.425 Please edit the file to correct the error
2024-12-07 09:14:59.426 Error parsing log file record: The input string '' was not in a correct format.
2024-12-07 09:14:59.426 LoadRecent: Error at line 1262 of data/202412log.txt : The input string '' was not in a correct format.
2024-12-07 09:14:59.426 Please edit the file to correct the error
2024-12-07 09:14:59.426 Error parsing log file record: The input string '' was not in a correct format.
2024-12-07 09:14:59.426 LoadRecent: Error at line 1263 of data/202412log.txt : The input string '' was not in a correct format.
2024-12-07 09:14:59.426 Please edit the file to correct the error
2024-12-07 09:14:59.426 Error parsing log file record: The input string '' was not in a correct format.
2024-12-07 09:14:59.426 LoadRecent: Error at line 1264 of data/202412log.txt : The input string '' was not in a correct format.
2024-12-07 09:14:59.426 Please edit the file to correct the error
2024-12-07 09:14:59.427 Error parsing log file record: The input string '' was not in a correct format.
2024-12-07 09:14:59.427 LoadRecent: Error at line 1265 of data/202412log.txt : The input string '' was not in a correct format.
2024-12-07 09:14:59.427 Please edit the file to correct the error
2024-12-07 09:14:59.427 Error parsing log file record: The input string '' was not in a correct format.
2024-12-07 09:14:59.427 LoadRecent: Error at line 1266 of data/202412log.txt : The input string '' was not in a correct format.
2024-12-07 09:14:59.427 Please edit the file to correct the error
2024-12-07 09:14:59.427 Error parsing log file record: The input string '' was not in a correct format.
2024-12-07 09:14:59.427 LoadRecent: Error at line 1267 of data/202412log.txt : The input string '' was not in a correct format.
2024-12-07 09:14:59.427 Please edit the file to correct the error
2024-12-07 09:14:59.427 LoadRecent: Too many errors reading data/202412log.txt - aborting load of graph data
2024-12-07 09:14:59.428 LoadRecent: Loaded 0 of 0 new entries to recent database
2024-12-07 09:14:59.435 LoadRecentAqFromDataLogs: Attempting to load 7 days of entries to Air Quality recent data
2024-12-07 09:14:59.644 LoadRecentAqFromDataLogs: Loaded 527 new entries to recent database

[HansR]

Thanks for the info but that is not the MXdiags logfile.
Could you post that please?

[AndyO2]

I'd rolled back. I upgraded yesterday to 4064 (following the instructions provided by Mark e.g. using the Zip file to create a new folder, then copying in the ~5 files / directory contents) - again, no activity on the wind gauges on the native web server - I grabbed the attached MXdiags file & rolled back again. Happy to do more testing.

[HansR]

I'd rolled back. I upgraded yesterday to 4064 (following the instructions provided by Mark e.g. using the Zip file to create a new folder, then copying in the ~5 files / directory contents) - again, no activity on the wind gauges on the native web server - I grabbed the attached MXdiags file & rolled back again. Happy to do more testing.

Since there are no errors in the MXdiags (apart from some AirLink related 400 message which in this seems irrelevant).
Since your website gauges are working fine.

As only the gauges in the local interface are not working I am inclined to say it is an installation issue related to the interface. Assuming you use the standard interface (Question: not the AI2?) you need to focus on the installation of the interface directory, specifically the lib/steelseries.

First start with checking the MD5 checksum of the distribution. Question: is that OK?
Then redo the installation. Question: Do you have a link to Marks instruction? I am not sure what you are pointing at.

In the first post you say:

on local web server DASHBOARD the 3 x wind gauges are all zero'd

.
Question: What local webserver do you mean? Or is it just your browser pointing to the <ip>:8998 local interface?

NOTE: when only the gauges do not work but all data is stored OK - there is no indication it is not - there is no need to roll back, we just need to find out why the gauges don't work.

[AndyO2]

Hans- correct - seen when my browser is pointing to the <ip>:8998 local interface (related Web server e.g. where I'm uploading via SFTP ) works fine.

[HansR]

And the other questions/answers?

[HansR]

Please see the reaction of @mcrossley, I think it is the same issue so we wait for this release.
viewtopic.php?p=187393#p187393

[AndyO2]

Ah - yes, that looks similar. I'll hold off upgrading until there's a release that likely fixes this.

in answer to the other questions
Ha. sorry.
This is using the standard interface
Will check the MD5 hashes (for both 4063 & 4064 as the same issue now seen with both releases)


Instructions for upgrading v.4 as here: viewtopic.php?t=22051, bottom of the thread (under "Upgrading version 4"!)
For my upgrade to 4063 I just unzipped over what was there (with the CumulusMX service stopped), for the upgrade to 4064 I followed these instructions

& agreed, the errors relating to the Davis WL should not be relevant here, as the internal web server gauges don't refer to any of these (though probably something for me to investigate).

[HansR]

Ok and thanks for answering
Now we wait