If you use Cumulus, please donate Image

Please read this post before posting

Latest Cumulus release v1.9.4 (build 1099) - Nov 28 2014
Latest Cumulus MX release - v3.0.0 build 3043 Jan 20 2017. See this post for download

Mx Stopping

Discussion of version 3 of Cumulus, which runs on Windows, Linux, and OS X. All Cumulus MX queries in here, please.
User avatar
KD7YZ
Posts: 70
Joined: Tue Mar 10, 2015 12:23 pm
Weather Station: Davis VP2
Operating System: Win 7 64bit
Location: Kentucky

Mx Stopping

Postby KD7YZ » Fri May 19, 2017 2:22 pm

I "thought" I'd solved this when I discovered I was supposed to do Port-Forwarding in the ASUS router. At least MX did work with only one crash for two days. But it just happened again a while ago ... naturally it did. Afterall, I patted myself on the back and pleased with the working I went and donated, then removed the MX screen from the firefox open tabs ..

any help on this one?

------------------Current culture: English (United States)
Serial: 5490216F9A3375DBD9E79DA4F7FF916D
Cumulus MX v.3.0.0 build 3041
Today.ini = data\today.ini
Last update=2017-05-19T07:04:00
Connected to station
07:07:52 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
5/19/2017 07:07:52
Type Ctrl-C to terminate
07:07:56 Downloading Archive Data
07:07:59 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
^A
----------------------

User avatar
steve
Cumulus Author
Posts: 26141
Joined: Mon Jun 02, 2008 6:49 pm
Weather Station: None
Operating System: None
Location: On tour in France
Contact:

Re: Mx Stopping

Postby steve » Fri May 19, 2017 3:00 pm

From the Cumulus point of view, this is the same problem that you've reported previously. The TCP/IP connection to the logger has been disconnected (by something other than Cumulus). Cumulus MX does not currently cater for the connection being disconnected.
Steve
-----
Hosting available for Cumulus web sites. See http://sandaysoft.com/forum/viewtopic.php?f=2&t=11876

Like Cumulus and want to support it? Please donate! Image

User avatar
KD7YZ
Posts: 70
Joined: Tue Mar 10, 2015 12:23 pm
Weather Station: Davis VP2
Operating System: Win 7 64bit
Location: Kentucky

Re: Mx Stopping

Postby KD7YZ » Fri May 19, 2017 4:27 pm

RR "before" .. but after I discovered I needed Port Forwarding, I was running the old Cumulus and it never quit for about 2 or 3 weeks .. thus I jumped to MX and for a couple days thought I'd figured it out.

What you're saying is "logger' ,, that would mean ANY Cumulus program was unable to get to the Davis VP2+ .... Earlier today I set the Davis Port into Port Forwarding .. I guess I need to start a 'Thread' here and get someone to walk me whatever I need to get Port Forwarding going.

I searched through the archives and thought all I'd seen were references to Mx and 8998 and 8002 ... didn't ever see anyone talk about the Davis.

Perhaps I am sending out data to the Davis network too and/or so often ... or 'storing' it to disk too often??
Anyone using a Davis care to help?

This is discouraging. My Weather Underground account has been having a bad day.

User avatar
N0BGS
Posts: 208
Joined: Sat Nov 10, 2012 2:26 am
Weather Station: Davis Vantage Pro 2
Operating System: Win7vm,VMWare ESXi 6.5
Location: Hermon, Maine USA
Contact:

Re: Mx Stopping

Postby N0BGS » Fri May 19, 2017 5:46 pm

Bob:

Can you explain a little about how your network is set up? Not clear to me why you'd need port forwarding enabled.

--Kurt
Blitzortung Station 1809

User avatar
KD7YZ
Posts: 70
Joined: Tue Mar 10, 2015 12:23 pm
Weather Station: Davis VP2
Operating System: Win 7 64bit
Location: Kentucky

Re: Mx Stopping

Postby KD7YZ » Fri May 19, 2017 6:21 pm

Single I5 win7/64 on an ASUS N66U Router via Ethernet cable.

Well, I have been having this problem for I guess a year .. Cumulus and now CumulusMX gets disconnected from Davis V P2+ po 32700 something according to the Diags "cumulus.018 file.

So I researched here and some had talked about needing port forwarding.

Anyway, the issue seems to be an irregular disconnect after 1 week or 3 days or several times in an afternoon ... of Cumulus to "station" ,,, which I guess is my VP2

User avatar
steve
Cumulus Author
Posts: 26141
Joined: Mon Jun 02, 2008 6:49 pm
Weather Station: None
Operating System: None
Location: On tour in France
Contact:

Re: Mx Stopping

Postby steve » Fri May 19, 2017 6:28 pm

I don't understand how port forwarding is related to this either. You shouldn't need any port forwarding for the communication between Cumulus and the logger - unless you're trying to run MX on a different network to the logger, e.g. across the internet.

