开云体育

Jasmin

If you look at the list of I00BC Settings in the logfile, you'll see:

SecondFactorAuthenticationExitInterval=
SecondFactorAuthenticationTimeout=180

When you do second factor authentication, IBKR gives you 180 seconds to acknowledge the prompt in the IBKR Mobile app. That's how long TWS/Gateway displays the Second Factor Authentication dialog, after which the basic login dialog is displayed. IBC needs to know the length of this interval, and SecondFactorAuthenticationTimeout specifies what it is. The only reason to ever change that setting is if IBKR decide to use a longer or shorter interval for some reason: and in the several years since 2FA was introduced, this hasn't changed. If that interval elapses and you haven't acknowledged the 2FA prompt, IBC restarts the login sequence, and you then get another chance to complete the 2FA (provided you have ReloginAfterSecondFactorAuthenticationTimeout=yes). This will repeat forever until the user finally acknowledges the prompt. So if you're in the bath or asleep in a hotel room on the other side of the world, you don't need to worry about catching the prompt the first time it's displayed.

Increasing the value of SecondFactorAuthenticationTimeout from its default of 180 seconds will just increase the time till you get another prompt after missing. Decreasing it is will probably cause problems in some cases, though if you successfully deal with the prompt quickly it will all work ok. So, please don't ever change SecondFactorAuthenticationTimeout unless it's clear that IBKR have changed the 2FA timeout.

The thing to note is that SecondFactorAuthenticationTimeout has nothing to do with the 'If login has not completed, IBC will exit in 60 seconds' message. This occurs when the 2FA prompt has been acknowledged, and the Second Factor Authentication dialog has been closed by TWS/Gateway. Normally login should now complete in a couple of seconds. But experience has shown that there are rare circumstances where this doesn't happen, and TWS/Gateway just hangs. After a period of time specified in SecondFactorAuthenticationExitInterval, if login hasn't completed, IBC shuts down TWS/Gateway, on the assumption that something is significantly wrong. The start scripts contain a setting that governs whether the script will automatically restart IBC, in the hope that doing so will clear the condition causing the problem.

So it seems that you need to change the SecondFactorAuthenticationExitInterval setting rather than SecondFactorAuthenticationTimeout.

In the scenario you describe, where you have a lower-powered CPU, the best thing to do is to not start all the TWS instances at the same time. Just give each one a minute or two to get going before starting the next. Then maybe there won't be any need to change SecondFactorAuthenticationExitInterval.

Richard