Cumulus Support

I started cmx accidentally not with my de-DE parameter. So cmx mixed up dot and commas. I tried to remove all commas. This seems not to be successful.

Cmx does not work and log file in MXdiags does have the following entries:
There was an error during serialization for object of type CumulusMX.DataStruct

Any suggestions?

Horst

Stop MX, find the backup folder created when you started with the wrong locale setting, copy the files from it into the data folder, and then start MX.

Hi steve,
thanks you for your response.

I tried this, but it seems to me i have tried to start cmx too often before. So there is no backup left which is from before the accident.

Btw. is there a setting to set the number of backups?

Horst

The Cumulus built in backups are very good, and adding your own full backup regularly is even better

I presume you had data saved in from before the current data in your datalogger? so backdating is not an option?

Paul

Did it happen more that ten days ago, so you can't use one of the daily backups?

No, the accident was 5 days ago. But i think cmx makes a backup every time it was started. So i do have 10 backups but i don't have 10 days backup.

Deleted

this is all i have but i need a backup from before 20150724. I have also saved the 20150724212258 and 20150724211338 outside the backup folder. So it seems there is no backup which i can use.

But how can i correct the error? Just changing the commas to dots does not work. There are also other mistakes. I found this one in dayfile.txt and corrected it:
27:01:15;18,4;[..]

which should be
27.01.15;18,4;[..]

This led me to the file Jan15log.txt which contained in several dates Slashes as date delimiter.

Correcting these errors changed nothing: cmx does start on the command line and the webpage does not contain data.

That daily backup folder is very odd, only the latest one looks reasonable, as it's timestamped just after midnight. If you zip up the MXdiags folder and attach it, I'll take a look.

You probably have some issues with date/time formats in the ini files which hold all-time records etc.

Edit: it's probably the timestamps in today.ini which have caused the daily backups to go wrong, as it's confused about what day it was when it last ran, so it's doing the daily backup immediately. It has probably done an end-of-day rollover for each of those, so you probably have multiple entries in dayfile.txt, with invalid data.

Hi steve,

i will send you the MXdiags folder and my oldest dayfile.txt by pm.

Horst

It seems to be working OK, so it looks like you have corrected the data successfully. The error message you quoted is probably because of the bug in the Mono json serializer when decimal commas are used.

Hi Steve,
but it does not work in the browser all data fields are empty.

steve wrote:It seems to be working OK, so it looks like you have corrected the data successfully. The error message you quoted is probably because of the bug in the Mono json serializer when decimal commas are used.

Yes, as I said, probably because of the bug in the Mono json serializer when decimal commas are used. There are known issues in Mono with its handling of decimal commas, which is why it's the first item, highlighted in red, on the 'FAQ/known issues' page.

What version of Mono are you using?

Hi Steve,

Mono version seems to be 3.2.8, ('dpkg -l | grep mono' gives me all 3.2.8)

O.K. what can i do, where are commas left?

I had a closer look on the cmx webpages and found some pages which are containing data (mybe wrong data) and some which not containg data. I have made some hardcopys which i will send you by pm. Maybe you find anything interesting.

Horst

That version of Mono doesn't work correctly with decimal commas, you need to use a locale which uses 'full stops' for decimals, and all of your data has to use that format.