IBC User Group

Re: TWS uses a different time zone when using IBC

fbell50x@... (Frank Bell) — Wed, 09 Apr 2025 14:51:32 -0700

Using a live account, if I start TWS manually EDT is used, with IBC it's CDT. I cannot find a TWS time zone option after logon. Could IBC be setting the time zone? I cannot find anything in the config file that seems to apply.

Re: Auto restart still not working

fbell50@... (Frank Bell) — Wed, 09 Apr 2025 07:37:14 -0700

Auto restart worked last night. Perhaps there's a timing issue. Hopefully it was a one time thing.

TWS uses a different time zone when using IBC

fbell50@... (Frank Bell) — Wed, 09 Apr 2025 07:34:30 -0700

I’m in the central time zone but I have my computers on EDT. When I use IBC to start TWS 10.33.1e on a new computer it displays CDT, not EDT. When I start manually it uses EDT.

Manual starts were also using CDT even though the “more options�� login screen showed the time zone as ��(UTC-05:00) America/New York��. I changed the time zone to UTC-06:00, finished logging in, shutdown, logged in again changing the time zone back to UTC-05:00 and TWS now uses EDT.

But with IBC TWS still uses CDT.

I’ve only done this on the paper account. Tonight I’ll try it on a live account.

There’s clearly something a bit screwy going on with TWS. Perhaps the IBC login moves too fast.

Any thoughts?

Auto restart still not working

fbell50@... (Frank Bell) — Mon, 07 Apr 2025 21:18:39 -0700

I set Auto restart in "Lock and Exit" and now auto restart is failing with a different message (full log attached):

SecondFactorAuthenticationDialog

2025-04-07 19:35:17:605 IBC: detected frame entitled: Second Factor Authentication; event=Opened
2025-04-07 19:35:17:617 IBC: Click button: OK
2025-04-07 19:35:17:690 IBC: detected dialog entitled: Second Factor Authentication; event=Closed
2025-04-07 19:35:17:691 IBC: Duration since login: 0 seconds
2025-04-07 19:35:17:691 IBC: If login has not completed, IBC will exit in 90 seconds
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
2025-04-07 19:36:47:693 IBC: IBC closing because login has not completed after Second Factor Authentication
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
2025-04-07 19:36:47:693 IBC: Exiting with exit code=1111
Program has exited
Error level is 1111
Check for 2FA dialog timed out
2FA completion timed-out but TWOFA_TO_ACTION=EXIT so not restarting IBC

Re: Auto restart not working

fbell50x@... (Frank Bell) — Fri, 04 Apr 2025 06:15:26 -0700

Auto restart wasn't set. I didn't have this problem when I set up a different machine a few months ago.

Thanks Richard.

Frank

Virus-free.www.avg.com

Re: Auto restart not working

rlking@... (Richard L King) — Fri, 04 Apr 2025 01:44:04 -0700

It looks like you just haven’t set the ‘Auto restart�� option in the ‘Lock and Exit�� section of the Global Configuration. The message at the end of those settings should say: ‘The application will automatically restart at 07:00 PM��. If it says ‘log out�� rather than ‘restart��, then you’ve set it up wrong.

Richard

Auto restart not working

fbell50@... (Frank Bell) — Thu, 03 Apr 2025 17:49:44 -0700

I'm running on a new computer (Windows 11, TWS 1033). I've taken a look at the dump file, but I don't really know how to analyze it. The last lines are (full dump attached):

Check for 2FA dialog timed out
Check for login dialog display timeout
Check for restart
call :GetAutoRestartOption
Finding autorestart file
INFO: Could not find files for the given pattern(s).
autorestart file not found
Check for cold restart
Normal exit

TWS finished at Thu 04/03/2025 20:00:06.66

IBC running TWS 1033 has finished at Thu 04/03/2025 20:00:06.67

Feature request: Show advanced order reject UI always

pranav@... (Pranav Lal) — Wed, 26 Mar 2025 20:41:05 -0700

Hi all,

Is it possible to toggle the option Show advanced order reject UI always
from ibc?

If not, is it worth adding the toggling of this option to ibc? I am thinking
about people using docker besides my own accessibility use case which is
co-incidental to ibc. <smile

Pranav

Re: TWS Paper Auto LOGON issue

windmill_1965@... (J.G.) — Sat, 15 Mar 2025 20:17:30 -0700

When you say "this morning", what day of the week was that? If it is a Saturday or Sunday then you need to remember that during the weekend you must provide your credentials manually. Simply put, IB has made it impossible to run TWS/Gateway for multiple consecutive weeks without any re-authentication.

Re: TWS Paper Auto LOGON issue

justinlane1979@... — Sat, 15 Mar 2025 10:14:18 -0700

The password is correct though, as soon as I closed tws & ibc and relaunched .bat, it logged in just fine.

Re: TWS Paper Auto LOGON issue

pranav@... (Pranav Lal) — Sat, 15 Mar 2025 08:50:46 -0700

