extrange / ibkr-docker

Run IBKR Gateway/TWS in a Docker container
212 stars 41 forks source link

autorestart file not found #82

Closed 8W9aG closed 9 months ago

8W9aG commented 10 months ago

After running ibkr-docker for some time it seems to eventually exit with the following logs:

2024-02-01 00:17:41.561
2024-02-01 05:17:41:363 IBC: detected frame entitled: Connecting to server...; event=Opened
2024-02-01 00:18:16.261
2024/02/01 05:18:16 socat[245] N socket 2 (fd 5) is at EOF
2024-02-01 00:18:17.461
2024/02/01 05:18:17 socat[245] N exiting with status 0
2024-02-01 00:18:18.062
2024/02/01 05:18:18 socat[15] N childdied(): handling signal 17
2024-02-01 00:19:09.561
2024-02-01 05:19:09:362 IBC: detected dialog entitled: Shutdown progress; event=Opened
2024-02-01 00:19:19.462
2024-02-01 05:19:19:463 IBC: detected dialog entitled: API client needs write access action confirmation; event=Lost focus
2024-02-01 00:19:20.461
2024-02-01 05:19:19:661 IBC: detected dialog entitled: API client needs write access action confirmation; event=Deactivated
2024-02-01 00:19:22.360
2024-02-01 05:19:22:263 IBC: detected dialog entitled: Shutdown progress; event=Activated
2024-02-01 00:19:22.760
2024-02-01 05:19:22:662 IBC: detected dialog entitled: Shutdown progress; event=Focused
2024-02-01 00:19:22.761
2024-02-01 05:19:22:761 IBC: detected dialog entitled: IBKR Gateway; event=Opened
2024-02-01 00:19:23.461
2024-02-01 05:19:22:762 IBC: detected dialog entitled: Shutdown progress; event=Lost focus
2024-02-01 00:19:23.461
2024-02-01 05:19:23:461 IBC: detected dialog entitled: Shutdown progress; event=Deactivated
2024-02-01 00:19:25.261
2024-02-01 05:19:23:861 IBC: detected dialog entitled: IBKR Gateway; event=Activated
2024-02-01 00:19:26.161
2024-02-01 05:19:26:161 IBC: detected dialog entitled: IBKR Gateway; event=Focused
2024-02-01 00:19:26.161
2024-02-01 05:19:26:162 IBC: detected dialog entitled: API client needs write access action confirmation; event=Closed
2024-02-01 00:32:39.168
2024-02-01 05:32:38,962 JTS-ShutdownTask-Shutdown_IA-921 ERROR Attempted to append to non-started appender d
2024-02-01 00:32:42.268
2024-02-01 05:32:39,662 JTS-ShutdownTask-Shutdown_IA-921 ERROR Attempted to append to non-started appender d
2024-02-01 00:32:43.268
2024-02-01 05:32:42,762 NIA-Input-Queue-2 ERROR Attempted to append to non-started appender d
2024-02-01 00:32:44.261
2024-02-01 05:32:43,463 NIA-Input-Queue-2 ERROR Attempted to append to non-started appender d
2024-02-01 00:33:14.860
2024-02-01 05:33:14,662 pool-3-thread-1 ERROR Attempted to append to non-started appender f
2024-02-01 00:33:27.561
IBC returned exit status 0
2024-02-01 00:33:31.871
autorestart file not found
2024-02-01 00:33:31.871
Gateway finished

Are there some extra steps to prevent this from happening, such as producing a autorestart file?

extrange commented 9 months ago

IBC's autorestart feature has quite a few quirks.

IB Gateway insists on being restarted daily at least once. IBC can help with this, and the setting for the auto-restart is via the docker compose variable IBC_AutoRestartTime. No user authentication is required for this.

IB Gateway also insists on being fully restarted weekly (every Sunday at 1300 SGT). A manual login is required for this.

dmacd commented 1 month ago

Quick question - If I want the container to auto-restart after a scheduled Cold Restart, is the recommended way to do something like this?

services:
  ibkr:
    restart: unless-stopped
    ...

Or is there more explicit mechanism that is preferred?

Thanks!