Cumulus Support

My open cmd window tells me MX crashed and to send in the MXDiags folder.

I guess what confuses me is that my weather-underground page sez it's still being updated.

I'd been gone for a dozen or more hours and no one was here who could have done anything on the 'puter box.
----------------------COMMAND Window--------------------------------------------------
Current culture: English (United States)
Serial: 5490216F9A3375DBD9E79DA4F7FF916D
Cumulus MX v.3.0.0 build 3041
Today.ini = data\today.ini
Last update=2017-02-01T15:00:00
Connected to station
15:13:43 Downloading Archive Data
Cumulus running at: http://*:8998/
(Replace * with any IP address on this machine, or localhost)
Starting web socket server on port 8002
2/1/2017 15:13:43
Type Ctrl-C to terminate
15:13:51 Downloading Archive Data
15:13:54 Normal running
System.IO.IOException: Unable to write data to the transport connection: An esta
blished connection was aborted by the software in your host machine. ---> System
.Net.Sockets.SocketException: An established connection was aborted by the softw
are in your host machine
at System.Net.Sockets.Socket.Send(Byte[] buffer, Int32 offset, Int32 size, So
cketFlags socketFlags)
at System.Net.Sockets.NetworkStream.Write(Byte[] buffer, Int32 offset, Int32
size)
--- End of inner exception stack trace ---
at System.Net.Sockets.NetworkStream.Write(Byte[] buffer, Int32 offset, Int32
size)
at ?.?(TcpClient ?, String ?) in C:\Users\steve\RiderProjects\CumulusMX\Cumul
usMX\DavisStation.cs:line 673
at ?.?() in C:\Users\steve\RiderProjects\CumulusMX\CumulusMX\DavisStation.cs:
line 563
at System.Threading.ThreadHelper.ThreadStart_Context(Object state)
at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionCo
ntext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, C
ontextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, C
ontextCallback callback, Object state)
at System.Threading.ThreadHelper.ThreadStart()
**** An error has occurred - please zip up the MXdiags folder and post it in the
forum ****
Press Enter to terminate
----------------------------------------------------------------------------------------------------

It doesn't say it crashed, it says an error has occurred. The data reading thread (and only the data reading thread) stopped working because the connection to the console was closed, as you have previously reported. As I have said previously, MX might one day cater for this unusual situation.

ok. I knew I'd seen a "problem" another time but frankly didn't recall what it was.
This morning I see the same problem occurred again between last night and this mo0rning.

I upshot is, do I need to worry about it or just restart it when I see the error in the cmd window?

wherre might I trace a problem generated by comms to the "console" ?

Clearly it's a problem for you - as you've seen, when the data reading thread stops, the rest of MX carries on blithely logging and uploading the same data until you restart it. Tracking down the problem is non-trivial, and I can't be of much help. You could try swapping out hardware items one at time (e.g. cables, router etc). Use of network 'sniffer' software might help to pinpoint the problem, but that requires a certain amont of expertise in diagnosing TCP/IP problems.

well, that may be ...

I just removed all scanning or paying-attention to, MX by system firewall.

now when I try to run MX I get windows error:

Problem signature:
Problem Event Name: CLR20r3
Problem Signature 01: CumulusMX.exe
Problem Signature 02: 1.0.0.0
Problem Signature 03: 57b4b79a
Problem Signature 04: System
Problem Signature 05: 4.6.1087.0
Problem Signature 06: 583e5c41
Problem Signature 07: 20f9
Problem Signature 08: 51
Problem Signature 09: System.InvalidOperationException
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 1033
Additional Information 1: 0a9e
Additional Information 2: 0a9e372d3b4ad19135b953a78882e789
Additional Information 3: 0a9e
Additional Information 4: 0a9e372d3b4ad19135b953a78882e789

Read our privacy statement online:
http://go.microsoft.com/fwlink/?linkid= ... cid=0x0409

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt

That appears to be a crash in the Windows .Net runtime, before Cumulus has been initialised.