Hi,

You need to change your password for the paper trading account through the web client portal.

Pranav

TWS Paper Auto LOGON issue

justinlane1979@... — Sat, 15 Mar 2025 08:44:03 -0700

I have configured autorestart within tws and it was working well for most of the week. This morning I saw a POPUP indicating "unknown or incorrect password", I did not screenshot it unfortunately. Needless to say, IBC was unable to login automatically. Does anyone have insight on how to fix this? Thank you.

Re: port already in use

rlking@... (Richard L King) — Thu, 13 Mar 2025 05:17:35 -0700

Ah, I understand. The screenshots were too fuzzy for me to make out the text and icons on the tabs, so it wasn’t at all clear to me that the blue popups were just from hovering over the items on the dock. I do have an Ubuntu installation, but only use it for IBC testing, and it has a rather different layout, so I didn’t make the obvious connection.

By the way, please don’t apologise about your English: it seems excellent to me. I don’t know what your native language is, but I can guarantee that I don’t speak a word of it (unless it’s Russian or French, and even then I need a dictionary and a lot of help!...).

You can easily tell which TWS owns the error popup: just kill the frozen one, and if the popup remains it must belong to the working one, otherwise the frozen one.

One thing you could try doing is to modify the /opt/ibc/scripts/ibcstart.sh script to leave a lengthy delay between TWS hutting down at restart time and the script starting the new instance. Look for these lines very near the end of the script (I don’t know what the actual line numbers are for the version you’re running):

# wait a few seconds before restarting

echo IBC will restart shortly

echo sleep 2

and change “echo sleep 2�� to something much longer like “echo sleep 60��. Make sure you know which tab on your dock is for the 4080 port. When it gets to restart time, you should see that TWS shut down, but the associated banner (xterm) window will still be there. You now have 60 seconds to check that the original instance really has gone, and you should now only see 2 TWS tabs (assuming your other TWS instances aren’t restarting at the same time). If the original TWS doesn’t shut down, then the laws of physics must have changed: it’s inconceivable that the “echo sleep 60�� statement could be reached without that process terminating. But perhaps you’ll see another unexpected instance appear, a rogue one �� this has to be the source of the problem. Then when the 60 seconds is up, the restarting TWS will be fired up, and then you would see the ‘port already in use�� dialog.

I wonder whether such a rogue instance might be because there is a crontab entry that runs the account -86 port 4080 TWS lying around somewhere, that you used at some stage for testing or whatever.

Another thing you should perhaps do, before getting to the restart time, is to try and account for all the IBC processes in the ps listing: there should be one for each TWS and Gateway that you start. Any extra ones need to be investigated. You can get a list using this command:

ps aux | grep ‘IBC.jar' > ~/ps-ibc

That’s it for now.

Re: port already in use

rik_en_veronique1@... (rik .) — Thu, 13 Mar 2025 01:36:45 -0700

Hi Richard,

you asked for a screenshot, but I can't explain in english what you see (sorry for that, I'm missing the right words). Let me try to explain the "blue tabs" again : at the bottom of the screen you see many tabs : starting from left I see "linux mint", "file mngr", "firefox" (orange colour), "file mngr", "U7"(green), etc. The "U7" tab is an IB TWS window with account number U7...86". How do I know this ? When I hover my mouse pointer over it, a blue popup appears, showing the full description : see screenshot API-86.2.png. Seven tabs more to the right, you see another green tab "U7" which is another IB TWS window with the SAME account number (see the other screenshot). This second green tab is lightened a bit, so it is shown on the screen, which is grey because TWS is frozen. (the green logo on the tab is from a local broker that is using the IB software).

The problem always occurs with account U...86 that is using port 4080.

When the problem occurs, there are two windows named "U...86" : one window is frozen, the other is functioning normally but the error popup warns me that there is a problem with the API. I don't know if his popup is about the functioning TWS, or about the frozen one ...

I checked all files like configPORT.ini and gwstartPORT.sh and twsstartPORT.sh : I made no mistake with the portnumbers (PORT=4080, 4081 etc). As mentioned, my code runs "/opt/ibc/twsstartPORT.sh" every 5' during the day, from 8:45 untill 22:00 for every port I'm using (2 TWS + 3 gateway currently, so 5 different account numbers and 5 different ports : on the screenshot you can see the 3 gateway tabs ("gw...") and the 5 IBC tabs, more to the right, the other TWS is the red tab with the small IB logo "U1.." : so I see 3 TWS tabs which is "impossible").
The two windows mentioned in 1. show me the same account number, when I hover my mouse pointer over the tab of the window.
There is only one config4080.ini file on my pc with the path ~/Jts4080 in it. All other configPORT.ini files have their own path ~/JtsPORT.
I was running this already when it was called IBcontroller. Last 2 updates I did were IB related (16/11/24 and 18/1/25). I'm wondering now whether the problem started after this last update (from 1030.1q to 1030.1t, because IB forced me to).
It started "weeks ago", just once a week, on monday morning (after startup on sunday morning).
see 4
?
I'm sure it's only on monday, when I start on sunday. I reboot on monday morning and then I'm fine for the week. Except this week : I started on monday, so the problem was there on tuesday morning. I rebooted and started again. But on wednesday, the problem was there again ... Yesterday I changed the autorestart time in TWS to "8h40" : this thursday morning no problem occurred while I was watching.

