Extra Webfiles Missing

[mcrossley]

The backup is not currently configurable. It saves the last ten days rollover backups, plus the last ten Cumulus startup backups.

[Phil23]

Should probably kick myself in the arse for not employing such a simple script from day one.
Classic case of over thinking, but not outside the square.

Code: Select all

Robocopy C:\CumulusMX C:\CmxBackup *.* /s
Robocopy C:\CumulusMX \\phils-i7\Xternal\Backups\CmxBackup *.* /s

Only catch is if there's a locked file when it's scheduled at 9:05am.
(None showing as failed, so assume RC opens read only).

Phil.

[Phil23]

It's happened again....

More specifically:-

Some of the Extra Webfiles entries are missing, but I think the fir 10 stayed intact.
The NOAA monthly figures were gone.
Additional Uploads to other services were gone.
Realtime Gauges upload was off again.

I'm fairly sure it's related to my routine shutdown/restart that happens 4 times a day.

Due to the backup script I mentioned above, I now have a total history of the ini file, so will take a look at all those & can upload a few if that's of help.

[freddie]

Hi Phil,

I'm fairly sure it's related to my routine shutdown/restart that happens 4 times a day.

Can I ask why do you need to restart 4 times a day?

[Phil23]

Can I ask why do you need to restart 4 times a day?

I put those restarts in place a year or so back in order to download data to Weatherlink by running it with the download option

Code: Select all

"C:\WeatherLink\WeatherLink 6.0.5.exe" -d

There was a graph involving EVT I was interested in which I could not get in MX.
Basically EVT, Rain & Temp on a strip graph.

The 4 times a day gave me the "AS of 9:00am" point we use here & also kept the number of records Weatherlink needed to download each time to a minimum.

It's all managed with Task Scheduler.

[freddie]

That sounds fair enough.
How are the restarts done?

[freddie]

How are the restarts done?

Oops sorry - you answered that already.
You're on Windows so I don't know if I can add anything useful, sorry.

[mcrossley]

From your log files I don't see the last message I would expect to see after "Writing Cumulus.ini file". The Davis VP2 station should write a log entry - "Closing connection".

It would seem the method of terminating CMX perhaps isn't giving it sufficient time to close properly before it kills the process.

How are you terminating Cumulus? Are you using a third party tool to send a Ctrl-C, Ctrl-Break, or CloseMainWindow event?

The shutdown logging is a bit sparse, I'll add a few more messages for the next release.

[sfws]

I'm fairly sure it's related to my routine shutdown/restart

Another way might be to set task scheduler start task to stop after 5 hours 50 minutes, if you do that I am unsure how it stops the task, I don't know.

When Cumulus is asked to close normally, it takes a while to close as it is writing out to files including Cumulus.ini.

[Phil23]

My guess FWIW, is that your scheduled shut down is terminating the Cumulus process using "Taskkill" rather than asking the Cumulus software to close. Off the top of my head I can't say how you send a control C to close the Cumulus task window, but someone will know

For the Shutdown, I use a complied script From AutoHotkey.
https://www.autohotkey.com/

It basically put the focus on the focus on the CMX Window & then sends Ctrl-C.

Simple script, that is complied into an exe so I don't need AutoHotkey running in the background.

Code: Select all

#NoEnv  ; Recommended for performance and compatibility with future AutoHotkey releases.
#Warn  ; Enable warnings to assist with detecting common errors.
SendMode Input  ; Recommended for new scripts due to its superior speed and reliability.
SetWorkingDir %A_ScriptDir%  ; Ensures a consistent starting directory.
WinActivate, C:\CumulusMX\CumulusMX.exe
Send ^c
Return

Cheers.

[sfws]

sends Ctrl-C.

Ok, you initiate a proper close down.

I'm fairly sure it's related to my routine shutdown/restart that happens 4 times a day.

If your shutdown script is just that hotkey routine....Could you use a WinWaitClose to wait until the MX window closes before you do the return.

If your shutdown script is more than that routine, what does it do next, perhaps it needs a delay there?

[cliftonweather]

Have a look at VirtualVP, http://www.softwx.com/weather/virtualvp.html
It basiclly allows you to connect upto 8 programs to single Vantage Pro console. You then won't need to keep stopping & starting MX. I've been using it for years on Windows 7 with no problems. It's free for 30 days so enough time to see if it cures your problem.

[Phil23]

Have a look at VirtualVP

That's something I've looked at over the years, but it's support has stopped, circa 2012.

From what I read on WXforums it can be hit & miss to get it working these days.
For just that reason they no longer take paid registrations.

See http://www.softwx.com/purchase.html
Something to do with the cost associated with registering updated Digitally Signed Drivers.

Cheers.

[cliftonweather]

That is one of the downsides, you have to run your pc permanently in Test Mode, but I've not found it to be a problem, supposedly it can be a security issue though.

[mcrossley]

VirtualVP doesn't support the Loop2 command either.