Cumulus Support

Upgrading from Cumulus 1 to Cumulus MX on Windows 10 pc - copied CMX build 1038 files to existing cumulus directory - all works well until WMX eventually crashes - runs from 5 to approx 30 min before crash with following error message:

2016-05-18 10:16:08.931 System.IO.IOException: Unable to write data to the transport connection: An existing connection was forcibly closed by the remote host. ---> System.Net.Sockets.SocketException: An existing connection was forcibly closed by the remote host
at System.Net.Sockets.Socket.Send(Byte[] buffer, Int32 offset, Int32 size, SocketFlags 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 )
at .()
at System.Threading.ThreadHelper.ThreadStart_Context(Object state)
at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Threading.ThreadHelper.ThreadStart()

Full Mxdiags zip file is attached.

Any help is greatly appreciated.

Dave

The console is disconnecting, probably because it's doing the upload to weatherlink.com - this has been the cause with others who have had this problem, and it looks like yours is the same. You could try increasing the disconnect interval, until I can get around to putting in some code to handle it and retry the connection.

Thanks Steve - I've tried resetting the Davis VP disconnect to 5, 10, 15, 25, and 40 - CMX runs just over an hour at the 40 setting before crashing with the same exception message.

Then presumably it's taking more than 40 seconds to upload to weatherlink.com, and I think the only solution is to turn off updates to weatherlink.com. MX has been running with my Weatherlink IP flawlessly for weeks on end - I don't upload to weatherlink.com. It's a design fault with the WLIP that it can't communicate with software at the same time as it is connected to weatherlink.com.

I stopped the weatherlink.com upload, reset the disconnect to 0, and CMX has been running like a champ for 7+ hrs.

Thanks Steve, another donation will be coming your way.

Thanks. It's unfortunate that they designed the IP logger this way. It's not helped by the fact that it's not documented anywhere, nor is any guidance given to third party software developers about how they are supposed to work around it.