Closed andreyohiienko closed 1 month ago
https://github.com/erdewit/ib_insync/issues/386#issuecomment-1001161053 most likely it is connected to this issue But how to prevent it is a question.
lsof -i :4002 COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME java 50 root 56u IPv6 137291 0t0 TCP localhost:4002->localhost:46418 (ESTABLISHED) java 50 root 60u IPv6 48900 0t0 TCP *:4002 (LISTEN) java 50 root 78u IPv6 238033 0t0 TCP localhost:4002->localhost:43734 (ESTABLISHED) java 50 root 80u IPv6 310694 0t0 TCP localhost:4002->localhost:39618 (CLOSE_WAIT) < ==== THIS ONE socat 260 root 5u IPv4 138298 0t0 TCP localhost:46418->localhost:4002 (ESTABLISHED) socat 1618 root 5u IPv4 237438 0t0 TCP localhost:43734->localhost:4002 (ESTABLISHED)
is there any way to prevent this?
Encountered the same issue, not sure how to solve this.
When I tried to kill the process that has CLOSE_WAIT
connection, the docker container died 😭.
Have u managed to find a solution for this issue?
@dchien234 No ( I think killing the process is not a solution. The process should not block the port after tws disconnection.
erdewit/ib_insync#386 (comment) most likely it is connected to this issue But how to prevent it is a question.
Yea, it is probably related to ib_insync
, and not related to wrapping IBKR in docker. Closing for now.
Hi, I really enjoy your TWS image, but I've faced with one problem recently. At some point in time connections start failing. The UI keeps running ok, but I can't connect to API. Here is my container logs:
and ib insync returns:
The problem is I can't catch the real reason of this problem because it can run without any problems for hours. I used recent
ghcr.io/extrange/ibkr:stable
then downgraded toghcr.io/extrange/ibkr:10.19.2d
but the problem appeared there too. And only container restart fixes the problem. Both TWS and IB GW have this issue.Will be grateful for any advice. Thanks.