Major MX crash tonight.

[UncleBuck]

Didn't notice a problem until I decided to just check it now.

It told me to zip up the files in the MXdiags folder and post them, so here they are.

[steve]

Two things of note from the diags file:

On the 20th at 19:28, it started having problems reading the data from the console - numerous 'data stopped' messages. This problem continued, and eventually it appears that no response at all was received from the console. I have no way of knowing what the cause was.

On the 20th at 20:00 an exception was logged while processing a web file - Mono doesn't give me enough information to say any more that that. It is probably this exception which printed the message to post the MXdiags files, but MX itself continued running.

[UncleBuck]

Now I just got this error....

System.ApplicationException: Mutex is not owned
at System.Threading.Mutex.ReleaseMutex () <0x2304340 + 0x0005a> in <filename unknown>:0
at (wrapper remoting-invoke-with-check) System.Threading.Mutex:ReleaseMutex ()
at System.Net.FtpClient.FtpClient.Dispose () <0x409d678 + 0x0022b> in <filename unknown>:0
at System.Net.FtpClient.FtpClient.Finalize () <0x409d638 + 0x00013> in <filename unknown>:0
**** An error has occurred - please zip up the MXdiags folder and post it in the forum ****

I have attached the latest MXdiags as well.

[steve]

2016-02-22 00:17:14.653 System.InvalidOperationException: Specified port is not open.

It looks like you're having problems with your USB/serial port - this may also explain your 'data stopped' problem.

[UncleBuck]

Checked the console and it was displaying a constant "R" in the bottom right corner of the display.
Checked the manual and it said to enter Setup Mode and then exit Setup Mode. Did that and the station started receiving data again. It even looks like it retained nearly all the data but there was a period lost between 2016-02-20 21:01:00 and 2016-02-21 02:05:00 (at least thats what the SQL database is showing).

Thanks guys.
At least I caught it early.

Col.