MXDiags Attached - Error and Unhandled Exceptions b3241 - SoJo Wx

[jwpetrov]

Hello all:

I have attached the MXDiags file for b3241. There is a previously reported Error in the log. Further down there are some Unhandled Exception messages that also show up in the CMX runtime dialog form.

As a reminder CMX is using the PHP upload option. Even with the Error and Exceptions the .json and realtimegauges.txt files appear to be uploading properly.

Jed
South Jordan Weather

[forestedge]

Further down there are some Unhandled Exception messages that also show up in the CMX runtime dialog form.

I have been having similar problems and so reverted to b3235 for the moment with no unhandled errors on the CMX dialogue screen. Also using php upload fine.

[HansR]

I see one error in the log for the upload.php. That means during more than one whole day there is only one upload error.
If you do not see any additional failures I would just ignore this. I assume CMX recovers and restores the connection.

Yes, something, some transfer, missed on the internet.
It happens. It does not look like a full system failure.

[jwpetrov]

I see one error in the log for the upload.php. That means during more than one whole day there is only one upload error.
If you do not see any additional failures I would just ignore this. I assume CMX recovers and restores the connection.

Yes, something, some transfer, missed on the internet.
It happens. It does not look like a full system failure.

Yes, Hans, I would agree the upload.php error isn't an issue in this case. I'm wondering if the Unhandled Exceptions are anything to be concerned about. As mentioned, these messages are showing up in the MXDiag runtime dialog.

Jed

[HansR]

Yes, Jed, anything unhandled should be avoided and as this is a system exception I think Mark should have a look. Too deep for me Though even this exception does not break and CMX simply continues. That's good

Code: Select all

2023-04-28 15:50:01.493 !!! Unhandled Exception !!!
System.ArgumentException: The tasks array included at least one null element.
Parameter name: tasks
   at System.Threading.Tasks.Task.WaitAll(Task[] tasks, Int32 millisecondsTimeout, CancellationToken cancellationToken)
   at CumulusMX.Cumulus.<DoIntervalUpload>d__944.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at CumulusMX.Cumulus.<DoHTMLFiles>d__941.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   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.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem()
   at System.Threading.ThreadPoolWorkQueue.Dispatch()
2023-04-28 15:50:02.288 SendLoopCommand: Starting - LPS 2 1