Cumulus resetting this night... every params been deleted...

[OliII]

Hi !
Surprise this morning, my Cumulus has been resetted this night, before the backup !
My Cumulus.ini file has been deleted , no params saved, the file is back to the defaults params.
Luckily, this friday, i've backup all the cumulus folder on another HDD.


But, now, i get these errors :

Code: Select all

6/01/2013 11:49:55 : Error on line 5017 of D:\Cumulus\data\janv.13log.txt: List index out of bounds (1)
6/01/2013 11:49:55 : Error reading D:\Cumulus\data\janv.13log.txt at line 5017: List index out of bounds (1)
6/01/2013 11:49:55 : Please edit the file to correct the error
6/01/2013 11:49:55 : Error on line 5017 of D:\Cumulus\data\janv.13log.txt: List index out of bounds (1)
6/01/2013 11:49:56 : Error on line 5017 of D:\Cumulus\data\janv.13log.txt: List index out of bounds (1)
6/01/2013 11:49:56 : Error on line 5017 of D:\Cumulus\data\janv.13log.txt: List index out of bounds (1)
6/01/2013 11:50:32 : Error on line 5017 of D:\Cumulus\data\janv.13log.txt: List index out of bounds (1)

I open the file and see this :

Code: Select all

05/01/13;21:37;6,8;98;6,5;1,7;4,0;280;0,0;0,0;1033,0;220,2;22,9;52;2,2;6,8;6,8;0;0;0,00;0,00;5,6;0;0,0;292;0,0
                                                                                                                05/01/13;21:39;8,1;98;8,0;0,7;2,2;270;0,0;0,0;1033,0;220,2;22,9;52;0,9;8,1;8,1;0;0;0,00;0,00;7,1;0;0,0;292;0,0
05/01/13;21:49;8,1;98;8,0;0,7;0,5;270;0,0;0,0;1033,0;220,2;22,9;52;0,5;8,1;8,1;0;0;0,00;0,00;7,1;0;0,0;270;0,0

Many spaces before the 5017th line. Just deleted these.

Why Cumulus has been resetted this night ? I don't understand, the soft running until 300+ days without problems.

[steve]

There's no code in Cumulus which can delete the cumulus.ini file. The fact that it has apparently been deleted, and the problem in your log file, point to a problem on your system (i.e. a hard drive corruption). Lucky (?) for you that you had a backup

[OliII]

I know there's no code in cumulus wich can delete my cumulus.ini file... Nothing wrong into my hdd or system.. Cumulus just restarted at this time (21:39) for a reason that i ignore...and the fils was deleted at this time.
PS; Luckily = fortunately
Just for report this problem.

Solved.

Bye.

[steve]

Cumulus just restarted

It restarted? If you zip up the diags folder and attach it, I'll take a look.

[agsteele]

Well, I can confirm that I suffered the same thing overnight. When I came to my PC this morning all the settings in the cumulus.ini file had disappeared and Cumulus asked for me to set everything up from scratch...

To be accurate, Cumulus was closed when the computer was shutdown yesterday. The issue became apparent when I restarted Cumulus after starting the computer.

Andrew

[steve]

Please zip up the diags folder and attach it.

[agsteele]

Please zip up the diags folder and attach it.

Sure, attached. But I was about to install the latest version of the 1.9.3 beta. I kind of assumed that with an old beta that a problem could have been resolved...

Andrew

[steve]

I kind of assumed that with an old beta that a problem could have been resolved...

I think that's unlikely, because I don't think it's a problem in Cumulus. The code which reads and writes the cumulus.ini file hasn't changed in the way it works for a very long time, and in any case it uses standard Windows routines to do it.

You're allowing your PC to suspend:

07/01/2013 08:00:47.493 : Windows SUSPEND broadcast received

You're using the 'close on suspend' setting. The end of the diags file is corrupted, presumably because it had the plug pulled while it was writing to the file. I suspect the cumulus.ini file was corrupted for the same reason, unfortunately. I strongly recommend that you don't allow your PC to suspend, and hence don't need to use the 'close on suspend' setting.

[agsteele]

You are, of course, correct about suspending... Since this has largely worked for me without problem I'll monitor the results.

I only added my tuppence as someone else was reporting a similar issue on the same day. If there was a trend then I reckoned you would like to know.

Thanks for the speedy assistance.

Andrew

[steve]

It would be interesting to know whether the OP is also using the 'close on suspend' setting. The help does warn against its use, saying that it can cause problems. I should probably make it clear that data corruption is one of the problems it can cause.

[OliII]

I'm not alone
Here's mine... I see into 003.file many writings into the.ini file
After verifications, no problems with the system, no changes. the netbook is placed into a rack.

[steve]

Here's mine... I see into 003.file many writings into the.ini file

Were you changing settings at the time - around 9pm on the 5th? The file gets written when any config changes are made, and when it closes down. It doesn't look like the close down case, because other messages would have been logged also. Whichever one it was, something was causing it to repeatedly write the file, and then the PC crashed or was rebooted, presumably in the middle of a write, so the file was corrupted.