Without other suggestions, I will try to end the week without changes (and hopefully, without errors). On sunday I will run my startup code only once, and shut it down then for the rest of the week. If that doesn't help, I'll try a complete update (IB + ibc) as soon as I have a free weekend.

rgds

rik

Re: port already in use

rlking@... (Richard L King) — Wed, 12 Mar 2025 12:00:10 -0700

I don’t understand these blue tabs with the account number in them. Where do they come from? And what do you mean by ��7 tabs more to the left or to the right��? In fact I don’t really understand what this paragraph is trying to say.

Let’s summarise what we know (please say if you think I’ve got some of this wrong):

There are incontrovertibly two (or more?) instances of TWS configured with the same API port number.
The two instances must be configured with different accounts, because you have ExistingSessionDetectedAction=primaryoverride in config.ini, and this won’t allow another login with the same user account: the original instance will be automatically closed down, and the ‘port already in use�� dialog disappears.
The two instances must use different config.ini files, because the twsstart.sh script won’t allow another one using the same config.ini to start.
You say you’ve been running this configuration for a long time (years?), except that you’ve upgraded to TWS 1030 at some point.
Everything has been fine until recently.
Nothing has changed ????
Auto-restart worked flawlessly according to the log. The ibcstart.sh script only starts the new instance once the original one has exited: it’s inconceivable that Linux could somehow have not terminated the program but returned a success exit code to the script. So the original instance cannot be one of the conflicting instances. The restarted instance presumably is one of the conflicting instances, though there is nothing in the log that obviously confirms this.
This only seems to happen the first time IBC is run during a week.

After quite a bit of experimenting, I haven’t managed to work out a scenario that could adequately explain all this.

However I do think it must be the case that another instance has been mis-configured with the wrong API port number - you said at the start that you run multiple instances. Can you please double-check this.

Re: port already in use

rik_en_veronique1@... (rik .) — Wed, 12 Mar 2025 01:28:21 -0700

screenshots included now

FW: [ibc] port already in use

rik_en_veronique1@... (rik .) — Wed, 12 Mar 2025 01:16:52 -0700

Hi Richard,

as mentioned yesterday I added some comments in my own logfile to see what happens after the restart.

This morning I saw the same error message, and again twice the same instance : account -86 is open and normally reacting. The same account -86 is still (or again?) there, but the screen is grey and it does not respond to anything. You will find 2 screenshots, both with the grey screen. On the first my pointer is in the lower tab menu above the account -86, so the account number is shown. On the second, my pointer is above another account tab (7 tabs more to the left or to the right), showing the same account number. That's the best I could get to show you what I try to tell.

My code in the background stops checking after 22:00 and does not start before 8:45 in the morning. The auto-restart is just before midnight. I took the screenshot this morning around 8:30. So the code did not do anything, which is confirmed by my logfile. (the code runs "/opt/ibc/twsstart4080.sh" every 5' during the day, from 8:45 untill 22:00 : as far as I know this will open the 4080 instance if not open yet, or do nothing if already open, please correct me if I'm wrong).

If you can't think of any other reason, I will change the restart time and try to see what happens at that time.

Thanks anyway,

rik

IBC 3.21.2

rlking@... (Richard L King) — Tue, 11 Mar 2025 12:51:06 -0700

I’ve just issued a new release of IBC. This is version 3.21.2. Find it here:

https://github.com/IbcAlpha/IBC/releases/tag/3.21.2

This release fixes Issue #293, reported earlier today, which prevents use of the Trusted IP Address list in the Gateway. (TWS is not affected by this bug).

To upgrade to this release from v3.21.1, just extract the IBC.jar and version files from the relevant zip and copy them into the folder where the IBC program files are stored.

You only need to install this update if you run Gateway and need to adjust the list of Trusted IP Addresses in the Gateway Configuration dialog.

Richard

Re: port already in use

rik_en_veronique1@... (rik .) — Tue, 11 Mar 2025 09:18:34 -0700

Thanks for your reaction, Richard.

I have indeed running a code that is checking if some instance has been closed while it shouldn't. This also runs for many years now. I will add comment lines to my logfile to check if this code tries to start a new instance at some time where the ibc-log says that it is open already. Anyway, thanks for the tip.

best regards

rik

Re: Set "Show Forex data in 1/10 pips" from config.ini

rlking@... (Richard L King) — Tue, 11 Mar 2025 05:53:33 -0700

Sorry, I forgot to reply to this.

Currently there is no way to set this from config.ini.

So at present the only way is via the API settings in the Global Configuration Dialog.