Cumulus 1 uses a Davis DLL for its communication with the console/logger. It appears that this DLL may automatically reconnect to the console/logger if communication is lost. MX does not use this DLL and does not currently have any code for automatically reconnecting if communication is lost. I ran MX myself for many months with a TCP/IP logger and never once had the connection disconnnect, so it did not occur to me to put any code in to handle this situation.
Steve
-----
Hosting available for Cumulus web sites. See http://sandaysoft.com/forum/viewtopic.php?f=2&t=11876

Like Cumulus and want to support it? Please donate! Image

User avatar
N0BGS
Posts: 208
Joined: Sat Nov 10, 2012 2:26 am
Weather Station: Davis Vantage Pro 2
Operating System: Win7vm,VMWare ESXi 6.5
Location: Hermon, Maine USA
Contact:

Re: Mx Stopping

Postby N0BGS » Fri May 19, 2017 6:29 pm

I have that same wireless router.

OK, so your Asus router is the device that is facing the Internet? Like...computer-->Asus router-->Cable modem(??)-->Internet?

And your Davis is connecting to the CumulusMX via TCP/IP or via USB serial converter?

--Kurt
Blitzortung Station 1809

User avatar
KD7YZ
Posts: 70
Joined: Tue Mar 10, 2015 12:23 pm
Weather Station: Davis VP2
Operating System: Win 7 64bit
Location: Kentucky

Re: Mx Stopping

Postby KD7YZ » Fri May 19, 2017 7:16 pm

yes. Computer to ASUS AND Davis to ASUS ... then ASUS to Internet

BUT, in my endeavours to consolidate AND make sure at the same time, that I am using latest, I put it on on the C:\Drive

and now it won't run ... won't get started

I ran cumulusmx.exe as admin, which I am anyway ...in the same fashion I'd been doing it today and other days ...


=====================================================
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.1647.0
Problem Signature 06: 58d879f6
Problem Signature 07: 460
Problem Signature 08: 33
Problem Signature 09: System.ArgumentException
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

===========================================

User avatar
steve
Cumulus Author
Posts: 26141
Joined: Mon Jun 02, 2008 6:49 pm
Weather Station: None
Operating System: None
Location: On tour in France
Contact:

Re: Mx Stopping

Postby steve » Fri May 19, 2017 7:24 pm

This is also the same as a problem you previously reported. As I said last time, this appears to be a crash in the Windows .Net runtime, before Cumulus has been initialised. I don't know what you did to resolve this problem previously. I can't offer any help because it occurs before any Cumulus code is executed.
Steve
-----
Hosting available for Cumulus web sites. See http://sandaysoft.com/forum/viewtopic.php?f=2&t=11876

Like Cumulus and want to support it? Please donate! Image

User avatar
KD7YZ
Posts: 70
Joined: Tue Mar 10, 2015 12:23 pm
Weather Station: Davis VP2
Operating System: Win 7 64bit
Location: Kentucky

Re: Mx Stopping

Postby KD7YZ » Fri May 19, 2017 7:40 pm

Sorry for the detour.
I'd not copied some key ini's into the new. C:\cumulus dir

am now running as it should be and viewing the dials which are reading my davis

====================
Current culture: English (United States)
Serial: 5490216F9A3375DBD9E79DA4F7FF916D
Cumulus MX v.3.0.0 build 3043
Today.ini = data\today.ini
Last update=5/16/2017 14:13:00
Connected to station
15:27:57 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
5/19/2017 15:27:57
Type Ctrl-C to terminate
15:28:00 Downloading Archive Data
15:28:05 Normal running

========================

that said, I am running, it hasn't crashed yet .. and I appear to be operating from the C:\ drive rather than another HDD in system.

so if CumulusMX never again crashes then I am unsure why it crashed so many times today.

User avatar
N0BGS
Posts: 208
Joined: Sat Nov 10, 2012 2:26 am
Weather Station: Davis Vantage Pro 2
Operating System: Win7vm,VMWare ESXi 6.5
Location: Hermon, Maine USA
Contact:

Re: Mx Stopping

Postby N0BGS » Fri May 19, 2017 7:57 pm

Regarding the port forwarding, which I don't believe has anything to do with the problem you are experiencing, it shouldn't be necessary since any connection that is initiated by the computer to say, Weather Underground, is going to be allowed by the Asus. The only common scenario that you would want port forwarding configured is if you wanted to be able to get to the CMX web interface on port 8998 FROM the Internet side.

Is your Windows firewall turned on? Assuming you have the firewall enabled on the Asus I recommend you turn the Windows FW off since the computer is already behind a FW and the Windows FW can break things unless you have specifically set rules to allow them.

What file system permissions do you have set on the folder where Cumulus is installed? Recommend you set them like this:

perms.PNG


Finally, is your computer up to date as far as Windows Update is concerned? If not, make it so.

Apologies if you already know all this. I have no idea what your level of computer expertise is.

--K
You do not have the required permissions to view the files attached to this post.
Blitzortung Station 1809

User avatar
KD7YZ
Posts: 70
Joined: Tue Mar 10, 2015 12:23 pm
Weather Station: Davis VP2
Operating System: Win 7 64bit
Location: Kentucky

Re: Mx Stopping

Postby KD7YZ » Fri May 19, 2017 8:26 pm

N0BGS wrote:Is your Windows firewall turned on?


