Гидра 4.2.3.21 периодически падает

Гидра 4.2.3.21 периодически падает
Atom
7/11/2014
Oldman


Приветствую всех.
Гидра 4.2.3.21

Периодически (через 4-6-8 часов работы) падает. Посоветуйте пожалуйста, чем помочь гидре проработать дольше :)

В Unhandled Exception.txt такой лог:

Code
16:48:37.639|Error  |Unhandled Exception|System.Exception: The socket is connected, you neednt' connect again!
   at Microsoft.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at Microsoft.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccess(Task task)
   at Pusher.Pusher.<<.ctor>b__2>d__5.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.AsyncMethodBuilderCore.<ThrowAsync>b__1(Object state)
   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()
16:48:37.940|Error  |Unhandled Exception|System.Exception: The socket is connected, you neednt' connect again!
   at Microsoft.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at Microsoft.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccess(Task task)
   at Pusher.Pusher.<<.ctor>b__2>d__5.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.AsyncMethodBuilderCore.<ThrowAsync>b__1(Object state)
   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()
20:42:05.809|Error  |Unhandled Exception|System.Exception: The socket is connected, you neednt' connect again!
   at Microsoft.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at Microsoft.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccess(Task task)
   at Pusher.Pusher.<<.ctor>b__2>d__5.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.AsyncMethodBuilderCore.<ThrowAsync>b__1(Object state)
   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()
20:42:05.890|Error  |Unhandled Exception|System.Exception: The socket is connected, you neednt' connect again!
   at Microsoft.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at Microsoft.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccess(Task task)
   at Pusher.Pusher.<<.ctor>b__2>d__5.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.AsyncMethodBuilderCore.<ThrowAsync>b__1(Object state)
   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()

Tags:


Thanks:


Oldman

Avatar
Date: 7/11/2014
Reply


В этот раз гидра упала спустя 30 минут. Еррор лога не записался, так что ошибки выше подозреваю вызваны чем-то другим :(

Второй момент в новой гидре с адаптером Quik - после запуска стартуют не все стаканы на вывод (каждый раз по разному, из 6 стаканов не стартует вывод 1-3)
Thanks:

Mikhail Sukhov

Avatar
Date: 7/11/2014
Reply


Oldman

Code
16:48:37.639|
   at Pusher.Pusher.<<.ctor>b__2>d__5.MoveNext()


А что за источник?
Thanks:

Oldman

Avatar
Date: 7/11/2014
Reply


Михаил Сухов
Oldman

Code
16:48:37.639|
   at Pusher.Pusher.<<.ctor>b__2>d__5.MoveNext()


А что за источник?


Включен был Quik, btc-e, bitstamp. Какие у них номера не знаю.
Thanks:


Attach files by dragging & dropping, , or pasting from the clipboard.

loading
clippy