Cumulus Support

Hi all

I upgraded my Cumulus MX from 3.17.0 to 3.22.2 in one big jump due to neglecting the other updates recently and I've run into a problem with the program itself. The dashboard itself shows no data at all although other areas of the interface like "Now" and "Gauges" show the data perfectly fine. FTP seems to have also stopped working with "FTP now" showing error when I click on it. I can see the realtime.txt file being generated normally within the CumulusMX files. I will attach screenshots but not sure what files I might have possibly mucked up to cause this all to happen or perhaps I upgraded in too big of a jump?

MXDiags file doesn't give too many hints either:
2022-10-31 14:42:53.860 Starting on Linux
2022-10-31 14:42:53.958 Creating SIGTERM monitor
2022-10-31 14:42:54.008 Running as a Linux service
2022-10-31 14:42:54.431 Creating main MX log file - MXdiags/20221031-144254.txt
2022-10-31 14:42:54.891 Cumulus MX v.3.22.2 build 3213
2022-10-31 14:42:54.892 Working Dir: /home/pi/CumulusMX/
2022-10-31 14:42:57.231 http://192.168.0.53:8998/
2022-10-31 14:42:57.231 Open the admin interface by entering one of the above URLs into a web browser.
2022-10-31 14:42:57.264 Today.ini = data/today.ini
2022-10-31 14:42:57.266 Last update=2022-10-31T14:42:00
2022-10-31 14:43:10.555 Connected to station
2022-10-31 14:43:17.582 Connecting real time FTP
2022-10-31 14:43:18.103 Normal running



Any help is greatly appreciated
Jamie

Hi Jamie,

Have you tried using another browser? You seem to be using Brave, that by default blocks a lot of things. You could enable ftp logging from settings to get more info. If you are using ftps or sftp, one possible failure reason could be the certificate validity check introduced in 3.20.0, that also can be overridden in settings.

viewtopic.php?p=165756#p165756


—
Sami

SamiS wrote: ↑Mon 31 Oct 2022 4:42 pm Hi Jamie,

Have you tried using another browser? You seem to be using Brave, that by default blocks a lot of things. You could enable ftp logging from settings to get more info. If you are using ftps or sftp, one possible failure reason could be the certificate validity check introduced in 3.20.0, that also can be overridden in settings.

viewtopic.php?p=165756#p165756


—
Sami

Hi Sami

It's the same in Edge and I don't see to have this option to override the certificate validity check in the settings. I also get an 500 error when trying to tick FTP logging. Think there's a culmination of errors that I haven't noticed over time..




Jamie

Missing options and http error 500 suggest that maybe your upgrade is partial or incomplete, and there is a mix of old and new files. Have you unzipped the whole distribution zip over your previous installation?

If you have used CMX console with both browsers before the upgrade, this could also be a browser cache issue. You could try to access the console in private browsing window to see if it helps.

That error is usually because someone has neglected to copy a part of the build to the working Directory or an old version of an existing DLL has not been deleted.

I would suggest copying the entire contents of the build to a new directory, and then copying your data directory into that area, and last copying your cumulus.ini from the existing directory to the new directory and starting MX to see if that solves the problem.

The other possibility is the version of mono you are running may need updating.

SamiS wrote: ↑Mon 31 Oct 2022 5:39 pm Missing options and http error 500 suggest that maybe your upgrade is partial or incomplete, and there is a mix of old and new files. Have you unzipped the whole distribution zip over your previous installation?

If you have used CMX console with both browsers before the upgrade, this could also be a browser cache issue. You could try to access the console in private browsing window to see if it helps.

water01 wrote: ↑Mon 31 Oct 2022 5:43 pm That error is usually because someone has neglected to copy a part of the build to the working Directory or an old version of an existing DLL has not been deleted.

I would suggest copying the entire contents of the build to a new directory, and then copying your data directory into that area, and last copying your cumulus.ini from the existing directory to the new directory and starting MX to see if that solves the problem.

The other possibility is the version of mono you are running may need updating.

I had left out some of the folders when copying over the new build that I hadn't even clocked until doing it now. Had a feeling it might have been some obvious thing like it.

All working now, thanks for your help!
Jamie