Win-7 no .. Kaspersky, Yes .

N0BGS wrote: Assuming you have the firewall enabled on the Asus I recommend you turn the Windows FW off since the computer is already behind a FW and the Windows FW can break things unless you have specifically set rules to allow them.


I believe I'll leave Kasp on CumulusMX is set as Trusted and can do what it wants, nearly.
I believe if the occasional problem was KT^S then the problem should manifest daily.

N0BGS wrote:What file system permissions do you have set on the folder where Cumulus is installed? Recommend you set them like this:

perms.PNG


They were not. Now they are.

N0BGS wrote:
Finally, is your computer up to date as far as Windows Update is concerned? If not, make it so.


Yes, it is.

User avatar
N0BGS
Posts: 208
Joined: Sat Nov 10, 2012 2:26 am
Weather Station: Davis Vantage Pro 2
Operating System: Win7vm,VMWare ESXi 6.5
Location: Hermon, Maine USA
Contact:

Re: Mx Stopping

Postby N0BGS » Fri May 19, 2017 9:58 pm

OK, well if you have set live/real-time or whatever the Kaspersky equivalent is for real-time scanning exclusions you should be good to go on that front.

If it goes down again check your Windows application event log and filter on critical, warnings, and errors and see if there is anything of interest and post it here.

Gud luck es 73,

--Kurt
Blitzortung Station 1809

User avatar
KD7YZ
Posts: 70
Joined: Tue Mar 10, 2015 12:23 pm
Weather Station: Davis VP2
Operating System: Win 7 64bit
Location: Kentucky

Re: Mx Stopping

Postby KD7YZ » Sat May 20, 2017 11:25 am

There are several 'Error' for different events and relating to CumulusMX.

one such:

"Application: CumulusMX.exe Framework Version: v4.0.30319 Description: The process was terminated due to an unhandled exception. Exception Info: System.ArgumentException at System.Timers.Timer.set_Interval(Double) at CumulusMX.Cumulus..ctor(Int32, Int32) at .Main(System.String[]) "

and an excerpt from another :
Version=1
EventType=CLR20r3
EventTime=131396947111970428
ReportType=2
Consent=1
ReportIdentifier=02d39c1d-3cc7-11e7-bf8c-402cf4eac557
IntegratorReportIdentifier=02d39c1c-3cc7-11e7-bf8c-402cf4eac557
WOW64=1
Response.type=4
Sig[0].Name=Problem Signature 01
Sig[0].Value=CumulusMX.exe
Sig[1].Name=Problem Signature 02
Sig[1].Value=1.0.0.0
Sig[2].Name=Problem Signature 03
Sig[2].Value=57b4b79a
Sig[3].Name=Problem Signature 04
Sig[3].Value=System
Sig[4].Name=Problem Signature 05
Sig[4].Value=4.6.1647.0
Sig[5].Name=Problem Signature 06
Sig[5].Value=58d879f6
Sig[6].Name=Problem Signature 07
Sig[6].Value=460
Sig[7].Name=Problem Signature 08
Sig[7].Value=33
Sig[8].Name=Problem Signature 09
Sig[8].Value=System.ArgumentException
DynamicSig[1].Name=OS Version
DynamicSig[1].Value=6.1.7601.2.1.0.256.48
DynamicSig[2].Name=Locale ID
DynamicSig[2].Value=1033
DynamicSig[22].Name=Additional Information 1
DynamicSig[22].Value=0a9e
DynamicSig[23].Name=Additional Information 2
DynamicSig[23].Value=0a9e372d3b4ad19135b953a78882e789
DynamicSig[24].Name=Additional Information 3
DynamicSig[24].Value=0a9e
DynamicSig[25].Name=Additional Information 4
DynamicSig[25].Value=0a9e372d3b4ad19135b953a78882e789
UI[2]=C:\CumulusMX\CumulusMX.exe
UI[3]=CumulusMX has stopped working
UI[4]=Windows can check online for a solution to the problem.
UI[5]=Check online for a solution and close the program
UI[6]=Check online for a solution later and close the program
UI[7]=Close the program
LoadedModule[0]=C:\CumulusMX\CumulusMX.exe
LoadedModule[1]=C:\Windows\SysWOW64\ntdll.dll
LoadedModule[2]=C:\Windows\SYSTEM32\MSCOREE.DLL
LoadedModule[3]=C:\Windows\syswow64\KERNEL32.dll
LoadedModule[4]=C:\Windows\syswow64\KERNELBASE.dll
LoadedModule[5]=C:\Windows\system32\apphelp.dll

User avatar
N0BGS
Posts: 208
Joined: Sat Nov 10, 2012 2:26 am
Weather Station: Davis Vantage Pro 2
Operating System: Win7vm,VMWare ESXi 6.5
Location: Hermon, Maine USA
Contact:

Re: Mx Stopping

Postby N0BGS » Sun May 21, 2017 2:43 am

Did CMX crash on that error or did it continue run?

Oh...on second look I see it did crash.
Blitzortung Station 1809


Return to “Cumulus MX”

Who is online

Users browsing this forum: No registered users and 3 guests