Extra Webfiles Missing

[Phil23]

What is very clear from all this, MX is not at fault, it does not have an error, it does not need to change to suit you.

First off, I've never pointed the finger at MX & demanded it be fixed for me. Just stated that my ini file is getting corrupted.
And I know damn well there aren't a string of others chiming in saying "it happens to me all the time".

Your routine must have an error that is stopping Cumulus prematurely.

That's why I'm putting it out there; I've got an issue, and am looking for a solution.

And a very random one at that. What is in? 3 times in 5 months?
December 3rd,
February 24th,
April 27th, (well a few days earlier, only posted after the fact).
Not an easy thing to trap.

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.

Good suggestion. My CumulusShutdown.exe was compiled 10/10/2016, so has not been revisited since then.

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

That's the only area I can bring up for question.
All this is just controlled by two Tasks.

Start Cumulus and Update WeatherLink

Capture.JPG

The Start Cumulus Task contains just one action, run the program C:\CumulusMX\CumulusMX.exe.

One key point to note with that task though is it's state: "Running" (0x41301)
It remains in that state until MX is closed down.

Is that relevant? Dunno.
Maybe the timing is too tight with those pings & WL is attempting to grab the Com port too soon & that's causing the wheels to fall off....

As it runs at 6 & 9am & 9pm, I've had ump-teen dozens of opportunities to stand there & gaze at the laptop as an hour rolls over; everything seems correctly timed on the screen.

The other thing in the equation is CumulusUtils; it opens the ini file.
But I tend not to think it's involved as it's only called in the script that runs at the 9:00am rollover;
And my most recent issue occurred at the 6:00am WL update.....

[cliftonweather]

VirtualVP doesn't support the Loop2 command either.

I'm still using a VP1 which is why I've not had any issues.

[Unit-53]

Ok, I have read everything about this loop2. Still can not get my weather site back on line. Can someone PLEASE tell me what I need to do to fix this?


Your console firmware version dose not support LOOP2. Consider disabling it in Cumulus.ini

[PaulMy]

Your console firmware version dose not support LOOP2. Consider disabling it in Cumulus.ini
Ok, I have read everything about this loop2.
Can someone PLEASE tell me what I need to do to fix this?

You can turn off Loop2 by shutting down CumulusMX, adding an entry in Cumulus,ini
[Station]
UseDavisLoop2=0
then restarting CumulusMX

Still can not get my weather site back on line.

Can you tell us a bit more on what the issue is, or what has changed?
If FTP related turn on FTP logging and then check the FTP log.

Enjoy,
Paul

[Unit-53]

That worked! Thank you very much!

[Phil23]

Happened Again.

Looks like at the midnight shutdown MX wrote a blanks 0kb ini file.
MX Diags between 6:00pm & 12:00am look fairly normal, barring a few FTP errors for the realtime transfers.

Last entries are:-

Code: Select all

2020-05-19 00:00:00.473 Writing log entry for 19/05/2020 12:00:00 AM
2020-05-19 00:00:00.505 Written log entry for 19/05/2020 12:00:00 AM
2020-05-19 00:00:00.520 Writing today.ini, LastUpdateTime = 19/05/2020 12:00:00 AM raindaystart = 388.2 rain counter = 388.2
2020-05-19 00:00:00.520 Updating CWOP
2020-05-19 00:00:01.989 WeatherCloud Response: OK: 200
2020-05-19 00:00:03.036 !!! loop data not received, bytes received = 0
Exiting system due to external: Ctrl-C
2020-05-19 00:00:30.629 Cumulus closing
2020-05-19 00:00:30.645 Writing Cumulus.ini file

So for some reason it was clobbered before the writing of the ini file had completed.

Looking at the Diags for the 6:00pm shutdown it was all smooth there.
It's hard to figure a timing thing as it all happens pretty quick.
Circa 60mS for the shutdown process to complete.

Thought about incomplete processes, but I do execute it 30 seconds after the hour mark,
So would presume all precesses have completed.

Code: Select all

2020-05-18 18:00:00.987 WeatherCloud Response: OK: 200
Exiting system due to external: Ctrl-C
2020-05-18 18:00:30.612 Cumulus closing
2020-05-18 18:00:30.643 Writing Cumulus.ini file
2020-05-18 18:00:30.675 Completed writing Cumulus.ini file
2020-05-18 18:00:30.675 Closing connection
2020-05-18 18:00:30.675 Station stopped
Cumulus has shutdown
2020-05-18 18:00:30.706 !!! loop data not received, Comm port is closed

Full Diag file attached.

Cheers

Phil.

[mcrossley]

I don't think its relevant, but I'd change your Start Cumulus task to launch CMX and return rather than wait for it to terminate. Use the cmd start combo, something like...

Code: Select all

