Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cannot start, exited with code 133 #131

Open
this-josh opened this issue Feb 7, 2024 · 1 comment
Open

Cannot start, exited with code 133 #131

this-josh opened this issue Feb 7, 2024 · 1 comment
Labels
bug Something isn't working

Comments

@this-josh
Copy link

Describe the bug
When trying to run the gateway it fails to start the container

To Reproduce
set

TWS_USERID
TWS_PASSWORD
TRADING_MODE
READ_ONLY_API

run docker-compose up

Expected behavior
The gateway container to run

Container logs
Error message, it tries to run again after about 15 seconds and faces the same issue

ib-gateway-1  | 2024-02-07 10:46:55:461 IBC: Using default settings provider: ini file is /root/ibc/config.ini
ib-gateway-1  | 2024-02-07 10:46:55:462 IBC: Using default login manager: getting username and password from args
ib-gateway-1  | 2024-02-07 10:46:55:462 IBC: Using default main window manager
ib-gateway-1  | 2024-02-07 10:46:55:462 IBC: Using default trading mode manager: constructor parameter args: tradingMode=paper
ib-gateway-1  | 2024-02-07 10:46:55:464 IBC: Using default config dialog manager
ib-gateway-1  | 2024-02-07 10:46:55:468 IBC: CommandServer is not started because the port is not configured
ib-gateway-1  | 2024-02-07 10:46:55:569 IBC: TWS Settings directory is: /root/Jts
ib-gateway-1  | 2024-02-07 10:46:55:574 IBC: Ensuring /root/Jts/jts.ini contains required minimal lines
ib-gateway-1  | 2024-02-07 10:46:55:575 IBC: Found setting: [Logon]/s3store=true
ib-gateway-1  | 2024-02-07 10:46:55:575 IBC: Found setting: [Logon]/Locale=en
ib-gateway-1  | 2024-02-07 10:46:55:575 IBC: Found setting: [Logon]/displayedproxymsg=1
ib-gateway-1  | 2024-02-07 10:46:55:575 IBC: Found setting: [Logon]/UseSSL=true
ib-gateway-1  | 2024-02-07 10:46:55:575 IBC: Found setting: [IBGateway]/ApiOnly=true
ib-gateway-1  | 2024-02-07 10:46:55:575 IBC: Confirmed /root/Jts/jts.ini contains required minimal lines
ib-gateway-1  | 2024-02-07 10:46:55:575 IBC: Starting Gateway
ib-gateway-1  | 2024-02-07 10:46:55:575 IBC: Starting session: will exit if login dialog is not displayed within 60 seconds
ib-gateway-1  | assertion failed [rem_idx != -1]: Unable to find existing allocation for shared memory segment to unmap
ib-gateway-1  | (VMAllocationTracker.cpp:745 remove_shared_mem)
ib-gateway-1  |  /root/ibc/scripts/ibcstart.sh: line 468:   125 Trace/breakpoint trap   "$java_path/java" -cp "$ibc_classpath" $java_vm_options$autorestart_option $entry_point "$ibc_ini" "$ib_user_id" "$ib_password" ${mode}
ib-gateway-1  | IBC returned exit status 133
ib-gateway-1  | Renaming TWS or Gateway .exe file to original name
ib-gateway-1  | 
ib-gateway-1  | Gateway finished
ib-gateway-1  | 
ib-gateway-1 exited with code 133

Versions (please complete the following information):

  • OS: MacOS 14.3, M1 Max
  • Docker version: Docker version 25.0.2, build 29cf629
  • Image Tag (docker --version): latest
  • Image Digest (docker images --digests): sha256:5f3311ed8dab171e5f955fdeca15ca269cea899577b82ad5955c5956e13461c3
@this-josh this-josh added the bug Something isn't working label Feb 7, 2024
@Jeffreylabranche
Copy link

I have the exact same issue with M1 as well...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants