Possible Bug x2012 written instead of 2012 in alltime.ini

[WoodburyMan]

Currently using Cumulus 1.9.2 build 2026 (Jan 6th build) with my Fine Offset 1090.

I had a odd issue this morning. Every few days I will close Cumulus and copy my entire Cumulus directory to a backup folder. I saw this morning I had a new record low of 5.0F (-15C). I decided it would be a good time to back it up. So I closed Cumulus, copy and pasted the folder, then reopened Cumulus. However I was greeted with a error message saying Cumulus.exe has an error. The error at the bottom of the error box (Which I forgot to screenshot) said "Can't convert date". So I checked out my Jan12log.txt file and the last few entries seemed fine. (Had issue before where power outage caused last line to only get half written and corrected it). So I then checked out my "alltime.ini" since I just had a record and figured it wrote to it. Something odd happened with the file. Every single .ini (alltime, year, month, today, yesterday) had the date changed to incorrect format.

Instead of seeing this:

Code: Select all

lowtempvalue=5
lowtemptime=1/16/2012 7:23:28 AM

this is what was in the file

Code: Select all

lowtempvalue=5
lowtemptime=1/16/x2012 7:23:28 AM

I have no idea what happened here. However I ran a script that looked for /x2012 and /x2011 (Only had records from those two years) and replace with with /2012 and /2011 respectfully and then Cumulus opened just fine and dandy.

Any idea why this might have happened or what caused it? I cannot seem to get it to happen again. I closed Cumulus and opened it several times and it worked fine. Also, yesterday I had another record (Both Temp, wind chill, and apparently) and closed it yesterday, backed it up, and reopened it with no problems, and there had been no change at all in my configuration since then. Just a fluke?

[steve]

The dates in alltime.ini are written using your Windows system date format - is it possible that you have some strange format set?

[WoodburyMan]

The dates in alltime.ini are written using your Windows system date format - is it possible that you have some strange format set?

I'm using standard Date/Time format for U.S. in Windows Regional options. I haven't touched it ever since I last formatted my machine I use for Cumulus sometime last year. I didn't change anything configuration wise in last few days. No programs installed, no windows updates (set to manual). This is also run on a Windows 7 x64 box. Just a really odd thing to happen. Maybe Cumulus doesn't enjoy this cold weather we're having just like me lol.

[steve]

If you zip up the diags folder and attach it, I can see what Cumulus has been using for the date format for the last few runs.

[WoodburyMan]

Here they are
http://files.warpfactor10.com/Diags.zip

Hopefully they'll help sort out what happened.
Cheers!

[steve]

Something strange happened to your system date format just after 05:00 this morning:

1/16/2012 05:00:00.801 : Writing today.ini, LastUpdateTime = 1/16/2012 5:00:00 AM raindaystart = 15.271653175354 rain counter = 15.271653175354
1/16/2012 05:01:00.515 : Writing today.ini, LastUpdateTime = 1/16/2012 5:01:00 AM raindaystart = 15.271653175354 rain counter = 15.271653175354
1/16/x2012 05:02:00.558 : Writing today.ini, LastUpdateTime = 1/16/x2012 5:02:00 AM raindaystart = 15.271653175354 rain counter = 15.271653175354
1/16/x2012 05:03:00.591 : Writing today.ini, LastUpdateTime = 1/16/x2012 5:03:00 AM raindaystart = 15.271653175354 rain counter = 15.271653175354

It looks like Cumulus then crashed on the next few starts, probably because of the invalid dates that had been written to the files, until 08:53, which is presumably after you'd corrected the problem.

So there was some sort of temporary glitch somewhere in Windows which caused the strange dates to get written.

[WoodburyMan]

Hmmm that's odd. I looked through in event log, and saw the only thing that ran, at exactly 5:01am was automatic disk defrag service. Nothing before it since around 12:30am. Other than that, nothing at all till after 7am. . I also checked to see when the last time Windows automatically sync'd my time and it was a few days ago. *shrug* Guess Windows just decided to have a brain fart

Thanks for your help!

[steve]

You were probably right, it's the cold weather