cmd.exe /C start "" "path_to_cmx\CumulusMX.exe"

Rather than rely the ping delay, would it be better for your CumulusShutdown.exe to wait for the CumulusMX process to terminate, then delay a couple of seconds

Also the logs are potentially much more useful if debug logging is switched on.

[Phil23]

I don't think its relevant, but I'd change your Start Cumulus task to launch CMX and return rather than wait for it to terminate. Use the cmd start combo, something like...

Code: Select all

cmd.exe /C 

Not familiar with the /C switch; better inform myself...................

Ahhhh,

Code: Select all

/C      Carries out the command specified by string and then terminates

So is that going to mean that the task no longer shows as "Running" in Task Manager until it is terminated?

My desire with the task is to start CMX, once that's done it's done....

The way I have it, it's more like run CMX, & the task sits in the "Running" state until MX shuts down.

Anything is worth a shot.

Thanks.

Phil.

[mcrossley]

Well, the "/C" means that the cmd.exe terminates after running "start", but it's the "start" that fires off CMX and returns immediately.

[Phil23]

Wow!

There's a whole lot more to the Command Processor than what normally comes to mind......

Code: Select all

C:\Users\Phil>cmd /?
Starts a new instance of the Windows command interpreter

CMD [/A | /U] [/Q] [/D] [/E:ON | /E:OFF] [/F:ON | /F:OFF] [/V:ON | /V:OFF]
    [[/S] [/C | /K] string]

/C      Carries out the command specified by string and then terminates
/K      Carries out the command specified by string but remains
/S      Modifies the treatment of string after /C or /K (see below)
/Q      Turns echo off
/D      Disable execution of AutoRun commands from registry (see below)
/A      Causes the output of internal commands to a pipe or file to be ANSI
/U      Causes the output of internal commands to a pipe or file to be
        Unicode
/T:fg   Sets the foreground/background colors (see COLOR /? for more info)
/E:ON   Enable command extensions (see below)
/E:OFF  Disable command extensions (see below)
/F:ON   Enable file and directory name completion characters (see below)
/F:OFF  Disable file and directory name completion characters (see below)
/V:ON   Enable delayed environment variable expansion using ! as the
        delimiter. For example, /V:ON would allow !var! to expand the
        variable var at execution time.  The var syntax expands variables
        at input time, which is quite a different thing when inside of a FOR
        loop.
/V:OFF  Disable delayed environment expansion.

Note that multiple commands separated by the command separator '&&'
are accepted for string if surrounded by quotes.  Also, for compatibility
reasons, /X is the same as /E:ON, /Y is the same as /E:OFF and /R is the
same as /C.  Any other switches are ignored.

