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