开云体育

Oops, sorry, I told you the wrong thing. It should be: TWS_PATH=/mnt/efs/Jts/ But it also looks like you’ve installed Gateway into a non-standard location. These ‘missing’ files should be in

sorry heres the attachment. the error logs has the same missing options file.. although it is now in there as you can see: [ec2-user@ip-172-31-35-164 chartsbacktest_D_20230202_zip]$ cd

unfortunately doenst seem to work. see attached.

This line in gatewaystart_7496.sh is incorrect: TWS_PATH=/mnt/efs/ibgateway/Jts/ibgateway It should be: TWS_PATH=/mnt/efs/ibgateway/Jts/ Sent: 19 February 2023 16:32 To: [email protected] Subject:

hi i run TWS using ibc315 and it works fine. however, when i try ibgateway, it isnt working. both tws and ibgateway are installed on the shared network drive rather in the home folder. the msg is

Hi Richard, The issue is resolved now. There were older restart folders under ~/Jts existed. After removing them, i did fresh login, it created new folder within ~/Jts and then restart worked as

I did notice that you said you’d changed the value to 100s, and that it didn’t help. Let me explain a bit more about this setting. The reason the setting is there at all is that on rare occasions,

I’m not entirely clear what you’re asking. Please can you clarify. Also attach a sample IBC logfile so I can see what settings you’re using. IBC works exactly the same on Linux as on Windows.

Thanks Richard for your reply! I couldnt find the log file anymore since I re-ran the bat and it overwrote it. Using IBC 3.16 and TWS 10.21. I actually did change it from 40-100seconds as stated in

Thanks Richard for this awesome tool. I've been using latest version for more last few weeks now but i couldn't see any automated restart of TWS session after scheduled restart in TWS every day.?

Ok, this is just a result of TWS taking a long time to display the main form after a 2FA login. The way to avoid this is to set SecondFactorAuthenticationExitInterval in config.ini to a larger value.

I experienced the same issue last night. I’ll try to investigate this later today. By the way, for future reference, it’s always helpful to give as much information as possible. For example, you

Ive manually checked and realised even after logging in successfully with 2FA mobile, the app/tws closes after 40 seconds. I've also set the timeout to be 100s and still no differences, kills both at

Fair enough, thanks!

Just create a socket connection, send the command, read the response, close the connection. I’m not a Pythonista, but I imagine this will be pretty straightforward. Sent: 01 February 2023 22:31 To:

Just saw this, thanks. Need to figure out how to send telnet commands from python now…

Thank you Richard.? I modified the scheduled task from Start TWS Live (daily) to Start TWS Live (weekly) starting Sunday and running for 6 days, checking if it runs every 10 minutes

The screenshot shows that the first task is being stopped at 03:36:57 because it reaches its timeout. That means that when the next schedule start arrives at 03:42:01, it is no longer running, so a

As seen in the attached scheduled task history, it's the culprit..? I guess I need to disable it and enable it at exactly 2:32am, my first trigger time? Again, as per today's C:\Jts\launcher.log it

If you started it at 03:42 on Sunday, then I think it will assume that it was a start in the week that ENDS on that Sunday. So when it gets to the configured auto-restart time it thinks it hasn’t