Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Why IBC ended? #244

Open
akatsev opened this issue Dec 18, 2023 · 6 comments
Open

Why IBC ended? #244

akatsev opened this issue Dec 18, 2023 · 6 comments

Comments

@akatsev
Copy link

akatsev commented Dec 18, 2023

Hi,
I wonder why IBC ended its execution. Log is attached.
Particularly, I don't understand what is file the log talk about.
Thank you very much in advance,
A. Katsev.
IBC-3.18.0_TWS-1026_MONDAY.txt

@rlktradewright
Copy link
Member

It ended because you pressed Ctrl-C.

What file are you referring to?

@akatsev
Copy link
Author

akatsev commented Dec 18, 2023

At the end of the log, lines 693-697:
Check for restart
call :GetAutoRestartOption
Finding autorestart file
INFO: Could not find files for the given pattern(s).
autorestart file not found

@rlktradewright
Copy link
Member

The logfile you posted only goes to line 193...

The logile tells you what file its talking about: the autorestart file. You don't need to know anything about that file The IBC script behaves differently depending on whether that file exists. If it doesn't exist, it's not an error, nor is it an error if it does exist.. That's why the l;ogfile doesn't say there's an error! It's just a statement of fact: the file doesn't exist.

So I guess I haven't answered your question about why IBC ended, because I haven't seen the proper logfile. Please attach it to your reply.

@akatsev
Copy link
Author

akatsev commented Dec 18, 2023 via email

@rlktradewright
Copy link
Member

[Please, for future reference, can you attach logfiles (like I asked) rather than quote them in your post. It's much easier for me if i can just open them in a text editor, search, compare with other logs etc. And it makes the narrative of the issue much easier to follow.]

What's happened here is that when you started IBC at 18:39:48, another instance of TWS was already running (perhaps the earlier Ctrl-C just ended the script, but not the running IBC program).

So at 09:09:25:999, TWS displayed the "Existing session detected" dialog. Because ExistingSessionDetectedAction=manual in config.ini, IBC just sat there waiting for you to decide what to do.

Then at 12:05:43:062 you handled that dialog in a way that told TWS to exit and let the other session resume, so TWS did exactly that.

Can I suggest you consider setting ExistingSessionDetectedAction to something other than 'manual' so that this situation is handled automatically?

@akatsev
Copy link
Author

akatsev commented Dec 18, 2023 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants