-
Notifications
You must be signed in to change notification settings - Fork 181
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
remove Client 0 message #108
Comments
Just set:
or
in your config.ini file. |
I didn’t realize that you added this in ecb6f3d#diff-c8d8d62a34800f1c969ec30de080d73cb3d46a102c697d8d4b942e973c615f6f That’s great! I’ve got to wait until Monday to check that the whole thing populates the database with data. I’ll check back in then. |
Still having some problems, but I'm beginning to suspect it's something else with teh config of the mysql db. Here is the tail end of my docker logs
|
The message 'remove Client 0' is nothing to do with IBC. I think TWS/Gateway logs it when an API client disconnects. So there is no information at all here that I can use to help you. The IBC logfile contains a lot of useful information, so you could attach that and I can then see if it looks like IBC is working - assuming you're actually creating the IBC logfile. Note that you need to run IBC from the gatewaystart.sh script to have an IBC logfile created automatically. But if you use ibcstart.sh to start it, you could create your own logfile and redirect stdout to it when you run the script. Or maybe your using some other logging mechanism? |
I am using If I jump into the client app's container and use a shell to run the trade client manually, I get this:
That error seems to say I'm getting an unhandled error in my own client code. Judging by my client code, it looks like my call to It looks like this is outside the realm of IBC, so I will close the issue. Thanks for your help! |
I keep getting this
remove Client 0
message in my Docker Compose project. I see that this has been discussed elsewhere so I am trying to figure out this Read-Only API true default issue.I follow the following instructions, but every time I complete the following steps, the Read-Only option is set back to true even after I have set it to false.
docker-compose up --build
and wait until I seeremove Client 0
docker ps -a
to get the CONTAINER_ID for the image "dockerized_logger_tws". For me it isdcffeeb7d754
docker exec -it dcffeeb7d754 /bin/bash
mkdir ~/.vnc && echo "mylongpassword" > ~/.vnc/passwd && x11vnc -passwd mylongpassword -display ":99" -forever -rfbport 5900
127.0.0.1:5901
When it prompts me for a password, I typemylongpassword
docker ps -a
docker-compose stop
docker-compose up
ordocker-compose up -d
But then I get the same message as before:
remove Client 0
I'm new to Docker so maybe the containers, when they get "rebuilt" (not sure if that's the right word) they clear out the saved progress made to
/root/Jts/*encrypted user id*/ibg.xml
?The text was updated successfully, but these errors were encountered: