Cumulus Support

Hi Mark

I updated from b3086 to 3090 and just updated the changed files including ini. On booting up an IO error flashed by and the realtime file was not updating but everything else seems ok.
I have reverted to b3086 and it works again. Attached is the MXDiags file including the error.
Many Thanks

It looks like it could not find the file "Renci.SshNet.dll" in the CumulusMX folder. So either missing or corrupt?

forestedge wrote: ↑Thu 13 Aug 2020 4:40 pm ... including ini.

ini? You just the contents of the zip.

It looks like it could not find the file "Renci.SshNet.dll" in the CumulusMX folder. So either missing or corrupt?

Thanks I still had the old version, missed the updated one in 3087 which is nearly twice the size!

As always I do not recommend just updating individual files, the only folder to be wary of is /web if you have customised the standard files. Otherwise just extract the whole zip. You cannot rely on me not missing files from the changed list. I fact it causes so many problems I'm thinking of dropping it from the release info.

mcrossley wrote: ↑Thu 13 Aug 2020 7:34 pm I fact it causes so many problems I'm thinking of dropping it from the release info.

I think that's a wise choice Mark. It does create confusion and complications. better to advise users just to backup the full CumulusMX folder and then copy in the whole zip contents.

mcrossley wrote: ↑Thu 13 Aug 2020 7:34 pm I fact it causes so many problems I'm thinking of dropping it from the release info.

Imaginable but bad from informatics point of view. Users need to know what changed.

It's more the freedom of installation they have which is problematic. Users seem to think that files are there just for selecting what they think, or think to know, is enough or required. If there was an installation script/procedure which forces an installation on the user, there would be much less problems I assume. The log file of that procedure would be required with a support request. Or a file check procedure could come in handy. If a user messes with the installation.... bad luck: reinstall required.

With regards to the website where the user may make mods: just make a copy so the user can find back what he did or only copy it during an initial install (that would be easy to detect I guess)

Something like that.
But don't leave out release notes, that is a bad habit.

Note: I always copy the whole distribution tree (I don't use the website so did not modify anything there): never a problem!
Note2: and even with the above you can be sure users will hack around just for the crack. So a check on the installation would probably best and least effort. Then require users to send in MXdiags and the filecheck log on support request. If not, no support.

mcrossley wrote: ↑Thu 13 Aug 2020 7:34 pm As always I do not recommend just updating individual files, the only folder to be wary of is /web if you have customised the standard files. Otherwise just extract the whole zip. You cannot rely on me not missing files from the changed list. I fact it causes so many problems I'm thinking of dropping it from the release info.

Installation of 3090 now completed ok. I understand why the full zip is recommended, with the volume and scope of updates now I will do this in future with the exception of the web folder.
Are the ini settings retained when this method is used or should it be copied back in?

There should be no Cumulus.ini supplied in the release so you should always retain your own version. If there is one it is a mistake.