Cumulus Support

Build 895

I tried to update the Weather Diary for today: Added a comment, checked snow lying & snow falling then also added the depth of snow. When I click on Update Cumulus gives the standard error message and options to continue or exit program.

I've rebooted the pc and restarted the application and still get this error.

I've attached the bugreport.txt

Could you attach your log.xml file (zipped), please?

What OS are you using?

Hi Steve

I'm using Windows XP Home

Thanks - the file looks OK, and indeed works fine for me, so it's a bit baffling. Are you able to look at existing entries?

When I try to go back to December I get the attached error with my current log.xml file and even after removing the log.xml file
cumulusdiaryerror.jpg

I also get the same message moving forward to January 2010

Then if I try to update I get the application error shown in cumulusdiaryerror2.jpg

Thanks - that makes it more understandable; basically it can't find/open the log.xml file, which is why you can't update it. Unfortunately I don't know why it can't open the file. I'll think about it.

I assume you also get an error with 'This Month' etc, as those also use the log.xml file?

Is your jan10log.txt file being updated OK?

Jan10log.txt is being updated
I have no problem accessing This Month, This Period, This Year or All Time records. I can move month to month without errors.

Its literally only the diary that is causing problems.

It looks like I've solved this one.

The reason for this odd behaviour is the file became fragmented.

Sorry but at least now should the problem raise its ugly head for someone else then you now have a solution for it.

I ran Auslogics Defrag program with optimisation on my Windows XP system.

http://www.auslogics.com/en/software/disk-defrag Free for Home Users. Fast and effective.

Thanks. I can't claim to understand it, though!

Thanks Steve for your help.

Its more down to a hardware problem. Once a file gets fragmented in many bits it can be stored all over the hard drive and when that happens sometimes the hard disk can't keep up trying to find parts of the file.

e.g. 1kb could be stored in the outer edge of the disk, 1kb on the inner edge and the rest of the filesize spread all over the place like a starburst of say an exploding firework.
Running a defrag with optimisation will put the file back in sequential order so the drive doesn't have to go searching for all the broken bits.

So although cumulus could read 9/10th's of the file the 1/10th it couldn't read was the Diary.

The more times a file is written to disk the higher chance of it fragmenting and becoming corrupted.

I hope this explains what I think has happened here.

I'm afraid - Using the Same Build as ScotWeather............
And mine has come up with Exactly the same error as ScotWeather.
I did defrag and restarted Cumulus and the Webtag is now working.
But, when trying to view previous entries it comes up with the Error Splash and Message.

Nope can't be a fragmented log.xml

I've just tried to update the diary after it was working earlier tonight and now I have the same problem again.

I don't really know what to suggest, I haven't changed the diary code at all. But I have introduced the snow web tag, and the 'this month' etc screens use the log (but they always have done anyway); I'm wondering if it's some sort of multiple access problem.

Scotweather - do you use the new snow web tag?

I use the snow depth tag yes as does WWS

OK did a test this morning.

I put back the orginal cumuluswebtag.php file (Version 1.02) which doesn't include the snowdepth tag and diary was working fine.
added the $snowdepth tag to it and restarted cumulus and low and behold I'm getting the diary error.

Remove the tag again and even without restarting Cumulus the error goes away and you can update the diary.

I can replicate the error everytime by adding the snow depth tag to cumuluswebtag.php