No Live Data but logger data seems fine

[josesimas]

Hello,

I have had CumulusMX connected a WS3083 for a few months without any issues. A couple of weeks ago I woke up to a restarted computer thanks to MS updates (Windows 10). I restarted CumulusMX but since then the Dashboard, Now and Gauges pages don't show the live data. I can see the data on all the other pages (Today/Yesterday, Charts, etc). If I stop CumulusMX and start the Win32 Cumulus everything works fine.

Is there a setting that governs this feature I may have turned off by mistake? Looking at the logs I see no errors. I wonder if someone has had this issue before?

Jose

[steve]

Those three pages use web sockets by default to get their data, so it sounds like Windows is stopping that working. If you can't work out how to get web sockets working again, you can switch to using Ajax instead - see the announcement for build 3032 for how to do that. Note that this is specifically mentioned in the MX FAQ!

[Fedx]

Dear friends,
i can't download any data. I can't see live data and datalog. Why this happens?
I follow all your rules.
Thank for your time.

[steve]

i can't download any data. I can't see live data and datalog. Why this happens?
I follow all your rules.

Is it not downloading data from the station, or is it that you can't see any data in the user interface in your browser? If you zip up the MX diags folder and attach it, I'll take a look. What version of Mono are you using?

[Fedx]

I'm a new user of Linux so...thanks for your help Steve.
I think my mono version in 3.2.8. I can't see live data using Chromium on the address 192.168.x.xx:8998. There are no downloaded data.
Thank you again.

[Fedx]

Steve now Cumulus is working!
I have all data and live data.

[steve]

You have selected a station type of "Easyweather", i.e. data supplied from an easyweather.dat file, but you apparently haven't configured the path to your easyweather.data file, or not configured it correctly:

2016-08-21 02:06:42.567 Easyweather file not found

Did you mean to use an 'easyweather.dat' file, or should you actually be using "Fine Offset" for the station type to get Cumulus to talk to it directly?

[Clak]

Steve I have a similar issue. Been away for 6 weeks with iMAx shut down but my logger still working. Using MX release 3041 on Max OSX 10.11.6 and thanks for the update. The attached log file from the Diags folder shows that the data for the absent weeks is being downloaded, but there seems to be an error writing the previous months data into the files. The result is that there is no data showing in the web interface.

Error message is:

System.IO.IOException: data/month201608.ini already exists
at System.IO.File.Copy (System.String sourceFileName, System.String destFileName, Boolean overwrite) <0x19ff750 + 0x00477> in <filename unknown>:0
at System.IO.File.Copy (System.String sourceFileName, System.String destFileName) <0x19ff710 + 0x0002c> in <filename unknown>:0
at . (DateTime ) <0x36beb30 + 0x001d7> in <filename unknown>:0
at . (DateTime ) <0x36af000 + 0x0329b> in <filename unknown>:0
at . () <0x36a9c10 + 0x0014b> in <filename unknown>:0
at . (System.Object , System.ComponentModel.RunWorkerCompletedEventArgs ) <0x36a9598 + 0x0006b> in <filename unknown>:0
at System.ComponentModel.BackgroundWorker.OnRunWorkerCompleted (System.ComponentModel.RunWorkerCompletedEventArgs e) <0x36a9528 + 0x00056> in <filename unknown>:0
at System.ComponentModel.BackgroundWorker.AsyncOperationCompleted (System.Object arg) <0x36a94d0 + 0x0003c> in <filename unknown>:0
at System.Threading.QueueUserWorkItemCallback.WaitCallback_Context (System.Object state) <0x194eaf0 + 0x0004f> in <filename unknown>:0
at System.Threading.ExecutionContext.RunInternal (System.Threading.ExecutionContext executionContext, System.Threading.ContextCallback callback, System.Object state, Boolean preserveSyncCtx) <0x1948700 + 0x001a4> in <filename unknown>:0
at System.Threading.ExecutionContext.Run (System.Threading.ExecutionContext executionContext, System.Threading.ContextCallback callback, System.Object state, Boolean preserveSyncCtx) <0x19486c0 + 0x00033> in <filename unknown>:0
at System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem () <0x194ea60 + 0x0005a> in <filename unknown>:0
at System.Threading.ThreadPoolWorkQueue.Dispatch () <0x194d110 + 0x001d8> in <filename unknown>:0
at System.Threading._ThreadPoolWaitCallback.PerformWaitCallback () <0x194e8d0 + 0x00017> in <filename unknown>:0
**** An error has occurred - please zip up the MXdiags folder and post it in the forum ****

[steve]

The problem is actually that something went wrong at the system level while downloading the logger data from the console:

2016-08-31 21:27:08.549 9:27:08 PM Read logger entry for 22/07/2016 4:33:06 AM address BD60: 1E 48 88 00 5B 6F 00 77 24 07 14 00 0E CB 1A 00
2016-08-31 21:27:08.581 Day reset required

