Cumulus Support

Is this because of the "New Year" rollover?

bnwrx wrote:Is this because of the "New Year" rollover?

Not specifically; it just looks like a 'failed rollover'. Looking at your site confirms that, as you have a hight temp at 15:15 and it's still morning there. Was Cumulus running overnight? If you zip up the diags files I'll see if I can see what went wrong.

Thanks Steve, it appears I have no dayfile for 12/31/2010. Now, what and how do I send you a "diags" file?

Steve, Here are the diags files from 1/1/2011

There was no activity between 21:45 yesterday and 03:00 this morning:

12/31/2010 21:39:02.732 : Writing todayfile, LastUpdateTime = 12/31/2010 9:30:00 PM raindaystart = 0
12/31/2010 21:45:23.054 : Writing todayfile, LastUpdateTime = 12/31/2010 9:30:00 PM raindaystart = 0
1/1/2011 03:00:29.532 : FTP Error: 426 Timeout
1/1/2011 03:00:29.601 : Writing todayfile, LastUpdateTime = 1/1/2011 3:00:29 AM raindaystart = 0
1/1/2011 03:00:39.594 : Writing todayfile, LastUpdateTime = 1/1/2011 3:00:29 AM raindaystart = 0

Looks like your PC went to sleep?

The easiest way to recover is to find the set of backup files which would have been taken when you started at 07:15 yesterday, and copy them to the data folder (with Cumulus stopped), delete the existing January log file, then start Cumulus. It will use the data from the logger to catch up.

Thank you!!!
I did as you instructed, and all seems well now. Don't quite understand what happened though. My computer normally goes to sleep overnite and Cumulus doesn't have a problem the next morning when I start it up. I will keep your instructions for future events though....

Cumulus will always have a problem if your PC goes to sleep while it's running. The magnitude of the problem depends on how long the PC is sleeping and whether or not it is sleeping at midnight, in which case you will get a failure to do the rollover.

It doesn't matter if the PC sleeps while Cumulus is stopped; presumably that's normally the case?

steve wrote:Cumulus will always have a problem if your PC goes to sleep while it's running. The magnitude of the problem depends on how long the PC is sleeping and whether or not it is sleeping at midnight, in which case you will get a failure to do the rollover.

It doesn't matter if the PC sleeps while Cumulus is stopped; presumably that's normally the case?

Yes it is, however it typically will go to sleep while Cumulus is running and I am not present to close the program. I return and start Cumulus without a problem. I thought this was OK because of ticking the "Close on suspend" option in Cumulus.This is how I have done it since using Cumulus for almost 2 years now. I will now be aware a problem could occur.

Thanks for the help.

As a thought, would using the 9am rollover be solution to this as typically the computer is running at that time. It is almost never running at midnight. If so would altering the rollover time now affect any of the previous record data?

bnwrx wrote: I thought this was OK because of ticking the "Close on suspend" option in Cumulus.

Normally, this would cause Cumulus to attempt to close itself, yes. But it all depends on it actually receiving the 'suspend' message from Windows and being able to process it. It appears that in this case it did not. This setting is really a 'last resort'. As it says in the help: "Please note that this option can occasionally cause problems, and you should avoid its use if at all possible. Better to make sure that your PC doesn't suspend!"

bnwrx wrote:As a thought, would using the 9am rollover be solution to this as typically the computer is running at that time. It is almost never running at midnight. If so would altering the rollover time now affect any of the previous record data?

It would effectively invalidate all of your data gathered so far. The best solution is to not allow the PC to suspend while Cumulus is running.