rpi-CumulusMX-lite-3.28.0_X64

[Safety]

Hi All,
I have installed the Raspberry Pi Lite image rpi-CumulusMX-lite-3.28.0_X64.zip file. To make the install easier for me I installed the image on a new USB memory stick knowing that I would eventually need to reinstall it on to my current weather SSD. As all went well, I took a copy of the data folder then erased my weather SSD drive. I then reinstalled the image on to the SSD to find this time that for some reason the rain was showing 124mm as was the "This Month" and "This year" fields.
I reloaded the image again onto the SSD just in case an error had crept in however found that the rain error was still apparent.
Given this error I replaced the data folder with the one from my previous SSD working Raspberry Pi drive.
By undertaking this action the programme on the SSD drive would not display data so I used "sudo systemctl status cumulusmx" to find cumulusmx systemd[1]: Starting CumulusMX service...
cumulusmx systemd[1]: Started CumulusMX service.
cumulusmx mono CumulusMX.exe: Index was outside the bounds of the array.
Could someone enlighten me on how to correct the above issues?

I am using a Raspberry Pi 4, Weather ENVOY and Weatherlink

[mcrossley]

Please zip up and attach the MXdiags log files

[Safety]

Hi Mark
And thank you for helping with this issue.
As requested I have attached the folder.
Best Regards

[mcrossley]

It's a bit confusing as to what you have done and where you are up to.

But you need to copy the entire /data and the Cumulus.ini file from the old install to the new install.

Be careful of any resulting permissions issues - make sure the account MX is going to run under has write access to all the files.

Your log files show you have a mismatch between your MX logging period and your stations.

Code: Select all

2024-02-20 11:49:07.110 CheckLoggerInterval: ** WARNING: Your station logger interval 15 mins does not match your Cumulus MX logging interval 10 mins

This causes the logger to dump its entire contents to MX at start-up which is very slow.

And a one point you had a serious mismatch between the computer clock and the Davis Clock

Code: Select all

2024-02-20 11:49:06.326 Console clock: 20/02/2024 06:13:36
2024-02-20 11:49:06.328 Console clock: Console is 20130 seconds adrift but automatic setting is disabled - you should set the clock manually.

And another log shows 54 duplicate entires in your dayfile.txt

Code: Select all

2024-02-21 16:15:25.589 ERROR: Duplicate entry in dayfile for 21/01/2010
2024-02-21 16:15:25.694 ERROR: Duplicate entry in dayfile for 30/05/2010
2024-02-21 16:15:25.694 ERROR: Duplicate entry in dayfile for 31/05/2010
2024-02-21 16:15:25.695 ERROR: Duplicate entry in dayfile for 01/06/2010
2024-02-21 16:15:25.695 ERROR: Duplicate entry in dayfile for 02/06/2010
2024-02-21 16:15:25.695 ERROR: Duplicate entry in dayfile for 17/04/2011
2024-02-21 16:15:25.696 ERROR: Duplicate entry in dayfile for 18/04/2011
2024-02-21 16:15:25.697 ERROR: Duplicate entry in dayfile for 19/04/2011
2024-02-21 16:15:25.697 ERROR: Duplicate entry in dayfile for 20/04/2011
2024-02-21 16:15:25.698 ERROR: Duplicate entry in dayfile for 21/04/2011
2024-02-21 16:15:25.698 ERROR: Duplicate entry in dayfile for 22/04/2011
2024-02-21 16:15:25.699 ERROR: Duplicate entry in dayfile for 23/04/2011
2024-02-21 16:15:25.699 ERROR: Duplicate entry in dayfile for 24/04/2011
2024-02-21 16:15:25.700 ERROR: Duplicate entry in dayfile for 25/04/2011
2024-02-21 16:15:25.700 ERROR: Duplicate entry in dayfile for 26/04/2011
2024-02-21 16:15:25.701 ERROR: Duplicate entry in dayfile for 27/04/2011
2024-02-21 16:15:25.701 ERROR: Duplicate entry in dayfile for 28/04/2011
2024-02-21 16:15:25.702 ERROR: Duplicate entry in dayfile for 29/04/2011
2024-02-21 16:15:25.704 ERROR: Duplicate entry in dayfile for 02/06/2010
2024-02-21 16:15:25.704 ERROR: Duplicate entry in dayfile for 03/06/2010
2024-02-21 16:15:25.705 ERROR: Duplicate entry in dayfile for 04/06/2010
2024-02-21 16:15:25.705 ERROR: Duplicate entry in dayfile for 05/06/2010
2024-02-21 16:15:25.706 ERROR: Duplicate entry in dayfile for 06/06/2010
2024-02-21 16:15:25.706 ERROR: Duplicate entry in dayfile for 07/06/2010
2024-02-21 16:15:25.707 ERROR: Duplicate entry in dayfile for 08/06/2010
2024-02-21 16:15:25.707 ERROR: Duplicate entry in dayfile for 09/06/2010
2024-02-21 16:15:25.708 ERROR: Duplicate entry in dayfile for 10/06/2010
2024-02-21 16:15:25.708 ERROR: Duplicate entry in dayfile for 25/04/2011
2024-02-21 16:15:25.709 ERROR: Duplicate entry in dayfile for 26/04/2011
2024-02-21 16:15:25.709 ERROR: Duplicate entry in dayfile for 27/04/2011
2024-02-21 16:15:25.710 ERROR: Duplicate entry in dayfile for 28/04/2011
2024-02-21 16:15:25.710 ERROR: Duplicate entry in dayfile for 29/04/2011
2024-02-21 16:15:25.711 ERROR: Duplicate entry in dayfile for 30/04/2011
2024-02-21 16:15:25.712 ERROR: Duplicate entry in dayfile for 01/05/2011
2024-02-21 16:15:25.712 ERROR: Duplicate entry in dayfile for 02/05/2011
2024-02-21 16:15:25.713 ERROR: Duplicate entry in dayfile for 03/05/2011
2024-02-21 16:15:25.716 ERROR: Duplicate entry in dayfile for 12/06/2010
2024-02-21 16:15:26.147 ERROR: Duplicate entry in dayfile for 12/06/2013
2024-02-21 16:15:26.148 ERROR: Duplicate entry in dayfile for 13/06/2013
2024-02-21 16:15:26.149 ERROR: Duplicate entry in dayfile for 14/06/2013
2024-02-21 16:15:27.973 ERROR: Duplicate entry in dayfile for 27/12/2017
2024-02-21 16:15:27.974 ERROR: Duplicate entry in dayfile for 27/12/2017
2024-02-21 16:15:28.466 ERROR: Duplicate entry in dayfile for 20/12/2018
2024-02-21 16:15:28.580 ERROR: Duplicate entry in dayfile for 01/03/2019
2024-02-21 16:15:28.844 ERROR: Duplicate entry in dayfile for 02/09/2019
2024-02-21 16:15:28.998 ERROR: Duplicate entry in dayfile for 04/12/2019
2024-02-21 16:15:29.064 ERROR: Duplicate entry in dayfile for 15/01/2020
2024-02-21 16:15:29.186 ERROR: Duplicate entry in dayfile for 26/03/2020
2024-02-21 16:15:29.188 ERROR: Duplicate entry in dayfile for 26/03/2020
2024-02-21 16:15:29.260 ERROR: Duplicate entry in dayfile for 06/05/2020
2024-02-21 16:15:29.353 ERROR: Duplicate entry in dayfile for 10/07/2020
2024-02-21 16:15:29.355 ERROR: Duplicate entry in dayfile for 11/07/2020
2024-02-21 16:15:29.431 ERROR: Duplicate entry in dayfile for 22/08/2020
2024-02-21 16:15:29.770 ERROR: Duplicate entry in dayfile for 21/02/2021

