Welcome to the Cumulus Support forum.

Latest Cumulus MX V3 release 3.28.6 (build 3283) - 21 March 2024

Cumulus MX V4 beta test release 4.0.0 (build 4017) - 17 March 2024

Legacy Cumulus 1 release v1.9.4 (build 1099) - 28 November 2014 (a patch is available for 1.9.4 build 1099 that extends the date range of drop-down menus to 2030)

Download the Software (Cumulus MX / Cumulus 1 and other related items) from the Wiki

MX v3.19.3 b3196 crash

From build 3044 the development baton passed to Mark Crossley. Mark has been responsible for all the Builds since. He has made the code available on GitHub. It is Mark's hope that others will join in this development, but at the very least he welcomes your ideas for future developments (see Cumulus MX Development suggestions).

Moderator: mcrossley

Post Reply
freddie
Posts: 2434
Joined: Wed 08 Jun 2011 11:19 am
Weather Station: Davis Vantage Pro 2 + Ecowitt
Operating System: GNU/Linux Ubuntu 22.04 LXC
Location: Alcaston, Shropshire, UK
Contact:

MX v3.19.3 b3196 crash

Post by freddie »

I've seen an unhandled exception that caused a crash. From ServiceConsoleLog.txt:

Code: Select all

2022-07-27 14:07:50.867 Normal running
2022-08-09 16:36:08.279 Error opening serial port - No such device or address
2022-08-09 16:36:08.280 Will retry in 30 seconds...
System.NullReferenceException: Object reference not set to an instance of an object
  at MySqlConnector.MySqlConnection.Cancel (MySqlConnector.Core.ICancellableCommand command, System.Int32 commandId, System.Boolean isCancel) [0x0017b] in <0991038b67db401dac35361600119a9a>:0
  at MySqlConnector.MySqlCommand.CancelCommandForTimeout () [0x00016] in <0991038b67db401dac35361600119a9a>:0
  at MySqlConnector.Utilities.TimerQueue.Callback (System.Object obj) [0x000cb] in <0991038b67db401dac35361600119a9a>:0
  at System.Threading.Timer+Scheduler.TimerCB (System.Object o) [0x00007] in <12b418a7818c4ca0893feeaaf67f1e7f>:0
  at System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem () [0x00019] in <12b418a7818c4ca0893feeaaf67f1e7f>:0
  at System.Threading.ThreadPoolWorkQueue.Dispatch () [0x00096] in <12b418a7818c4ca0893feeaaf67f1e7f>:0
  at System.Threading._ThreadPoolWaitCallback.PerformWaitCallback () [0x00000] in <12b418a7818c4ca0893feeaaf67f1e7f>:0
**** An error has occurred - please zip up the MXdiags folder and post it in the forum ****
From latest MXdiags file:

Code: Select all

2022-08-10 10:41:52.251 Realtime[77]: Failed MySQL updates are present
2022-08-10 10:41:52.252 MySqlCheckConnection: Connected to server ok, default database = weathermx
2022-08-10 10:41:52.367 CustomSqlSecs: Error encountered during MySQL operation = The Command Timeout expired before the operation completed.
2022-08-10 10:41:52.370 !!! Unhandled Exception !!!
System.NullReferenceException: Object reference not set to an instance of an object
  at MySqlConnector.MySqlConnection.Cancel (MySqlConnector.Core.ICancellableCommand command, System.Int32 commandId, System.Boolean isCancel) [0x0017b] in <0991038b67db401dac35361600119a9a>:0
  at MySqlConnector.MySqlCommand.CancelCommandForTimeout () [0x00016] in <0991038b67db401dac35361600119a9a>:0
  at MySqlConnector.Utilities.TimerQueue.Callback (System.Object obj) [0x000cb] in <0991038b67db401dac35361600119a9a>:0
  at System.Threading.Timer+Scheduler.TimerCB (System.Object o) [0x00007] in <12b418a7818c4ca0893feeaaf67f1e7f>:0
  at System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem () [0x00019] in <12b418a7818c4ca0893feeaaf67f1e7f>:0
  at System.Threading.ThreadPoolWorkQueue.Dispatch () [0x00096] in <12b418a7818c4ca0893feeaaf67f1e7f>:0
  at System.Threading._ThreadPoolWaitCallback.PerformWaitCallback () [0x00000] in <12b418a7818c4ca0893feeaaf67f1e7f>:0
2022-08-10 10:41:52.381 LOOP: Data - 38: 4C-4F-4F-EC-00-8A-07-61-76-2A-03-2B-27-03-01-02-B4-00-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-2E-FF-FF-FF-FF-FF-FF-FF-00-00-FF-FF-7F-00-00-FF-FF-00-00-08-00-8C-05-00-00-00-00-EE-00-FF-FF-FF-FF-FF-FF-FF-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-1C-03-06-09-BD-01-9B-07-0A-0D-8D-92
2022-08-10 10:41:52.381 LOOP: 38 - Data packet is good
Looking at the ServiceConsoleLog.txt, it appears that the "Error opening serial port" is from yesterday, so probably unrelated to the crash, which occurred at 10:41 today. There are no error messages before or after the snippet of MXdiags logfile reproduced above.

There was a brief network dropout just before the crash.
Freddie
Image
User avatar
mcrossley
Posts: 12689
Joined: Thu 07 Jan 2010 9:44 pm
Weather Station: Davis VP2/WLL
Operating System: Bullseye Lite rPi
Location: Wilmslow, Cheshire, UK
Contact:

Re: MX v3.19.3 b3196 crash

Post by mcrossley »

The next build has all the MySQL errors fully trapped so you should not see this again.
freddie
Posts: 2434
Joined: Wed 08 Jun 2011 11:19 am
Weather Station: Davis Vantage Pro 2 + Ecowitt
Operating System: GNU/Linux Ubuntu 22.04 LXC
Location: Alcaston, Shropshire, UK
Contact:

Re: MX v3.19.3 b3196 crash

Post by freddie »

Okay, thank you.
Freddie
Image
Post Reply