#2400

Hello,

I'm using ibc for years now, starting multipal instances on sunday or monday, and let them restart overnight until the weekend. Since a few weeks I'm getting the error "port already in use" (see printscreen) on the first restart moment, so I see it on monday or tuesday morning. This is because one instance (always the same) did not close as it should (it is still open, and does not react on anything). The new instance opens well but cannot use the API port as it seems to be still in use by the blocked instance. The only thing I can do is close everything but the blocked instance, restart my pc and start all over again. This happens only after the first overnight restart. The rest of the week everything ngoes fine (until now...).

I have no clue what or where to look for. The log is attached (this week I started on monday, so I saw the error this tuesday morning). Every help is welcome. Thanks,

rik

ibc-3.18.0_TWS-1030_Monday_copy.txt

API.png

#2401

开云体育

rik

?

As far as I can tell from the logfile, IBC is behaving fine. The restart does complete successfully, and then at 2025-03-11 08:40:09:452 the program shuts down: I presume this is because at this point you closed it manually, because it was displaying the ‘port already in use’ dialog?

?

All the evidence points to there really being another instance configured with the same API port. When the first instance closes for restart at 2025-03-10 23:49:02, it really has shut down – there is no possibility that it’s still running. And yet you say ‘one instance (always the same) did not close as it should (it is still open, and does not react on anything)’. Can you get a screenshot showing this supposedly blocked instance, the new instance, and the error message together?

?

What seems most likely to me is that the original instance has indeed shut down and restarted successfully (which is what the log shows), and another new ?instance has somehow been started and it is this one that is showing the error dialog. I have no idea why that might have happened: perhaps you are doing periodic restarts using Task Scheduler to catch cases where IBC/TWS has crashed, and this just happens to be at the same time as the auto-restart?

?

So from my point of view I can’t see anything wrong here: there doesn’t appear to be an IBC problem. However I do note that you’re running a rather old version of IBC, and I would encourage you to move to the latest version.

?

Richard

?

Show quoted text

From: [email protected] <[email protected]> On Behalf Of rik . via groups.io
Sent: 11 March 2025 08:03
To: [email protected]
Subject: [ibc] port already in use

?

Hello,

I'm using ibc for years now, starting multipal instances on sunday or monday, and let them restart overnight until the weekend. Since a few weeks I'm getting the error "port already in use" (see printscreen) on the first restart moment, so I see it on monday or tuesday morning. This is because one instance (always the same) did not close as it should (it is still open, and does not react on anything). The new instance opens well but cannot use the API port as it seems to be still in use by the blocked instance. The only thing I can do is close everything but the blocked instance, restart my pc and start all over again. This happens only after the first overnight restart. The rest of the week everything ngoes fine (until now...).

I have no clue what or where to look for. The log is attached (this week I started on monday, so I saw the error this tuesday morning). Every help is welcome. Thanks,

rik

#2403

开云体育

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

Show quoted text

Van: [email protected] <[email protected]> namens Richard L King <rlking@...>
Verzonden: dinsdag 11 maart 2025 10:51
Aan: [email protected] <[email protected]>
Onderwerp: Re: [ibc] port already in use

?

rik

?

As far as I can tell from the logfile, IBC is behaving fine. The restart does complete successfully, and then at 2025-03-11 08:40:09:452 the program shuts down: I presume this is because at this point you closed it manually, because it was displaying the ‘port already in use’ dialog?

?

All the evidence points to there really being another instance configured with the same API port. When the first instance closes for restart at 2025-03-10 23:49:02, it really has shut down – there is no possibility that it’s still running. And yet you say ‘one instance (always the same) did not close as it should (it is still open, and does not react on anything)’. Can you get a screenshot showing this supposedly blocked instance, the new instance, and the error message together?

?

What seems most likely to me is that the original instance has indeed shut down and restarted successfully (which is what the log shows), and another new ?instance has somehow been started and it is this one that is showing the error dialog. I have no idea why that might have happened: perhaps you are doing periodic restarts using Task Scheduler to catch cases where IBC/TWS has crashed, and this just happens to be at the same time as the auto-restart?

?

So from my point of view I can’t see anything wrong here: there doesn’t appear to be an IBC problem. However I do note that you’re running a rather old version of IBC, and I would encourage you to move to the latest version.

?

Richard

?

From: [email protected] <[email protected]> On Behalf Of rik . via groups.io
Sent: 11 March 2025 08:03
To: [email protected]
Subject: [ibc] port already in use

?

Hello,

I'm using ibc for years now, starting multipal instances on sunday or monday, and let them restart overnight until the weekend. Since a few weeks I'm getting the error "port already in use" (see printscreen) on the first restart moment, so I see it on monday or tuesday morning. This is because one instance (always the same) did not close as it should (it is still open, and does not react on anything). The new instance opens well but cannot use the API port as it seems to be still in use by the blocked instance. The only thing I can do is close everything but the blocked instance, restart my pc and start all over again. This happens only after the first overnight restart. The rest of the week everything ngoes fine (until now...).

I have no clue what or where to look for. The log is attached (this week I started on monday, so I saw the error this tuesday morning). Every help is welcome. Thanks,

rik