CumulusMX Reliability

[thief2]

Hi Guys!

Before I explain the topic, can I say that the Cumulus software is brilliant and 99% of the time is very reliable.

I have been using Cumulus software for many years now and many thanks to Steve for this.

At this moment in time I use CumulusMX V3.0.0 Build 3036.

Now , in the last few days, the config file suddenly reset to default and the realtimegaugesT.txt file disappeared from the web folder!

As I keep backups of everything , I recovered the situation very quickly.

This has happened to me twice in the last 4-5 years that I have been using Cumulus software.

Around the same time as this happened I also had network issues and wifi disconnections.

The cumulus software resides on a laptop and uses wifi to collect data from the weather station and send information to my website and other organisations.

This has been working quite happily apart from the two issues mentioned.

Has anyone had similar issues and if so do they have any ideas as to the cause?

Many thanks for your time.

Keith.

[PaulMy]

My first recommendation is to update to current version, build b3052 which has had a number of fixes and improvements as well as new features like Windy.
Reliability is rock solid!

The same update process as previous. A full install is my preference, then copy over from your b3036 the \data folder, Cumulus.ini, and any changes you may have made in the standard template files for upload, etc.

Enjoy,
Paul

[thief2]

Thanks Paul!

I'll update as you requested to the latest version.

Any thoughts as to why I have had this problem?

Regards,

Keith.

[mcrossley]

Sorry, no idea really. CMX only ever opens the realtimegaugesT.txt file in read-only mode, so its hard to envisage CMX deleting the file.

Likewise on exit CMX writes all the existing settings back to the Cumulus.ini file. If the Cumulus.ini is missing, then CMX will create a new blank one with the default entries.

I have no explanation, other than it seems "something" deleted these two files. Anti-virus software is always a suspect in cases like this - it may briefly lock files. If you haven't already try adding the Cumulus folder (or at least the ini file, the web and data folders) to your AV exclude list.

[thief2]

Thanks Mark.

MY AV already has an exclusion entry for the entire cumulusMX folder.

I guess we'll have to see if this recurs.

Oh , I took Paul's advice and upgraded to the latest cumulusMX version.

But I have one issue now , the local computer cumulusMX dashboard errors with connection closed if run on the new version.

Developer f12 shows error during websocket handshake: unexpected response code: 200 ( dashboard.js:14)

Everything else is working just fine though.

[mcrossley]

If you copied all the new folders over for b3052, then try flushing your browser cache.

[thief2]

Hi Mark.

I had already cleared all the caches on the browsers I use but no change.

So I started again and upgraded afresh and bingo everything works ok.

I must have made a simple mistake somewhere along the road , but all is ok now.

Many thanks for your help and also Paul too.

Keith.

[thief2]

Just to let you know , I am now running v3.2.5 build 3061 .

This upgrade was seamless and trouble free!

Many thanks to Mark for all his hard work!

[raul_sbd]

Hello Mark,

Just to confirm the process of upgrade to a new build ie next Mx build when will be out is to unzip the file you post and then paste all the files on my existent cumulus Mx folder? Without copying any of the folders just files?

I have been trying to check on the wiki but could not find anywhere on how to update cumulus or update the steel gauges to last version.. David explained me how to update cumulus but it kind of vanished from top of my head and I want to have both up to date with last versions..

Many thanks

[mcrossley]

Unless you have modified any of the web site files, it is best to copy everything in the zip. If you have modified the web files, just omit that folder.

[freddie]

Just to confirm the process of upgrade to a new build

One thing you may wish to change is the longitude value for your site - as it is currently placing your site in the North Sea. It should be Longitude W 02° 31' 59" (not E) to place it in Cheshire.