If /C or /K is specified, then the remainder of the command line after
the switch is processed as a command line, where the following logic is
used to process quote (") characters:

    1.  If all of the following conditions are met, then quote characters
        on the command line are preserved:

        - no /S switch
        - exactly two quote characters
        - no special characters between the two quote characters,
          where special is one of: &<>()@^|
        - there are one or more whitespace characters between the
          two quote characters
        - the string between the two quote characters is the name
          of an executable file.

    2.  Otherwise, old behavior is to see if the first character is
        a quote character and if so, strip the leading character and
        remove the last quote character on the command line, preserving
        any text after the last quote character.

If /D was NOT specified on the command line, then when CMD.EXE starts, it
looks for the following REG_SZ/REG_EXPAND_SZ registry variables, and if
either or both are present, they are executed first.

    HKEY_LOCAL_MACHINE\Software\Microsoft\Command Processor\AutoRun

        and/or

    HKEY_CURRENT_USER\Software\Microsoft\Command Processor\AutoRun

Command Extensions are enabled by default.  You may also disable
extensions for a particular invocation by using the /E:OFF switch.  You
can enable or disable extensions for all invocations of CMD.EXE on a
machine and/or user logon session by setting either or both of the
following REG_DWORD values in the registry using REGEDIT.EXE:

    HKEY_LOCAL_MACHINE\Software\Microsoft\Command Processor\EnableExtensions

        and/or

    HKEY_CURRENT_USER\Software\Microsoft\Command Processor\EnableExtensions

to either 0x1 or 0x0.  The user specific setting takes precedence over
the machine setting.  The command line switches take precedence over the
registry settings.

In a batch file, the SETLOCAL ENABLEEXTENSIONS or DISABLEEXTENSIONS arguments
takes precedence over the /E:ON or /E:OFF switch. See SETLOCAL /? for details.

The command extensions involve changes and/or additions to the following
commands:

    DEL or ERASE
    COLOR
    CD or CHDIR
    MD or MKDIR
    PROMPT
    PUSHD
    POPD
    SET
    SETLOCAL
    ENDLOCAL
    IF
    FOR
    CALL
    SHIFT
    GOTO
    START (also includes changes to external command invocation)
    ASSOC
    FTYPE

To get specific details, type commandname /? to view the specifics.

Delayed environment variable expansion is NOT enabled by default.  You
can enable or disable delayed environment variable expansion for a
particular invocation of CMD.EXE with the /V:ON or /V:OFF switch.  You
can enable or disable delayed expansion for all invocations of CMD.EXE on a
machine and/or user logon session by setting either or both of the
following REG_DWORD values in the registry using REGEDIT.EXE:

    HKEY_LOCAL_MACHINE\Software\Microsoft\Command Processor\DelayedExpansion

        and/or

    HKEY_CURRENT_USER\Software\Microsoft\Command Processor\DelayedExpansion

to either 0x1 or 0x0.  The user specific setting takes precedence over
the machine setting.  The command line switches take precedence over the
registry settings.

In a batch file the SETLOCAL ENABLEDELAYEDEXPANSION or DISABLEDELAYEDEXPANSION
arguments takes precedence over the /V:ON or /V:OFF switch. See SETLOCAL /?
for details.

If delayed environment variable expansion is enabled, then the exclamation
character can be used to substitute the value of an environment variable
at execution time.

You can enable or disable file name completion for a particular
invocation of CMD.EXE with the /F:ON or /F:OFF switch.  You can enable
or disable completion for all invocations of CMD.EXE on a machine and/or
user logon session by setting either or both of the following REG_DWORD
values in the registry using REGEDIT.EXE:

    HKEY_LOCAL_MACHINE\Software\Microsoft\Command Processor\CompletionChar
    HKEY_LOCAL_MACHINE\Software\Microsoft\Command Processor\PathCompletionChar

        and/or

    HKEY_CURRENT_USER\Software\Microsoft\Command Processor\CompletionChar
    HKEY_CURRENT_USER\Software\Microsoft\Command Processor\PathCompletionChar

with the hex value of a control character to use for a particular
function (e.g.  0x4 is Ctrl-D and 0x6 is Ctrl-F).  The user specific
settings take precedence over the machine settings.  The command line
switches take precedence over the registry settings.

If completion is enabled with the /F:ON switch, the two control
characters used are Ctrl-D for directory name completion and Ctrl-F for
file name completion.  To disable a particular completion character in
the registry, use the value for space (0x20) as it is not a valid
control character.

Completion is invoked when you type either of the two control
characters.  The completion function takes the path string to the left
of the cursor appends a wild card character to it if none is already
present and builds up a list of paths that match.  It then displays the
first matching path.  If no paths match, it just beeps and leaves the
display alone.  Thereafter, repeated pressing of the same control
character will cycle through the list of matching paths.  Pressing the
Shift key with the control character will move through the list
backwards.  If you edit the line in any way and press the control
character again, the saved list of matching paths is discarded and a new
one generated.  The same occurs if you switch between file and directory
name completion.  The only difference between the two control characters
is the file completion character matches both file and directory names,
while the directory completion character only matches directory names.
If file completion is used on any of the built in directory commands
(CD, MD or RD) then directory completion is assumed.

The completion code deals correctly with file names that contain spaces
or other special characters by placing quotes around the matching path.
Also, if you back up, then invoke completion from within a line, the
text to the right of the cursor at the point completion was invoked is
discarded.

The special characters that require quotes are:
     <space>
     &()[]{}^=;!'+,`~

C:\Users\Phil>

[mcrossley]

OK, I have found an issue with the program close down code under Windows, and reproduced the empty Cumulus.ini file. It will need a patch release to fix this, it's a random timing problem, but easy to fix.

[Phil23]

OK, I have found an issue with the program close down code under Windows.

Sounds Excellent.

That has been in the back of my mind, from the point of view of was it my routines or a possible MX issue.

Must let MX run for days & weeks even (as I have done).
The 4 restarts a day is excessive; but also extreme testing of sorts.

Thanks for taking the time to investigate it.

Cheers

Phil.

[Phil23]

I don't think its relevant,

Code: Select all

cmd.exe /C start "" "C:\CumulusMX\CumulusMX.exe"

Interesting side comment to this.
It launches MX ok & the Task then shows as completed; as opposed to still running with my usual method.

BUT, the catch is it launches MX in a Window with no title.
I'd assume AutoHotkey would have method of locating that window.

Phil.

[mcrossley]

You put the window title if you want one in the first set of empty quotes.

[laulau]

OK, I have found an issue with the program close down code under Windows, and reproduced the empty Cumulus.ini file. It will need a patch release to fix this, it's a random timing problem, but easy to fix.

It happens here for the first time yesterday, i'm running Cumulus MX 3.5.4 b3075.
I was closing CMX to upgrade to latest version but i'l wait for the patch.