Closed radekwlsk closed 6 years ago
The warning is likely not something serious but i will look into how it can be avoided.
@erdewit so my initialization of Watchdog
is good and it works fine then, yes? Because the TWS freezes for me everyday when run with ib-controller
24/7. I hope it will resolve the problems.
To restart 'manually' is calling Watchdog.scheduleRestart()
at predefined hour enough? I would like to restart the ib-controller
and therefore IBGateway at 2:30 UTC each day.
@AfroMetal the watchdog instantiation looks okay. The use of the threading and socketserver module looks a bit troubling in the sense that they do not work well with asyncio so I hope you have thought that through.
For a manual restart, first do watchdog.stop() and then watchdog.scheduleRestart(). In my experience the gateway is restarted at least once a day anyway because of either timeout or error 1100.
@erdewit would you recommend moving to multiprocessing
instead of threading
?
@AfroMetal I can't really recommend anything as I have no clue what your project looks like. For myself I prefer asyncio in a single thread and use distex to farm out to other processes.
This should be no longer a problem.
ib_insync 0.9.3
I am getting this warning when using new
Watchdog
. It uses one of 3IB
s that are connected all the time, to keep TWS alive with ib-controller.Watchdog
and other 2IB
s are run in separatethreading.Thread
that is the live algorithm using those clients.First
IBController
is created:Then
Watchdog
is initialized and started:Is there anything else that I have to do?