the-hideout / TarkovMonitor

Monitor Tarkov log files to help track progress, queues, and groups
GNU General Public License v3.0
91 stars 16 forks source link

Exception while matching #81

Closed bitpushr closed 2 months ago

bitpushr commented 2 months ago

Getting the following while matching/searching for a raid after the latest update. Reverting back to the previous version of Tarkov Monitor resolves it.

2024-06-19 00:26:07.378 +10:00|Info|push-notifications|LongPollingWebSocketRequest WebSocketException:System.Net.WebSockets.WebSocketException (0x80004005): The remote party closed the WebSocket connection without completing the close handshake. ---> System.Net.WebSockets.WebSocketException (0x80004005): The remote party closed the WebSocket connection without completing the close handshake.
  at System.Net.WebSockets.ManagedWebSocket+<EnsureBufferContainsAsync>d__69.MoveNext () [0x00116] in <ef151b6abb5d474cb2c1cb8906a8b5a4>:0 
--- End of stack trace from previous location where exception was thrown ---
  at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw () [0x0000c] in <eae584ce26bc40229c1b1aa476bfa589>:0 
  at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess (System.Threading.Tasks.Task task) [0x0003e] in <eae584ce26bc40229c1b1aa476bfa589>:0 
  at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification (System.Threading.Tasks.Task task) [0x00028] in <eae584ce26bc40229c1b1aa476bfa589>:0 
  at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd (System.Threading.Tasks.Task task) [0x00008] in <eae584ce26bc40229c1b1aa476bfa589>:0 
  at System.Runtime.CompilerServices.ConfiguredTaskAwaitable+ConfiguredTaskAwaiter.GetResult () [0x00000] in <eae584ce26bc40229c1b1aa476bfa589>:0 
  at System.Net.WebSockets.ManagedWebSocket+<ReceiveAsyncPrivate>d__60.MoveNext () [0x0010d] in <ef151b6abb5d474cb2c1cb8906a8b5a4>:0 
  at System.Net.WebSockets.ManagedWebSocket+<ReceiveAsyncPrivate>d__60.MoveNext () [0x00654] in <ef151b6abb5d474cb2c1cb8906a8b5a4>:0 
--- End of stack trace from previous location where exception was thrown ---
  at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw () [0x0000c] in <eae584ce26bc40229c1b1aa476bfa589>:0 
  at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess (System.Threading.Tasks.Task task) [0x0003e] in <eae584ce26bc40229c1b1aa476bfa589>:0 
  at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification (System.Threading.Tasks.Task task) [0x00028] in <eae584ce26bc40229c1b1aa476bfa589>:0 
  at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd (System.Threading.Tasks.Task task) [0x00008] in <eae584ce26bc40229c1b1aa476bfa589>:0 
  at System.Runtime.CompilerServices.TaskAwaiter`1[TResult].GetResult () [0x00000] in <eae584ce26bc40229c1b1aa476bfa589>:0 
  at +.MoveNext () [0x00105] in <71141e9c225785fe20e8f9f156eb5213>:0 
--- End of stack trace from previous location where exception was thrown ---
  at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw () [0x0000c] in <eae584ce26bc40229c1b1aa476bfa589>:0 
  at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess (System.Threading.Tasks.Task task) [0x0003e] in <eae584ce26bc40229c1b1aa476bfa589>:0 
  at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification (System.Threading.Tasks.Task task) [0x00028] in <eae584ce26bc40229c1b1aa476bfa589>:0 
  at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd (System.Threading.Tasks.Task task) [0x00008] in <eae584ce26bc40229c1b1aa476bfa589>:0 
  at System.Runtime.CompilerServices.TaskAwaiter.GetResult () [0x00000] in <eae584ce26bc40229c1b1aa476bfa589>:0 
  at +.MoveNext () [0x0013b] in <71141e9c225785fe20e8f9f156eb5213>:0 
2024-06-19 00:26:07.378 +10:00|Info|push-notifications|long polling request finished error: 
2024-06-19 00:26:07.378 +10:00|Warn|push-notifications|Notification channel has been [dropped] by server error with code: 0
2024-06-19 00:26:07.378 +10:00|Info|push-notifications|Notification channel creation timeout:60
2024-06-19 00:26:07.378 +10:00|Info|push-notifications|LongPollingWebSocketRequest webSocket disposed
Razzmatazzz commented 2 months ago

PVP or PVE? Does this error show up in the messages window? If so, what does it say about what was happening when the error occurred?

bitpushr commented 2 months ago

Sorry,

PvE. It shows up in the Raw Logs window. Will endeavour to keep an eye out for when it happens again so I can catch it.

Razzmatazzz commented 2 months ago

The raw logs window just shows what's literally being written to the game logs. Tarkov Monitor doesn't have any impact on that, and I can't fix any errors the game itself is throwing, so there's nothing to fix here.