Latest CumulusMX issues ftp and mysql

[The PIT]

Upgraded to the latest cumulusmx today and everything seemed to be working fine. I made some changes on the ftp and changed password and it still connected.

Anyway I had to stop the ftp server and restart it and thats when the the trouble started.

Cumulusmx wouldn't reconnect to ftps.

At the same time I noticed that the following error Error encountered during MySQL operation = Could not load file or assembly 'System.Diagnostics.DiagnosticSource, Version=5.0.0.1, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51' or one of its dependencies. The system cannot find the file specified

Anyway first job get ftp working. Looking at the connection logs on the server it wasn't even trying to connect.

Stopped restarted mx no joy.

Tried plain ftp still no connection attempt.

Tried sftp and it connected well I prefer it to use that so I'm happy with that.

Still stuck at mysql error and I also noticed another error that cumulusmx would try ever so often to upload old image files that aren't used any more and neither were they ticked to upload. I then removed from from the extra files so hopefully thats fixed.

However the mysql error is where I'm stumped. What files is it looking for??? Nothing has changed on that side and the error didn't occur until the ftp service died so it maybe related.

[mcrossley]

Do you use a MySQL database?

If not then you need to disable the realtime upload.

Either way it looks like your system is missing some .Net 4.8 files. You could also try running the .Net repair tool - https://docs.microsoft.com/en-gb/dotnet ... all/repair

[The PIT]

Fixed the ftp issue it was to do with tls looks like cumuls doesn't support tls 1.3

[The PIT]

The mysql has always been enabled but I presume those settings for mysql on a web server?

[water01]

From Release 3.14.0 Build 3159

Change: Now supports TLS1.3 for HTTPS/FTPS/MQTT/Email - dependent on OS support and enabled

Have you upgraded ALL files as the MySqlConnector.dll changed in this release to version 2.0.0 to allow this to happen.

[The PIT]

tls 1.3 wasn't enabled in windows but at the moment leaving things where they are on the ftp server.

[The PIT]

Yeh I updated that.

Life is rather difficult since we no longer have a list of what files have changed but I spotted that one.

[water01]

Yeh I updated that.

Life is rather difficult since we no longer have a list of what files have changed but I spotted that one.

Best to overwrite ALL files from a release, have always done that and had no problems.

[The PIT]

Yeh I updated that.

Life is rather difficult since we no longer have a list of what files have changed but I spotted that one.

Best to overwrite ALL files from a release, have always done that and had no problems.

Err nope then you run the risk of breaking some other configuration you may have setup in the past.
Ideally you just copy the files over that have changed which is what err release notes are for.

Now got an error in regards to wow.

[water01]

Err nope then you run the risk of breaking some other configuration you may have setup in the past.

Nope I said just copy ALL the release files where CumulusMX exe is(there is nothing in there that has anything to do with configuration) not the data area where all the configuration and previous data files are held.

Never had a problem ever since the beta release under Steve Loft, many, many moons ago!!

[The PIT]

Still got that WOW warning leaving it for now and if still acting up tomorrow will probably revert back to the old cumulus backup

However I checked the wow web site and it's updating.

[mcrossley]

As David said, the recommended way to upgrade is to copy all the files out of the zip - at least all those in the root Cumulus folder and /interface if you have customised web files. But if you customise web files I recommend you rename them, and use the renamed versions in your config. Then you are safe to copy the entire contents of the zip every release.

Providing a list of changed files invites people to just copy files they think have changed and that led to so many support issues.

Re WOW, I didn't see any mention of an error - but I find it normal that their servers return errors every so often.

[freddie]

Still got that WOW warning leaving it for now and if still acting up tomorrow will probably revert back to the old cumulus backup

However I checked the wow web site and it's updating.

What WOW warning do you see? It may be something that can be ignored, but it's difficult to be sure without seeing it.

[Mapantz]

ideally you just copy the files over that have changed which is what err release notes are for.

updates.txt is included in the Cumulus MX zip.

The correct practice is to copy all files across..

Almost 100% of the time, when a member reports that something has gone wrong after upgrading to the latest version, it's always down to not copying all of new files across.

[The PIT]

Checked this morning and everything seemed to be okay. WOW error vanished so guess it was an error at there end.
Stopped culumusmx. Anyway for the hell of it I just copied the cumuluxmx files over the top leaving the sub folders as is.
Restarted the cumulusmx program wow and everything else connected. Just out of interest I re-enabled the mysql upload and that got a different error a time out instead.

The only other thing is the cloud base graphic no longer shows the correct time or no time at all. Last night it had stopped showing the 24 hour format. There isn't anything on the update that should effect the time and date.