You should have let the installer install to its default location, which is /home/pranav/Jts/ibgateway/1022

?

This being the case, IBC should find the jars folder at /home/pranav/Jts/ibgateway/1022/jars. If it’s not there, it must be because you didn’t use the installer’s default location.

?

If you actually used the TWS installer, the default location would be /home/pranav/Jts/1022, and the jars folder would be at /home/pranav/Jts/1022/jars

?

Since IBC isn’t finding the jars folder, either you didn’t install the standalone (offline) version, or you changed the installer’s location from the default.

?

By the way, you don’t seem to have successfully deployed the updated IBC.jar and version files, as your logfile still says it’s IBC 3.16.2, not 3.16.3.

?

Richard

?

Hi Richard and all,

?

I upgraded to version 1022 and have updated to the file mentioned in the below message. However, ibc is unable to find the gateway.

?

I have installed in the standard path.

?

?

I have attached the complete ibc log to this message.

Pranav

?

Well, I think you really need to fix the problem with TightVNC. I can’t give you any advice about that.

?

Other than that, not sure what you can do other than standard Linux commands over SSH.

?

Regarding log files, IBC took a silly decision several years ago to encrypt the Gateway and TWS logfiles, as you’ve discovered. The launcher.log file only contains information from the startup phase, so it will never tell you about anything later. And to view the encrypted logfiles you have to use the GUI, which is a bit tricky if your VNC session is inaccessible (you REALLY need to fix that problem…!).

?

The only other thing is the IBC logfile, but that won’t tell you much either. Though if IBC has shutdown for some reason, that should be recorded in the logfile.

?

Oh, there is one other possibility: you can use IBC’s command sever port (see the settings for this in config.ini) to send a dummy command, say “HELLO”, and you’ll get an ‘ERROR Command invalid’ response if IBC is running. You can send such a command using telnet, for example:

?

telnet 10.252.0.7 7462

?

Here 10.252.0.7 is the IP address of my server running Gateway, and 7462 is the port number configured for the IBC command server. This will start an interactive telnet session if IBC is running, then just type in any command (other than STOP and RESTART which do exactly what they say).

?

Alternatively you could script this:

?

(echo restart; sleep 1; echo "HELLO" ) | telnet 10.252.0.7 7462

?

Richard

[NB: if you are not trying to use Gateway 10.22 there is no need for you to take any action, so just ignore this.]

?

It’s come to my attention that IBC 3.16.2 and earlier doesn’t work properly with Gateway 10.22: it fails to fill in the username and password when logging in (but TWS 10.22 is fine).

?

This is because of a change to the window title of the login dialog that IB have made: it used to be ‘IB Gateway’ and now it’s ‘IBKR Gateway’. Consequently IBC doesn’t recognise it as the login dialog, and ignores it.

?

I have fixed the problem and a new version is accessible on GitHub, but I haven’t actually yet created a new release in the usual way. There are other things that need to go into the next release, and I’m not quite ready for it.

?

So in the meantime you can download the new version of the following files from :

?

IBC.jar

version

?

Just download these two files directly and copy them over the current versions in your IBC installation folder. No other changes are necessary.

?

After deploying these files, IBC will identify as version 3.16.3 in the logfiles.

?

Richard

?

The version number shown in the window is taken from a text file called ‘version’ (no file extension) that is located in your IBC folder.

?

When you upgrade by putting a new IBC.jar file in that folder, you must also copy in the corresponding ‘version’ file.

?

So I suspect your ‘version’ file is just out-of-date.

?

Richard

?

?

Line 26 has a DOS comment indicator rather than a Bash one at the start of the line. Hence the error. It should be like this:

?

#==============================================================================

?

Your question reminds me that I haven’t yet published these scripts in the repository, so I’ll do that soon.

?

?

?

Mark

?

You asked:

?

I don't know if you plan to apply a default port and IP setting in config.ini in the next release to allow scripts to work off the bat or this will be left blank. Should I wait for your next release, before making the relevant adjustment?

?

I don’t intend to make any changes to what’s currently in the config.ini regarding these settings. Very few people use the command server at all, though that might increase a little as a result of the ‘restart’ command being available. So I think the default that the command server port is zero (ie not listening for connections) is sensible. The local host can always send commands if the command server is enabled, so there is no need for a default for the ControlFrom setting, and indeed there is no viable default other than localhost.

?

So the upshot is that the user will always have to do something in config.ini to use the command server, and won’t be able to use it ‘out of the box’.

?

Richard

?

?

Mark

?

As it happens, today I worked out a Python script for sending commands to IBC (see below): this was as part of an ongoing discussion relating to an issue in the IBC repository on Github.

?

I’m not a Python user, so it took me a while to get it to work: it’s based on something I found in the Python Wiki (see ), which is a little out-of-date.

?

This works fine as a free-standing script so it can be run from the? command line in either Windows or Linux, but it would be easy to incorporate it into a Python program.

?

I’ll probably add something like this to the IBC download, as it’s better and more versatile than the current Stop.bat/Restart.bat files (apart from the need to install Python, but that is straightforward).

?

Here’s the script:

?

#!/usr/bin/env py

?

import socket

import time

?

?

TCP_IP = '10.252.0.7'??? # IP address or name of computer running TWS

TCP_PORT = 7463????????? # CommandServerPort setting in config.ini:

BUFFER_SIZE = 1024

?

MESSAGE = b"RESTART\n"? # Command to send to IBC

?

s = socket.socket(socket.AF_INET, socket.SOCK_STREAM)

s.connect((TCP_IP, TCP_PORT))

?

print("sending: ", MESSAGE)

s.send(MESSAGE)

?

data = s.recv(BUFFER_SIZE)

print("received data:", data)

?

time.sleep(1)

?

print("closing socket")

s.close()

?

print("exiting script")

?

?

?