Page 2 of 3
Re: Problem with the records menu
Posted: Fri 12 Apr 2024 12:55 pm
by HansR
You did not turn debug on as I asked and this is a rotated logfile which means I cannot see how CMX started.
So again: pleas switch debug on, restart CMX and show the records page in the interface. And do it in that order.
The purpose of these actions, in case you m ay wonder, is to get information in the logfile which may say something about the record issue. Not guaranteed, but if any, it will show.
And those FTP errors do not seem right. However it does not say anything about records.
With continuous errors like this, a restart with debug on always is useful. Before you restart: check your FTP credentials!
Re: Problem with the records menu
Posted: Sat 13 Apr 2024 9:08 am
by rchi
HansR wrote: ↑Fri 12 Apr 2024 12:55 pm
So again: pleas switch debug on, restart CMX and show the records page in the interface. And do it in that order.
So, I had never activated these options but if they are these, I found them already active.
I read somewhere that you should put a file called debug.log in the same location as the executable and I put it but it doesn't seem to get populated even after restarting cumulus...
Re: Problem with the records menu
Posted: Sat 13 Apr 2024 9:58 am
by HansR
Those are the log options, Yes.
You may switch off data logging.
You will find your logfile in the MXdiags directory, nothing to do with debug.log in the executable directory.
Re: Problem with the records menu
Posted: Sat 13 Apr 2024 10:11 am
by water01
To be clear the log files are in the MXDiags folder and called 202404xx-xxxxxx.txt.
They can get quite large (20MB) so you may have to zip them in order to attach them to your post.
If you set the logging options, close CMX and then reload it, the one will want to see is the latest dated file in that format in MXDiags folder after you have run CMX long enough to allow it to run at least once through it's upload cycle (the time in minutes you set in Normal Interval Settings).
Re: Problem with the records menu
Posted: Sat 13 Apr 2024 11:53 am
by rchi
ok I think we're there; Attached is the latest log file produced of approximately 1 Mb. There are those FTP errors that continue but they are not due to login errors because the FTP data is correct and in fact the NOAA reports are recorded regularly... We hope to resolve it in the meantime. I wish you a great weekend and always thanks for your help. .
Re: Problem with the records menu
Posted: Sat 13 Apr 2024 12:35 pm
by freddie
Records start date looks correct:
Code: Select all
2024-04-13 12:04:53.080 Cumulus start date Parsed: 2021-09-29
Looks like there is some configuration missing. Have you copied across the entire contents of the data folder from your old installation? This should include all the .ini files, as well as the monthly logs and dayfile.
Your networking appears incorrectly set up on your host - a DNS server is not specified by the looks:
Code: Select all
2024-04-13 12:04:54.177 Failed to get the latest build version from GitHub - Exception Type: System.Net.Http.HttpRequestException
Message: No such host is known
Code: Select all
2024-04-13 12:04:56.910 RealtimeFTPLogin: Error connecting ftp - Could not resolve host 'ftp.robertochimenti.it'
Your Cumulus logging interval is different to your station's logging interval:
Code: Select all
2024-04-13 12:04:55.644 Warning, your console logging interval (30 mins) does not match the Cumulus logging interval (10 mins)
This has implications when Cumulus attempts to read your station's logger.
Re: Problem with the records menu
Posted: Sat 13 Apr 2024 2:15 pm
by HansR
freddie wrote: ↑Sat 13 Apr 2024 12:35 pm
Looks like there is some configuration missing. Have you copied across the entire contents of the data folder from your old installation? This should include all the .ini files, as well as the monthly logs and dayfile.
From what do you draw that conclusion @freddie? It simply reads the inifiles without any issue as can bee read from the logfile:
2024-04-13 12:04:54.636 ET today = 0.00
2024-04-13 12:04:54.638 ReadTodayfile: Rain day start = 2627.7
2024-04-13 12:04:54.638 ReadTodayfile: set initialiseRainCounterOnFirstData false
2024-04-13 12:04:54.649 /opt/CumulusMX/data/alltime.ini
2024-04-13 12:04:54.651 Alltime.ini file read
2024-04-13 12:04:54.670 MonthlyAlltime.ini file read
2024-04-13 12:04:54.680 Month.ini file read
2024-04-13 12:04:54.690 Year.ini file read
2024-04-13 12:04:54.691 LoadDayFile: Attempting to load the day file
2024-04-13 12:04:54.935 LoadDayFile: Dayfile parse = 241 ms
2024-04-13 12:04:54.936 LoadDayFile: Loaded 888 entries to recent daily data list
2024-04-13 12:04:54.938 Finding raintoday from logfile data/Apr24log.txt
2024-04-13 12:04:54.938 Expecting listsep=, decimal=.
freddie wrote: ↑Sat 13 Apr 2024 12:35 pm
Your networking appears incorrectly set up on your host - a DNS server is not specified by the looks:
Code: Select all
2024-04-13 12:04:54.177 Failed to get the latest build version from GitHub - Exception Type: System.Net.Http.HttpRequestException
Message: No such host is known
Code: Select all
2024-04-13 12:04:56.910 RealtimeFTPLogin: Error connecting ftp - Could not resolve host 'ftp.robertochimenti.it'
Indeed, I think this needs to be solved first before continuing with the records issue.
@rchi: you use CMX v.3.25.0 build 3241, try the latest CMX v3 release (Cumulus MX v3.28.6 build 3283, 21-March-2024). The FTP libraries have been upped a bit afaik.
freddie wrote: ↑Sat 13 Apr 2024 12:35 pm
Your Cumulus logging interval is different to your station's logging interval:
Code: Select all
2024-04-13 12:04:55.644 Warning, your console logging interval (30 mins) does not match the Cumulus logging interval (10 mins)
This has implications when Cumulus attempts to read your station's logger.
@rchi: Indeed but I don't think this has anything to do with the networking issue nor with the records issue.
Best to make the intervals equal though.
Re: Problem with the records menu
Posted: Sat 13 Apr 2024 2:27 pm
by freddie
HansR wrote: ↑Sat 13 Apr 2024 2:15 pm
freddie wrote: ↑Sat 13 Apr 2024 12:35 pm
Looks like there is some configuration missing. Have you copied across the entire contents of the data folder from your old installation? This should include all the .ini files, as well as the monthly logs and dayfile.
From what do you draw that conclusion @freddie? It simply reads the inifiles without any issue as can bee read from the logfile:
2024-04-13 12:04:54.636 ET today = 0.00
2024-04-13 12:04:54.638 ReadTodayfile: Rain day start = 2627.7
2024-04-13 12:04:54.638 ReadTodayfile: set initialiseRainCounterOnFirstData false
2024-04-13 12:04:54.649 /opt/CumulusMX/data/alltime.ini
2024-04-13 12:04:54.651 Alltime.ini file read
2024-04-13 12:04:54.670 MonthlyAlltime.ini file read
2024-04-13 12:04:54.680 Month.ini file read
2024-04-13 12:04:54.690 Year.ini file read
2024-04-13 12:04:54.691 LoadDayFile: Attempting to load the day file
2024-04-13 12:04:54.935 LoadDayFile: Dayfile parse = 241 ms
2024-04-13 12:04:54.936 LoadDayFile: Loaded 888 entries to recent daily data list
2024-04-13 12:04:54.938 Finding raintoday from logfile data/Apr24log.txt
2024-04-13 12:04:54.938 Expecting listsep=, decimal=.
@hansr true - which implies the inifiles don't contain the data specifying the older records. Hence my comment about copying all the data files from the old location.
Re: Problem with the records menu
Posted: Sat 13 Apr 2024 2:39 pm
by HansR
freddie wrote: ↑Sat 13 Apr 2024 2:27 pm
@hansr true - which implies the inifiles don't contain the data specifying the older records. Hence my comment about copying all the data files from the old location.
I seriously don't get your point. My own logfile says the same:
Code: Select all
2024-04-13 09:07:02.385 ReadTodayFile: Last update time from today.ini: 13-04-2024 09:05:00
2024-04-13 09:07:02.386 ReadTodayFile: Date = 13-04-2024, LastUpdateTime = 13-04-2024 09:05:00, Month = 4
2024-04-13 09:07:02.389 ReadTodayFile: ET today = 0,13
2024-04-13 09:07:02.393 ReadTodayfile: Rain day start: 170,6000, midnight counter: 170,6000, last counter: 170,6000
2024-04-13 09:07:02.425 Alltime.ini file read
2024-04-13 09:07:02.561 MonthlyAlltime.ini file read
2024-04-13 09:07:02.581 Month.ini file read
2024-04-13 09:07:02.602 Year.ini file read
2024-04-13 09:07:02.652 LoadDayFile: Attempting to load the day file
against rchi's file (an older version so other logging):
Code: Select all
2024-04-13 12:04:54.638 ReadTodayfile: Rain day start = 2627.7
2024-04-13 12:04:54.638 ReadTodayfile: set initialiseRainCounterOnFirstData false
2024-04-13 12:04:54.649 /opt/CumulusMX/data/alltime.ini
2024-04-13 12:04:54.651 Alltime.ini file read
2024-04-13 12:04:54.670 MonthlyAlltime.ini file read
2024-04-13 12:04:54.680 Month.ini file read
2024-04-13 12:04:54.690 Year.ini file read
2024-04-13 12:04:54.691 LoadDayFile: Attempting to load the day file
2024-04-13 12:04:54.935 LoadDayFile: Dayfile parse = 241 ms
2024-04-13 12:04:54.936 LoadDayFile: Loaded 888 entries to recent daily data list
So the logfile simply states it is reading the file, no data whatsoever is shown. You can't draw that conclusion, and that question has already been asked and positively been answered (all files were copied)
I invite @rchi to post e.g. his
alltime.ini file to see what the contents is.
Re: Problem with the records menu
Posted: Sat 13 Apr 2024 2:54 pm
by freddie
@hansr I'm going with the assumption that CMX can read the inifiles containing the record data - as we see no errors in the log, and record data for April is shown in the screenshots. Therefore the historic record data from the old installation can't be in the inifiles that are being read.
Re: Problem with the records menu
Posted: Sat 13 Apr 2024 3:04 pm
by HansR
Ok, skip the post of the current inifile and post the original before install/copying.
Re: Problem with the records menu
Posted: Sat 13 Apr 2024 3:31 pm
by water01
I would agree with Freddie. It looks like he started MX before he copied all the .ini files and data files. Hence when MX starts it finds only April Data. If he copies ALL the .ini files and data files over the new Data folder I think that the missing data will appear.
Re: Problem with the records menu
Posted: Sat 13 Apr 2024 3:41 pm
by HansR
Yes, i understand it now... Agreed
Re: Problem with the records menu
Posted: Sat 13 Apr 2024 6:34 pm
by rchi
HansR wrote: ↑Sat 13 Apr 2024 2:39 pm
freddie wrote: ↑Sat 13 Apr 2024 2:27 pm
@hansr true - which implies the inifiles don't contain the data specifying the older records. Hence my comment about copying all the data files from the old location.
So the logfile simply states it is reading the file, no data whatsoever is shown. You can't draw that conclusion, and that question has already been asked and positively been answered (all files were copied)
I invite @rchi to post e.g. his
alltime.ini file to see what the contents is.
Here are the alltime files attached; I opened them too and saw that they only contain data for 2024...
At this point I would have liked to see the same files in CumumulusMx 3.9.1 that I would like to migrate to RB 4; but these files are not there in the old station (the data folder is empty and in the CUmulusMX directory they are not there), yet the historical data shown are shown correctly... where does it get them from?
Grazie a tutti!
Re: Problem with the records menu
Posted: Sat 13 Apr 2024 6:49 pm
by rchi
Sorry, I correct myself, the given folder on the Raspberry 3 is empty because when doing these tests I moved them and not copied them; I found them all in the backup from a week ago and the data starts from 2021... I attach the file...
alltime.ini which I also attach, contains only a few lines... should it be longer?