I think a deep breath and start again restoring /data and cumulus.ini

[Safety]

Hi mcrossley,

Thank you for your feedback I will get on with your suggestion.
On the topic of mismatching the time (regarding computer clock and the Davis Clock) does both the Pi / MX & weatherlink IP take it's time reference from the Network Time Protocol ?

Best Regards

[mcrossley]

The rPi uses NTP, and unless you add one does not have a hardware real-time clock (RTC) to keep the time when you reboot/power off. It will restart with the last time it had when it shut down until it can connect to an NTP server.

CMX takes its time from the rPi.

So you should not restart CMX straight away after the rPi boots, you need to wait until the network is up and NTP has synchronised***. The service install waits for the network to initialise, but it's a well to add a further start-up delay and/or PING to the CMX config to make sure the time is set before CMX starts to read the station.

Or as I do, add a RTC module to my rPis that run CMX.

[Safety]

Hi again

So, I had a clean Installation to work with I wiped my SSD and reinstalled the current PI image again.
Thus, all folder / files are default, however, the current rain reading has over 130 mm display as does the Month/Year fields. Hence my question of why this error? I have attached the current MXdiags folder for your reference.

Thank you for the advice regarding the Time issue.
Regarding this topic, I have seen in the log files a statement in the time adrift line item that "automatic setting is disabled" how do I enable this, This time I have set the time of the wheatherlink IP / Envory 6314 via weather link software V 6.0.5.?

Regards

[Safety]

Folder attached this time.

[mcrossley]

Slightly confusing, you have two log files in there the first from the 5th Feb, that looks like a clean start with no Cumus.ini, and you set the station type. Is that an old log left in error?

The other log does not see the /data files from your previous install, so is effectively starting again.

You must restore cumulus.ini and ALL the files in your /data folder from your previous install, otherwise you are starting again with a clean install.

Can you list the contents of the /data folder you are restoring please.

[Safety]

Hi Mark,
As I implied in my message my objective was to build a clean copy to start with and then go on to move my data folder and cumulus.ini into the know good file structure.
So, the files I sent you are associated with the clean build. No left overs from a previous build.

I have now removed the duplicate from the dayfile.txt file (found them in the mater) moved the data folder and cumulus.ini across into the file structure that I hoped would show correct data. Unfortunately, using the "sudo systemctl status cumulusmx" command still shows the following error "cumulusmx mono CumulusMX.exe: Index was outside the bounds of the array" and MX will not show any data in its default screen.

As requested, I have attached the structure of my data folder and the log files for the build that will not display data and has the "mono" error message.

[mcrossley]

As there are no errors in either the log file or the console there's not a lot I can say. An uncaught exception would normally be logged in the MXdiag file.

Switch on debug logging and post the MXdiags file again.

Have you tried running CMX interactively from the command prompt?

[Safety]

Mark,Good news.

Given my current problem of the mono error and data not being displayed on the MX default screen in my view had to be associated with the information in the files in my data folder. I decided to remove the February 24 txt file, once MX was restarted and I run the "sudo systemctl status cumulusmx" command I found that the mono error was not displayed and data started being displayed.

The next stage was to replace the file with groups of line items of data until I found the line item that was at fault, this I did and all is working OK now.

Thank you for the pointers you have provided me.

Best Regards

[mcrossley]

Glad you got it working.