Cumulus Support

10 seconds for realtime and 5 minute for standard uploads.

Hi,

After a long time without crash, updating to v3.6.1 and later v3.6.2 also crashing my CumulusMX setup on the RPi.
I'm using 5 minutes FTP intervals.

Ta, it ran for 2 hours without an error, so just restarted it with plain FTP and 10 sec/5 min settings.
Only other problem is that my debug env runs on Windows, so it could be a mono "thing".

Using the older dll with 3.6.2 MX ran fine for 110 minutes without crashing.

Can you tell me what versions of mono you are running please?
I cannot reproduce this on Windows or Debian with mono 6.8.0

Mono JIT compiler version 5.18.0.268 (tarball Tue Mar 12 14:29:07 UTC 2019)

That version is a little old, so I could be using a newer version, but I stayed with that version a while ago when mono caused issues with the date format.

I have the same issue since updating to 3.6.2. Sockets problem, no web updates and Cumulus stopped. My web updates are at 10 minute intervals. It will run for about 12 hours before it stops. When I try to stop the process and restart Cumulus the stop command errors because the process has already stopped. Restarts work fine. I'll try the old FluentFTP.dll from version 3077 and see how it goes.
Cheers
PeterB

Hi Mark

It didn't last 12 hours this time. Below is from the Raspberry Pi terminal screen. Hope it helps.
Thanks

PeterB

pi@raspberrypi:~ $ cd /home/pi/cumulus;sudo mono CumulusMX.exe -lang en-AU
Current culture: English (Australia)
Cumulus MX v.3.6.2 build 3078
Today.ini = data/today.ini
Last update=2020-05-21T08:10:00
Looking for Fine Offset station
Fine Offset station found
Connected to station
Cumulus running at: http://*:8998/
(Replace * with any IP address on this machine, or localhost)
Open the admin interface by entering this URL in a browser.
21/05/2020 8:13:18 AM
Type Ctrl-C to terminate
Downloading Archive Data
Normal running
System.ObjectDisposedException: The object was used after being disposed.
at System.Threading.WaitHandle.CheckDisposed () [0x00000] in <filename unknown>:0
at System.Threading.EventWaitHandle.Set () [0x00000] in <filename unknown>:0
at (wrapper remoting-invoke-with-check) System.Threading.EventWaitHandle:Set ()
at System.Net.Sockets.Socket+SocketAsyncResult.set_IsCompleted (Boolean value) [0x00000] in <filename unknown>:0
at System.Net.Sockets.Socket+SocketAsyncResult.Complete () [0x00000] in <filename unknown>:0
at System.Net.Sockets.Socket+Worker.Receive () [0x00000] in <filename unknown>:0
at System.Net.Sockets.Socket+Worker.DispatcherCB (System.Net.Sockets.SocketAsyncResult sar) [0x00000] in <filename unknown>:0
**** An error has occurred - please zip up the MXdiags folder and post it in the forum ****
Press Enter to terminate
System.ObjectDisposedException: The object was used after being disposed.
at System.Threading.WaitHandle.CheckDisposed () [0x00000] in <filename unknown>:0
at System.Threading.EventWaitHandle.Set () [0x00000] in <filename unknown>:0
at (wrapper remoting-invoke-with-check) System.Threading.EventWaitHandle:Set ()
at System.Net.Sockets.Socket+SocketAsyncResult.set_IsCompleted (Boolean value) [0x00000] in <filename unknown>:0
at System.Net.Sockets.Socket+SocketAsyncResult.Complete () [0x00000] in <filename unknown>:0
at System.Net.Sockets.Socket+Worker.Receive () [0x00000] in <filename unknown>:0
at System.Net.Sockets.Socket+Worker.DispatcherCB (System.Net.Sockets.SocketAsyncResult sar) [0x00000] in <filename unknown>:0
**** An error has occurred - please zip up the MXdiags folder and post it in the forum ****
Press Enter to terminate
424;1R

I also got into serious trouble when upgrading from 3.6.0 to 3.6.2.
Unfortunately I have no mxdiag where -debug is turned on.
One reflection I did was that RPI went slow, wifi ran totally crazy.
I found no other way then to downgrade to 3.6.0, no problems at all after the downgrade.

mono versions please.

Mono JIT compiler version 6.8.0.105 (tarball Tue Feb 4 21:51:48 UTC 2020)
Copyright (C) 2002-2014 Novell, Inc, Xamarin Inc and Contributors. www.mono-proj ect.com
TLS: __thread
SIGSEGV: normal
Notifications: epoll
Architecture: armel,vfp+hard
Disabled: none
Misc: softdebug
Interpreter: yes
LLVM: yes(610)
Suspend: preemptive
GC: sgen (concurrent by default)

Ah well, that's a mono 5.18 problem ruled out then!

I have posted version 3.6.3 which reverts back to the same FTP component as 3.6.0. I hope this fixes your issues.

Thank !

Trying to upgrade later this evening.
Have a nice day !

Thanks Mark.

No crash after upgrading to 3.6.3 which I had running for 2 hours so far. So it looks like its working correctly now.