It only managed to get data back as far as the 22nd July, when it actually needed data back to 15th July. Something (in the system USB drivers, probably) has caused the data reading thread to crash silently such that it doesn't get around to processing the data that is has downloaded. Between those two logged messages should be a message indicating how many entries it has downloaded, and then messages showing it processing those entries. Because the thread is suddenly terminated, with no error message from the system, it's not possible for me to say what the cause of the problem was.

After the data reading thread is terminated, it then spots that there is a gap in the data so tries to do a day reset so that it can at least start doing today's data, but this results in the crash for which you've posted the stack trace. I'm not sure why this happens, when I get chance I'll investigate.

What you could try is to 'rewind' by copying the files from the backup folder created when MX started up:

2016-08-31 21:22:05.352 Creating backup folder backup/20160831212205/

You will also need to delete any files in the data folder which are for August (or September). When you start MX again, it will try to download the missing data again.

If the same problem still occurs, then I am afraid that it is not possible for Cumulus to obtain all of the required data from the logger.

[Clak]

Thanks Steve. I now note that all the logger data (minus a few hours from 31 Aug 23:35 - 2 Sep 10:00) is in the data files. The problem is now I am unable to get the program to run. The exception error occurs as it is looking for the station. I have tried a clean install, with the same result. Perhaps I have corrupted my Cumulus.ini file? Any thoughts would be appreciated.

Error data (truncated)
Looking for Fine Offset station, VendorID=0x1941 ProductID=0x8021
System.MissingMethodException: Method 'Mono.Unix.Native.Syscall.uname' not found.
at System.RuntimeType.InvokeMember (System.String name, BindingFlags bindingFlags, System.Reflection.Binder binder, System.Object target, System.Object[] providedArgs, System.Reflection.ParameterModifier[] modifiers, System.Globalization.CultureInfo culture, System.String[] namedParams) <0x18859d0 + 0x0106b> in <filename unknown>:0

[steve]

Seems to be a problem with your Mono installation:

System.MissingMethodException: Method 'Mono.Unix.Native.Syscall.uname' not found.

That's a bit odd as it was clearly working before. I don't know what to suggest other than reinstalling Mono. Or does it come already installed in OS X, I forget.

[Clak]

Steve I now have been able to get the program to run and show current information by going back to a very old Cumulus.ini file. However it still has errors in startup allbeit different from the earlier error messages. Historic information does not seem to have been loaded in spite of it being in the data files. Any help appreciated.

[steve]

If you zip up the MXdiags folder and attach it, I'll see if I can see what's going on.

[Clak]

Thanks Steve. I have been successful in getting all the data from the logger in an old version of Cumulus (1.9.4) on my windows machine. The logger and the windows version of the old program are operating normally there. However the same errors (below) show on terminal when starting the MX version on the iMAc in spite of a clean install using the Cumulus.ini and data files from the successful windows load. No current data is available in the MX output but all the historic data is now in the charts and record views. Curious.

Reinstalled mono to the latest version - same error message in terminal

Looking for Fine Offset station, VendorID=0x1941 ProductID=0x8021
System.MissingMethodException: Method 'Mono.Unix.Native.Syscall.uname' not found.
at System.RuntimeType.InvokeMember (System.String name, BindingFlags bindingFlags, System.Reflection.Binder binder, System.Object target, System.Object[] providedArgs, System.Reflection.ParameterModifier[] modifiers, System.Globalization.CultureInfo culture, System.String[] namedParams) <0x20859d0 + 0x0106b> in <filename unknown>:0
at System.Type.InvokeMember (System.String name, BindingFlags invokeAttr, System.Reflection.Binder binder, System.Object target, System.Object[] args, System.Globalization.CultureInfo culture) <0x2167890 + 0x0005a> in <filename unknown>:0
at HidSharp.Platform.Linux.NativeMethods.uname (System.String& sysname, System.String& release, System.String& machine) <0x3b652b8 + 0x000bb> in <filename unknown>:0
at HidSharp.Platform.Linux.NativeMethods.uname (System.String& sysname, System.Version& release, System.String& machine) <0x3b64fc0 + 0x00033> in <filename unknown>:0
at HidSharp.Platform.Linux.LinuxHidManager.get_IsSupported () <0x3b64ae8 + 0x00043> in <filename unknown>:0
Not supported
Fine Offset station found
Connected to station

[steve]

As far as I can tell, it's working fine. If you can't see live data using the Cumulus UI, then perhaps you have a problem with web sockets, which is what this thread was about to begin with (albeit by a different user). If all of the screens apart from Dashboard, Now and Gauges are showing data, then as described above and in the MX FAQ, if you can't work out how to get web sockets working again, you can switch to using Ajax instead - see the announcement for build 3032 for how to do that.