Hi Tony,
In summary: I cannot explain why you have a perfect maps.txt but there are no stations in it. So I blame the activation of two instances (see below), but the proof of the pudding is in the eating. So run again with just
mapson and see what happens. And btw, this has no relation with the 3.6.4 beta test, so I'll create a new thread.
One thing I do not understand is why you start two cumulusutils at the same time:
The first is:
Code: Select all
2020-07-04 00:00:03.546 CumulusUtils : Entering Main
2020-07-04 00:00:03.776 CommandLineArgs : starting
2020-07-04 00:00:03.800 CommandLineArgs : handling arg: Top10
2020-07-04 00:00:03.800 CommandLineArgs : handling arg: SysInfo
2020-07-04 00:00:03.800 CommandLineArgs : handling arg: DayRecords
2020-07-04 00:00:03.800 CommandLineArgs : handling arg: Records
2020-07-04 00:00:03.800 CommandLineArgs : End
And the other is:
Code: Select all
2020-07-04 00:00:04.080 CumulusUtils : Entering Main
2020-07-04 00:00:04.104 CommandLineArgs : starting
2020-07-04 00:00:04.104 CommandLineArgs : handling arg: pwsFWI
2020-07-04 00:00:04.104 CommandLineArgs : handling arg: Graphs
2020-07-04 00:00:04.104 CommandLineArgs : handling arg: Yadr
2020-07-04 00:00:04.104 CommandLineArgs : handling arg: MapsOn
2020-07-04 00:00:04.104 CommandLineArgs : handling arg: Windrose
2020-07-04 00:00:04.104 CommandLineArgs : handling arg: NOAA
2020-07-04 00:00:04.104 CommandLineArgs : End
That was intended to be run as one command with all those parameters on the commandline. There is obviously an interaction somewhere but I am not going to analyse that deeply because this is not the way it should be run, even though the logfile system has been taken care of (by the runtime of C#).
What you should avoid anyway is running two instances at the same time (which is what is the case here), that has never been anticipated and apparently leads to unwanted interaction (not understood by me at the moment).
As you run the website, you should run (square brackets means: optional):
But as you don't want that (obviously
), probably because of your modifications in the generated files, you should at least do it in one command:
And then - when this is finished - you run:
If you want the sysinfo updated - e.g. every hour - you run the last command without the mapson parameter every hour but make sure it won't interfere with the daily command. Because the windrose can take quite some time and you don't use thrifty you should measure once how much time that takes (I see in the logfile for you it is only 3.5 seconds, that will increase over the years!) and account for that in starttime for the next run of CumulusUtils.
So, given your situation, I would advice (e.g.) to do a midnight at 00:01 run (to allow Cumulus to make the rollover to finish if you do not run from within CumulusMX) with the
all parameter followed by a maps run at 00:10 and then a sysinfo run every hour at 00:15. That would avoid any unwanted interaction of multiple instances.